Jump to content

Archived

This topic is now archived and is closed to further replies.

bethperkins

Recently accepted support for a Pagelines website - CSS and Account issues

Recommended Posts

bethperkins

I recently started supporting a Pagelines website after the last developer left, Problem #1 is that any updates to Pagelines options cause an old rev of CSS to become active. A "Pagelines Customize" plugin is active. If I use FTP to refresh the CSS with the most recent copy, this also causes an old rev of CSS to become active. Does this indicate that the last developer was directly updating the compiled CSS? Sounds crazy but its all I can come up with as a possibility. The only way for me to "recover" the correct CSS is to cut and paste the compiled CSS.

 

How can I use my compiled CSS to restore the Pagelines Customize Plugin CSS so that updates to the Pagelines options don't restore an old version?

 

How can I find out the status of the Pagelines software that's running on the website? The Pagelines dashboard indicates that it was a "Pro" version but there is no connection to an account. When I click "reset account credentials" it triggers an update to the CSS which loads the old version.

 

 

 

Share this post


Link to post
Share on other sites
Simon

style.css in the themes root folder will reveal the version. Also in the page source there is a version message.

 

If there is a problem with the css, if LESS fails to compile for whatever reason it will load the saved css as a backup.

 

I doubt if the previous guy was editing the compiled css file.

Share this post


Link to post
Share on other sites
bethperkins

I'm running Pagelines v 2.4.2

 

Biggest issue is that I can not FTP a new rev of the CSS (to /wp-content/plugins/pagelines-customize) or update anything in the Pagelines settings without triggering a CSS recompile which pulls an incorrect version of the css. The resulting new compiled version is incorrect. At this point, the only solution I have is to cut and paste the previous compiled CSS into the new file.

 

Can you explain how I can use the correct version of my compiled CSS to recover the CSS in the plugins/pagelines-customize folder?

Share this post


Link to post
Share on other sites
bethperkins

Can someone help me to recover my CSS?

 

  • The current compiled version of the CSS is correct
  • If I refresh the CSS and a recompile takes place, the newly compiled CSS is incorrect
  • The CSS in /wp-content/plugins/pagelines-customize is not correct (and does not appear to be used by the compiler because the rules in the file are not contained in the compiled version)
  • In the pagelines settings, their is no custom css

Can I use the contents of my compiled CSS to get Pagelines working again????

Share this post


Link to post
Share on other sites
James B

If the customize plugin isn't being used deactivate the plugin. If the previous developer inserted the css changes into the style.css and didn't manually create a style.less for the plugin then it won't go into the compiler. Only a style.less will be compiled, if a style.css was used then that will just provide a static style sheet.

 

I would say copy all your correct css so you have a copy saved in a blank text doc that you can fall back on. Deactivate the customize plugin completely and see what displays on the site with that inactive. Paste your code in to the css/less panel inside the Framework admin and see if your changes take affect, that way you can tell if it's working. If it does, delete the current copy of the customize plugin with the developers previous code in. Install a fresh version and in the blank style.css paste your correct code or create a style.less inside the customize plugin and paste your code in there so it compiles into the main compiled css file.


Kindly search the forum and read the documentation before posting. It will help you resolve many issues.

For CSS help be sure to check out W3Schools first and be sure to download FireBug for FireFox for troubleshooting.

James B

Share this post


Link to post
Share on other sites

  • Similar Content

    • glyph.marketing
      By glyph.marketing+
      Hello, I am having a problem similar to that experienced by Michael Kummer here. We have pages that show this automatic scrolling issue (examples here and here) and it is sufficiently annoying that we have seen customers bounce while trying to convert. Strangely, it only happens at specific resolutions, so it can be difficult to reproduce. In general we can only consistently reproduce it on a 4k resolution with a browser width between 1517 and 1536px. 
      Thanks to Michael Kummer's help we were able to set the overflow-anchor property to none in the entire body, which fixed the issue as far as we can tell, but also obviously disabled scroll anchoring for the whole site. I tried applying it to the specific element that looked like it was being reloaded, which was the PL Meganav extension, but that was unsuccessful. 
      Can anyone help us figure out which element or ID we can apply this property to, so that we can fix the scrolling issue but not disable scroll anchoring for the entire site?
      Thank you - 
      Glyph Language Services
    • chamois_blanc
      By chamois_blanc+
      Hello,
      Shouldn't the image PL5 component be using the srcset/picture css directives to pick the correct size for an image? or it does already and I don't know how to use it? Thank you for any advice or enlightenment.
    • Dan Haddock
      By Dan Haddock
      Plugins Active and installed: 
      Akismet Anti-Spam
      Coming Soon Page & Maintenance Mode by SeedProd
      Contact Form 7
      Cookie Law Info
      DMS Professional Tools  
      Enhanced Media Library  
      Flamingo
      Google Analytics for WordPress by MonsterInsights
      Google XML Sitemap
      Jetpack by WordPress.com
      Legull 
      Loginizer   
      MailChimp for WordPress
      PageLines Updater    
      Schema App Structured Data 
      Sucuri Security - Auditing, Malware Scanner and Hardening
      Uber reCaptcha    
      Yoast SEO
      Wordpress Version: 4.8.1
      Pagelines Version: 2.2.4
       
      Good Evening/Afternoon or Morning, 
      I am running into a problem with CSS styling not applying inside of most browsers (Safari, Firefox) when I am logged in to wordpress, and all browsers that I have tested when I am logged off and the site has been made public (Chrome, Firefox and Safari).
      As a result, I have managed to identify the probable cause. It looks as though these browsers are refusing to render my sites compiled CSS file due to it being a HTTP URL rather than HTTPS.
      I have attempted to change this URL to HTTPS in my browser, however it brings back an ERROR: File not found page - https://www.shortfilmblog.com/wp-content/uploads/pagelines/compiled-css-core-1505847507.css
      What would you suggest in this regard? Would this be resolvable from your end?
      Happy to provide any further details required.
    • Borries
      By Borries+
      I know this is not an easy problem. Maybe there is a easy solution.
      I have tryed to uses the existing solution, that I have found in the forum
      I changed the colours of my nav (simple nav) and the hover effect (a. hover).
      I really tryed to highlight the active/used link in the nav but I cant figure it out.
      I want it to be black when active.
      Any help would be appreciated. Thanks.
      http://www.marcborries.de  nav link: "Sinn & Selbst" 
    • Michael Kummer
      By Michael Kummer+
      Hi guys,
      every since Chrome introduce scroll anchoring (see chrome://flags) blog posts on my page start scroll automatically as soon as the user scrolls down a bit. It is super annoying and I don't know exactly what triggers the incompatibility with Chrome's latest feature that is supposed to improve usability.
      Since I don't know what causes it (Pagelines, or a Plugin), I would like to disable the feature using a CSS override that Google describes as follow:
      "Scroll anchoring aims to be the default mode of behavior when launched, so that users benefit from it even on legacy content. A CSS property overflow-anchor can disable scroll anchoring in part or all of a webpage (opt out), or exclude portions of the DOM from the anchor node selection algorithm. This property supports the following values when applied to an element E:
      overflow-anchor: auto (the default value) declares that the DOM subtree rooted at E is eligible to participate in the anchor node selection algorithm for any scrolling box created by E or an ancestor of E. overflow-anchor: none declares that the DOM subtree rooted at E is not eligible to participate in the anchor node selection algorithm for any scrolling box created by E or an ancestor of E." Do you guys happen to know how to use that property with the ROOT element so it applies to the whole page?
      Thanks
      Michael 
×