-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing images on website, when using LSCache #4
Comments
www.lungekursus.dk homepage looks ok to me when I use Desktop Chrome and Iphone Safari to access it. Both works fine from my point of view. Can you give us an example URL with the problem and steps to reproduce it? |
My original site is www.lungekursus.dk (running on apache)- hosted at digital ocean (my own server) I has to disable lasy loading of images on the litespeed server (a2.lungekursus.dk), the website load correctly. (that is a change form my apache server) |
What do you means "lasy loading of images" and where to set it? LiteSpeed cache plugin for Joomla doesn't have such function for it. Not sure how you turn it off/on. By the way, you will need to turn off other full page cache plugin ( such as Jotcache) before enabling litespeed cache plugin for Joomla |
Lasy load: So I should disable Jotcache? |
Doesn't seem to happen when we got login and checked. |
After release it and the updates, it looks like it's working |
Setting:
A2Hosting, managed hosting enviroment.
CMS: Joomla 3.8.5
Plugins: JCH optimizer, Jotcache (memcached, device specific)
Caching setting: memcached, device specific
Problem: Some images does not load correctly on buttom of website
link: a2.lungekursus.dk
There should be the following images: AstraZenica, Teva,Roche, Alk,Novartis, Boehring Ingelheim.
Ord link www.lungekursus.dk
This is only a problem on the mobile device.
The original website www.lungekursus.dk, loads correctly (An Apache 2.4 webserver, memcached ....) Same website, just not LiteSpeed cache or webserver.
I tested JCH Optimizer, now as Lasyload + Force Load -> That seems to work.
But still a change since Apache.
The text was updated successfully, but these errors were encountered: