NO BUG: Problem with Accordion Element on different and same browsers

Browser: Firefox 120.01 & Microsoft Edge newest Version
OS: Windows 11
URL: staging elements – Pott Elektrofahrräder


Hi everyone,
i am having problems with the accordion Element in Bricks.
On some devices it looks like it should, on others it is leftbound and the elements are stacking ontop of each other. On another PC there are even the lines missing from the List element withing.
I have no idea what is happening - and i am not sure if this is a bug or if i have messed something up. But it works… most of the time.

Hi @potti ,

Thanks for the link.

Unfortunately, tested it on Windows and all works well as per your first image on the left.

Based on your images, seems like it’s either the CSS is not generated yet while browsing.

I can see you are using litespeed and the CSS was generated from litespeed cache plugin.

You can try clearing the browser cache on those problem PCs. (CTRL + F5 for hard refresh)

Regards,
Jenn

Thank you very much for checking, Jenn!

The thing with the CSS not being ready while loading/browsing, is this an issue that could be solved anyhow or tweaked?

It really worked, thanks for it being such a simple solution :slight_smile: Eve though it didn’t work the first time after i cleared all caches. But for alle the other people testing the site it worked :slight_smile:

Kind regards,
Kevin

Hi @potti ,

Glad that works.

If your website is already live launched, would suggest you put the site under maintenance (new feature in 1.9.4) so nobody can access it while you are tweaking the site.

Once completed, turn off maintenance mode, and clear LiteSpeed cache, and the website visitors should be able to see the latest update without the need to clear their browser cache.

However, the settings of your LiteSpeed cache or any performance-related plugins also play an important role. Some of them may remove the version strings on asset files (CSS, JS etc) and this will cause browsers not to fetch the latest changes.

You could search for more articles about browser cache in Google for a better explanation.

I will mark this thread as NO BUG now.

Regards,
Jenn