Plugin Support
qtwrk
(@qtwrk)
Hi,
Please upload image to somewhere like imgur.com
We will help you once we see the issue
Or please try descript how does it “breaks” ?
Best regards,
Thread Starter
Gene_W
(@kelltech)
Ok here are some screens without and with LSC activated:
Before and after
-
This reply was modified 5 years ago by
Gene_W.
-
This reply was modified 5 years ago by
Gene_W.
Plugin Support
qtwrk
(@qtwrk)
Hi,
Could you please do a purge all ?
And see how it goes ?
Best regards,
Thread Starter
Gene_W
(@kelltech)
Thanks for your reply. I did try purge all after updating, but I can try again. I’m currently away from my computer until Friday, so I’ll try then.
Speaking of purge all, even though I have my settings to manual purge only, LSC still insists on purging all not only after performing updates but also before. A little annoyed that my choice of settings is ignored, but at least it’s getting purged I suppose.
Plugin Support
qtwrk
(@qtwrk)
Hi,
after performing updates but also before
You mean when update plugins/themes/WP core ?
I see other user mentioned this as well , but from the debug log I can see , the purge call is trigger by WP hook , and that hook only happens when something is updated.
Best regards,
Thread Starter
Gene_W
(@kelltech)
Could you please do a purge all ?
And see how it goes ?
Updated, purged all and still broken. Deactivated LiteSpeed Cache and it fixes. To my understanding, I’m on a LiteSpeed server if that’s helpful to know.
Plugin Support
qtwrk
(@qtwrk)
Hi,
when you see page broken , could you please open browser dev tool , and in “network” tab , see if there is anything out of ordinary ? like 404 request or 403 request ? anything that is not 200 OK
Best regards,
Thread Starter
Gene_W
(@kelltech)
Ok, thank you for having a look.
Here are the errors I see in network that are not there when I deactivate the plugin:
Mixed Content: The page at ‘https://genewhitehead.com/’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://genewhitehead.com/gwwp-suitcase/litespeed/cssjs/1e93a.css’. This request has been blocked; the content must be served over HTTPS.
VM193:1
Mixed Content: The page at ‘https://genewhitehead.com/’ was loaded over HTTPS, but requested an insecure script ‘http://genewhitehead.com/gwwp-suitcase/litespeed/cssjs/1422b.js’. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at ‘https://genewhitehead.com/’ was loaded over HTTPS, but requested an insecure script ‘http://genewhitehead.com/gwwp-suitcase/litespeed/cssjs/b14f7.js’. This request has been blocked; the content must be served over HTTPS.
(index):1 Mixed Content: The page at ‘https://genewhitehead.com/’ was loaded over HTTPS, but requested an insecure script ‘http://genewhitehead.com/gwwp-suitcase/litespeed/cssjs/c212e.js’. This request has been blocked; the content must be served over HTTPS.
(index):38 Uncaught TypeError: jQuery(…).matchHeight is not a function
at HTMLDocument.<anonymous> ((index):38)
at i (jquery.js?ver=1.12.4-wp:2)
at Object.fireWith [as resolveWith] (jquery.js?ver=1.12.4-wp:2)
at Function.ready (jquery.js?ver=1.12.4-wp:2)
at HTMLDocument.J (jquery.js?ver=1.12.4-wp:2)
Plugin Support
qtwrk
(@qtwrk)
Hi,
Could you please check in your WP setting —> General , site URL and home URL are set to https:// ?
Best regards,
Thread Starter
Gene_W
(@kelltech)
They are both set to https://.
Thread Starter
Gene_W
(@kelltech)
Just updated to the new LSC today and still having the same problem. I checked lazy load images, css and js settings but all with no luck. Then I deactivated every plugin except LSC, purged all but still had the same issue. I think I am officially stuck. 🙂
Plugin Support
qtwrk
(@qtwrk)
Hi,
Could you please verify , in cache setting —> purge
purge stale , is it ON or OFF ? please try set it to OFF and purge all
Best regards,
Thread Starter
Gene_W
(@kelltech)
Hi again, I checked the purge stale setting and it was set to ON. I switched it OFF, purged all, cleared my browser and I’m sorry to report still no change. 🙁
Plugin Support
qtwrk
(@qtwrk)
Hi,
Please create a ticket here
We will investigate it further.
Best regards,