Browser: Chrome 110 OS: macOS / Windows / Linux / etc. URL: Link to a page that illustrates this issue Video: Short screen recording that illustrates this issue (free tool: jam.dev)
[Please describe this bug in as much detail as possible so we can replicate & debug this bug]
Images are not loading for guests or other roles that are not Admin (due to caching setup on exclude section).
ACF Pro having an image field on homepage as a section background so clients can change the image.
This also applies to all images on the page that are dynamically placed.
Litespeed Cache enabled, I did test clearing all cache and turning off all other cache such as object etc. Even after purge the images wouldn’t load for other user accounts, Admin accounts not affected as they are excluded from Cache but all other roles and guests are.
Once disabled the Enable Cache in section 1 Litespeed all images return, this only happens in Bricks for me.
Hope someone else can replicate, seen a few posts about images / backgrounds and i wonder if they’re linked to cache in some way.
It’s hard to say what’s going on…
Is it possible that you are caching for logged-in users, too? If so, you should exclude the builder. You can add the ?bricks=run parameter to the exclusion rules in the Litespeed settings (see Litespeed docs).
If that doesn’t help, please send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.
Thanks for the reply, strangely it all started working again recently even with cache on.
Unfortunately now having an issue with image gallery, the images are there but not visible. If i enable lightbox you can click the images and they open up, if you drag where the image is its there but just invisible. I have duplicated image gallery, made fresh on new pages and removed all plugins and checked on guest users in incognito mode which makes me wonder if this happened before with the images and they were there just invisible.
As I said, it is difficult to say what is wrong with your caching. You can try deactivating the settings in the caching plugin bit by bit. That would at least be our first debugging step.