[Resolved] Issue between GeneratePress and Litespeed caché

[eduard sans]

Hi there, ok so I had this weird thing going in all of my pages (and to this day I really didn’t think it was a big deal but a client just complained):

So here it is how you can replicate it (it is a demo site):
https://bundle2.eduardosans.com

If you access it for the first time (or do it through the incognito window), you’ll see how colors change briefly (at first there is some green navigation menu – check screenshot below) and then it changes into the actual design.

What I tried so far:
– deactivating and activating plugins and yes, it is related to Litespeed caché (no big surprise so far, because I checked all CSS and no line of code should display that green color in the navigation menu)
– surprise comes when I activate Litespeed with another theme and this greenish thing doesn’t happen. After some tests, I’m thinking there might be an issue between generatepress and litespeed caché plugin.

Any thoughts? Thanks!

[Leo]

Hi there,

It could be a setting within LiteSpeed Cache that’s causing the issue. Looks like a flash of unstyled content.

You could try toggling off the settings in the plugin on/off to test, or check with LiteSpeed cache’s support team to see if they can point you in the right direction.

[eduard sans]

Hi there, ok so after quite some extensive check with litespeed support I’m back here. You can see everything I’ve tried so far in this thread (it’s a little bit long to explain and I think it shows best to link you there):

https://wordpress.org/support/topic/issues-with-cache-2/

As you’ve read, I’m now at this point where they say it must be CSS related but I’ve tried removing all custom CSS, disabling child theme, etc. and I’m still at the same point. Any other thoughts? If you need access please let me know, it is a demo site so there’s no peril in screwing up something. Thanks in advance!

[Leo]

Does it say which CSS is causing the issue?

[eduard sans]

“If issue still exists, you must verify your CSS sources. cache plugin uses only what exists and if there is nothing cached, the plugin uses existing sources for CSS to optimize it.” – this is what they say after we manually removed EVERYTHING in the lscache folder from my server. There is physically nothing else in cache folders.

About the CSS source: The problem is that I remove all my custom css, deactivate all plugins except GP Premium and Litespeed cache and problem still remains. Then I deactivate GP Premium and the issue is gone. At this point it feels like everything is pointing in that direction.

I enclose details so you can access and have a look (if you need further info about what’s been tested so far, please check the link on my previous response, it’s been quite some things)

BTW the issue now is that instead of a green navigation menu, there is a blue one showing briefly before getting to the actual design (everything is explained in the link to the litespeed cache support).

Thanks!

[David]

Hi there,

your site login requires 2FA – i did notice on the login screen this PHP Error:

Notice: Trying to access array offset on value of type bool in /home/esans/bundle2.eduardosans.com/wp-content/themes/generatepress_child/functions.php on line 458

You may want to eliminate that from the equation.

Now the really odd part – on first load i saw the blue styled navigation. On subsequent loads with the cache cleared and using different browsers the site loads correctly first time. That says to me it is NOT a stylesheet loading issue, if it was – it would occur in an incognito browser and also i would be able to find the ‘blue’ styles in the CSS – which i cannot.

This points to some weird stuff going on at the server level, as if its loading an old cached object and then refreshing that,. Really hard to track or debug that as it only occurs the once.

[eduard sans]

Hi there David!

– About the 2FA: Yes, sorry for that. I removed it already
– About the PHP error: don’t worry, it is unrelated. It’s referring to a line of code in my functions.php that will automatically display the client logo on the login page. That error is just shown when there’s no logo whatsoever (like now).

This issue is just weird because it happens to all my clients (by default I work with two different bundles that basically work with the same tools -only difference is woocommerce in one of them- so then I clone one or another depending on my client’s needs) and it is sth I really never paid attention to because as you said, it just shows briefly the first time you access it (or everytime you access it through incognito mode when opening a new browser). But now one of my clients complained so here I am.

I know it is odd and I’m contemplating contacting my hosting company as well, but before moving on to another support team I’d feel a little bit more confident if you could give it a look, just in case there is something that due to my technical skills I’d be missing out. My thoughts so far:

– A noticeable thing is that if I activate the twenty-two theme, the issue is gone. So I’m thinking that somehow somewhere there must be sth in GP Premium and/or Generatepress that captures the previous design and displays it briefly.
– Litespeed cache seems to be off the equation because unless there was some other folder they didn’t tell me about, we literally removed every file from the lscache folder on a server level (through file manager in cpanel).
– My custom code cannot be either, because all my CSS is in style.css of my child theme, and I tried: a) removing CSS manually and b) reverting to Generatepress theme (instead of Generatepress child theme) and the issue still shows.

Any thoughts?

[David]

I was able to get this screenshot on the developers tools whilst the blue styles were visible:

https://www.screencast.com/t/9Y5UcTNbn

Which allowed me to pinpoint the only CSS file that is initially loaded:

https://bundle2.eduardosans.com/wp-content/litespeed/ucss/45876a4ac0884f81f94bccb6a640dffa.css?ver=5757b

Theres also a cached JS file:

https://bundle2.eduardosans.com/wp-content/litespeed/js/717b67529fc96fd288810c4f8eae2a91.js?ver=5757b

As a note: Switching themes is a large enough change to the code base that will burst most server caches.

[eduard sans]

Done! thank you so much David, I wasn’t able to point that out. So yes, apparently they didn’t tell me about that litespeed folder with extra .css and .js in it (which would’ve been the logical step to take before sending me away). Now I removed all those files from the server and the issue is gone. Sorry to have brought someone else’s issue to you.

Thank you again, as always, awesome support.

[David]

Not a problem – glad we could be of help 🙂

[Author]

Posts