Insecure content blocked after 2.07 update

Hello @taisho,

I’m not sure if this is caused by the latest release as we have not changed anything related in the newest version.

Checking your reply I can see that this is related to the admin dashboard page. Can you please check if the site URL in your Settings -> General uses HTTP or HTTPS?

If is using the first one, can you change that to HTTPS instead which should fix this issue also?

Thanks!

My test website is fully https and in general settings, there are 2 https links. After uninstalling 2.07 and installing version 2.06 (to exclude any possible issues with rollback) from the repository, then clearing website and browser cache, everything is back to normal, green buttons don’t have spinning wheels and display correctly “Save changes”, so it’s clearly 2.07 issue.

I think that the new update system messed something up because I can see the yellow updating button in place of the 2.06 blue refresh stats button on the dashboard tab.

EDIT: I’ve noticed that it can actually be 2 problems. Even on 2.06, there is blocked content for bundle.min.js:1, so 2.07 spinning wheels may or may not be related. Because on 2.06 all tabs appear and seem to work correctly, I probably never noticed this blocked content icon.

Mixed Content: The page at ‘https://parymet.pl/staging/wp-admin/upload.php?page=optimole’ was loaded over HTTPS, but requested an insecure resource ‘https://parymet.Mixed Content: The page at ‘https://parymet.pl/staging/wp-admin/upload.php?page=optimole’ was loaded over HTTPS, but requested an insecure resource ‘https://parymet.pl/staging/’. This request has been blocked; the content must be served over HTTPS.

Also on 2.06 console says for upload.php?page=optimole:1, but only on Chrome, Firefox doesn’t mention it:

[DOM] Password field is not contained in a form: (More info: https://www.chromium.org/developers/design-documents/create-amazing-password-forms)

I don’t think it has any serious impact.

• This reply was modified 5 years, 5 months ago by taisho.
• This reply was modified 5 years, 5 months ago by Jan Dembowski. Reason: Removed short link

Hello @taisho,

That’s pretty strange. Would you mind to contact me on https://optimole.com/#contact to have a closer look and debug the issue together?

Looking forward to helping you.

Hello,

I got some suspicion which came out to be true:

1. I haven’t noticed mixed content before because I have this plugin installed on an unreleased website https://parymet.pl and here it worked correctly on 2.0.6 without any mixed content or any other console errors.
2. Some time ago I created a few staging websites to test my plugins, including https://parymet.pl/staging. It’s here where all reported errors appear. On the staging website I probably never visited Optimole’s admin, 2.0.6 was already set up once a staging website was created.
3. After updating to 2.0.7 https://parymet.pl works perfectly.

These 2 websites are almost the same. I think the problem may be related to the main path of the website being a folder. Or maybe lack of trailing slash after folder name? It’s only in admin, the whole staging website is properly optimized with Optimole’s CDN images.

• This reply was modified 5 years, 5 months ago by taisho.
• This reply was modified 5 years, 5 months ago by taisho.
• This reply was modified 5 years, 5 months ago by taisho.

Hello @taisho,

That’s indeed strange. Do you still face the issue right now?

Can you send a support request on https://optimole.com/#contact with a screenshot of the General settings page, top area, from the site with problems?

Thanks !

Hello,

I’m using 2.0.6 at the moment but I’m going to update to 2.0.7 today and send screenshots of admin tabs and console where errors are visible on https://optimole.com/#contact

Best Regards