Jump to content

Archived

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

tpldrew

Which File Generates the CSS - Need to tell Caching Which File to Let Pass Through

Recommended Posts

tpldrew

I've been suffering a number of issues (detailed elsewhere) with data disappearing on servers using heavy caching to serve up Wordpress. The folks at WPEngine are helping fix this issue so others with DMS installed can benefit.

 

We've narrowed down the issue, but need help identifying which file gets hit directly to generate the CSS.

 

If we can tell them this their team can let it pass through the cache and load.

 

Can anyone help with this. I'm in a chat with the cache team at WPEngine right now.

Thanks,

Andrew

Share this post


Link to post
Share on other sites
Simon

The css is written to a static file in the uploads folder. ive replied to one or two of your other threads.

 

Please try and keep this all in one place.

Share this post


Link to post
Share on other sites
tpldrew

Sorry simon. I thought this was a better way to handle this.

I'm nearing the point of giving up on fixing this.

 

I'm at wits end without any idea how to proceed.

 

What writes the CSS to the uploads folder? That's the question maybe?

 

- Andrew

Share this post


Link to post
Share on other sites
tpldrew

Simon,

 

Here's the use case and problem:

 

  • User Status: Logged In
  • Working in DMS Editor the site looks fine, everything seems to be working as I add, edit, or update items, modules and text on the page. Here's what it looks like http://i.imgur.com/AjS818f.png
  • I Publish the page and refresh a second browser (user status: NOT logged in) where the site is completely styleless. Here's what that looks like: http://i.imgur.com/C458MEc.png
  • I Purge the Cache and refresh the front end and the site is back to normal.

I've spent four hours troubleshooting this with the team at WPEngine and they are trying to help. 

 

Do you have any questions about the problem?

- Andrew

Share this post


Link to post
Share on other sites
Simon
You are editing in the production site.

They cache the page when you click save a new CSS file is created and the old one deleted

You see the old page with the old URL until you clear their cache

Ask them if there is a way to disable the caching on the production site so you can make changes there and not in staging


Sent from my iPad using Tapatalk

Share this post


Link to post
Share on other sites
tpldrew

Simon,

I've asked them if they can disable the cache, unfortunately not.

Also, I'm NOT making changes on the staging site. I'm making the updates on the production site.

What they've asked me to find out what forces the re-write of the css file.

That way they said they can make sure this executes.

Does that help?

- Andrew

Share this post


Link to post
Share on other sites
Simon

Its ok, i'll try to make my reply more clear.

 

You are making changes o the production site, the production site is cached.

 

When you click save dms creates a new css file using all the settings.. the css file is saved to the uploads folder.

 

If you look at the css files url you will see it has a timestamp, this is so CDN's, browsers etc always get the latest file.

 

WPE is caching the page, so when you click sav and refresh.. you are looking at the cached page and he url for the css is now broken, because the url changed when you clicked save.

 

There *might* be a way we could hack the code to never write a file on save, or to always use the same url but then if you changed a colour or a width for example... your end users would never see the change..

Share this post


Link to post
Share on other sites
tpldrew

Simon,

Thank you. That's helpful.

Let me ask the WPEngine folks if they can help me with that information.

- Andrew

Share this post


Link to post
Share on other sites
tpldrew

Simon,

Unfortunately, WPEngine can't help with that.

Everytime I hit publish I have to Purge the Cache...

 

I'm going to have to move on without a real solution to this on either end.

Thanks though.

- Andrew

Share this post


Link to post
Share on other sites

  • Similar Content

    • Michael Kummer
      By Michael Kummer+
      Hi guys!
      I have noticed that my primary sidebar becomes intermittently invisible when browsing through various blog articles on michaelkummer.com/blog.
      See:
      https://www.dropbox.com/s/z646sgoa3mfjl1j/Screenshot 2018-07-12 15.57.46.jpg?dl=0 and https://www.dropbox.com/s/vdledzzgginvwgv/Screenshot 2018-07-12 15.57.57.jpg?dl=0
      Upon refresh, the sidebar appears. I have been using the following CSS code to hide the sidebar on mobile without any issues. 
      @media only screen and (max-width: 993px) {
      /* hide sidebars */
           .plsb {
              display: none !important;
          }
      }
      I tried to add the following CSS to force the sidebar to show on screens that are wider than 994 pixels but to no avail. Any clue what could be causing this issue?
    • Michael Kummer
      By Michael Kummer+
      Hi guys!
      I am using the LESS/CSS Pagelines extension and tried to add the following code to make use of FontAwesome:
      a.c2a:before {
          content: "\f07a\00a0";
          font-family: "Font Awesome 5 Pro";
          Font-weight: 900;
          font-style: normal;
          font-weight: normal;
          text-decoration: inherit;
          padding-left: 4px;
      }
       
      The issue is that as soon as I have the CSS via the Custom Styling text box, Pagelines (or the extension) strips out the backslashes (\). As a result, I had to abandon the CSS/LESS extension and instead add all my CSS code to a separate .css file.
      Is there a fix or workaround for this?
      Thanks
      Michael
    • 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.
×