Broken Shop page
-
Hi
From time to time the Shop page is loading without the full CSS so it looks broken.
When I delete the Cache from admin the situation is solved.
I do not want to make it manualy each time and do not want the customers will see
such broken pages.
What can be done ?
-
When this happens is the Autoptimized CSS-file not found (404)? Because in that case *something* is removing Autoptimize’s cache (I’ve seen reports of Divi doing this, Siteorigin Widgets had this problem too but it should be fixed, others might do so too) but your page cache will still have pages with references to the Autoptimized file.
hope this helps,
frankThanks for your prompt reply.
I do not know if the Autoptimized CSS-file was not found.
Could I see the 404 error if the Autoptimized CSS-file not found in the console?By the way, the specific site has also:
Free Autoptimize CriticalCSS.com Power-Up
and Free Cache EnablerCould I see the 404 error if the Autoptimized CSS-file not found in the console?
yes, you could. what you can do to confirm is testing the broken page in https://webpagetest.org/ and providing me with the resulting test report URL for me to review maybe?
No problem to send you the test results.
The problem is to replicate this issue…
Need to wait few days for the cache to be filled ??keep me posted ??
Hi
Today it happened again.
Shop page is broken.
In Chrome console I see the errors that block the page from loading.
Here is one of them:
Mixed Content: The page at ‘https://*****.co.il/shop/’ was loaded over HTTPS, but requested an insecure stylesheet ‘https://*****.co.il/wp-content/cache/autoptimize/css/autoptimize_eb57dfe9045886a7df3e1a6870e517b8.css’. This request has been blocked; the content must be served over HTTPS.The page test for this page at webpagetest is here:
https://webpagetest.org/result/190525_0Q_f4fda85a22a1ad06177b1a2a35ddbd49/That’s weird, for 2 reasons;
* AO uses the URL as set in Settings -> General -> WordPress Address, so if that is set tohttps://
the Autoptimized files should _always_ be served over https
* In the webpagetest results the AO’ed files are loaded overhttps://
and all is fineI did a quick test and see your site can _also_ be loaded over
https://
, whereas I expected to be redirected to thehttps://
-version.Based on the above, I think you’ll need to (have someone) revisit the http/https setup of your site?
frank
Thanks again for your prompt reply.
Wordpress admin setting urls are https.
I have a redirect in the htaccess file from http to https.
After your reply I have checked the main page and could not see the site over http
as it was redirected to https as expected.
But for xxxx.co.il/shop it was not redirected to https as you mentioned.
So I guess the redirect in the htaccess is for the main page only and not defined
for the inner directories.
Going to fix it now and report…I have changed the htaccess file to redirect all pages to https
but still got the mixed blocked content msg on shop page.
I cleared the cached in AO and it’s back to normal.OK, I *think* that should fix the problem for good ??
I hope and will update.
Thanks for now ??Enjoy your weekend ??
You too ??
Hi again
The problem keep happens.
Here is a copy from the console:Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS. Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS. Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS. Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS. Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS. Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS. Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS. Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS. (index):2 Mixed Content: The page at 'https://XXXXX.co.il/shop/' was loaded over HTTPS, but requested an insecure script 'https://XXXXX.co.il/wp-includes/js/wp-emoji-release.min.js'. This request has been blocked; the content must be served over HTTPS. f @ (index):2 (index):1 Mixed Content: The page at 'https://XXXXX.co.il/shop/' was loaded over HTTPS, but requested an insecure script 'https://XXXXX.co.il/wp-includes/js/jquery/jquery.js'. This request has been blocked; the content must be served over HTTPS. (index):1493 Mixed Content: The page at 'https://XXXXX.co.il/shop/' was loaded over HTTPS, but requested an insecure image 'https://XXXXX.co.il/wp-content/plugins/wp-accessibility-helper/assets/images/accessibility-48.jpg'. This content should also be served over HTTPS. (index):1 Mixed Content: The page at 'https://XXXXX.co.il/shop/' was loaded over HTTPS, but requested an insecure script 'https://XXXXX.co.il/wp-content/cache/autoptimize/js/autoptimize_5012568e40c7522a91787fd5cfef544e.js'. This request has been blocked; the content must be served over HTTPS.
- The topic ‘Broken Shop page’ is closed to new replies.