LiteSpeed Cache Causing Design Issues on Website

Status
Not open for further replies.
D

djm

New Member
#1
#1
Morning Everyone,

My website uses the Divi Builder alongside multiple plugins, including LiteSpeed Cache.

Recently we've started seeing some design issues on our website, mainly our menu / navigation bar not showing up correctly on the website homepage. Some sub-headings become larger and bolder than others, and some sub-headings are even removed from the drop down list.

After speaking to Divi Support they recommended disabling LiteSpeed, which we did and the problem was resolved.

However, in the long term we want to keep LiteSpeed on, as it helps to keep our site running quickly and smoothly.

Has anyone else experienced anything like this? Or has anyone got any advice?

Thank you!
 
A

alanrogers

New Member
#3
#3
Yes, I've just experienced issues with Header Text missing when I have LiteSpeed Cache activated - I've been using the plugin on the majority of my websites for over three years now, as they're on a LiteSpeed server?

To me, it seems to have been triggered by a Wordfence update - 8.0.5?

I've deactivated LiteSpeed Cache for now, but would rather reactivate it than move to another plugin if it can be resolved?
 
D

djm

New Member
#4
#4
@alanrogers I kept LiteSpeed deactivated for about an hour and then reactivated it, and that seemed to do the trick. Not sure why, maybe while it was off it allowed all pages and menu bars etc to reload properly to what they are supposed to look like, so then when turning it back on they were reloading the correct designs?

Not sure if that is how it works, but either way that worked for me and is still working now so maybe give that a go, just keeping it deactivated for a fairly longer period of time
 
A

alanrogers

New Member
#5
#5
@djm Many thanks for coming back on this thread, unfortunately, it hasn't worked for me when I just tried it on my own website, so I've had to deactivate it again. I have notified Divi Support team too, not that I think it's their issue directly.

BTW. I was wrong to link it to the latest Wordfence update in my original Post, that doesn't now appear to be the case. Hopefully it will be reported more widely and LiteSpeed will come up with a fix.
 
Status
Not open for further replies.
Top