Mixed content errors

Hi,

the mixed content fixer is active since the data-rsssl=1 maker is present in the page source. Your site seems to be using Divi theme, which due to minification and caching option can cause mixed content issues after moving to SSL. This can be fixed by temporarily disabling the Divi minification options and clearing the Divi cache. That will update the links to https:// which should result in the secure lock. See https://really-simple-ssl.com/knowledge-base/mixed-content-when-using-divi-theme/ for detailed instructions.

Ok that’s great, thanks – client changed the theme to something unfamiliar (aren’t they all at first!) – I’ll pass this info on and explain.

Ok, all seemed to go well and works exactly as described, but still getting the following in Firefox under Site Security:
“Your connection is not private and information you share with the site could be viewed by others”

Your site seems to be using Divi theme. Divi uses its own caching mechanism which has to be cleared before all links are updated to https://. See https://really-simple-ssl.com/knowledge-base/mixed-content-when-using-divi-theme/ for instructions. Clearing the Divi cache should give your site the secure lock.

I think the problem might be in the solution/instructions you have provided:
“Then navigate to the ‘Builder’ tab. Select ‘Advanced’ and uncheck the ‘Static File Generation’ option. Finally, press ‘Clear’ to clear the Divi cache.”

If I uncheck ‘Static File Generation’ then the ‘Clear’ tab/option next to it disappears.

Is the mixed content fixer after pressing the clear button while leaving the static file generation option enabled? If so, we will update the article accordingly.

Seemingly not – this is what I did originally (when I found the clear button disappeared) then found that FF still produced the warning mentioned.

Does it work in other browsers? If so, you might have to clear Firefoxs cache. It’s also possible your site uses another caching plugin, if so, that has to be cleared as well.

I have just run the site through ‘Why No Padlock? (thesslstore.com) again and it’s showing up several image errors. Loading the site in Safari shows it as HTTPS, but no padlock is showing.

The site still serves a cached Divi stylesheet containing https:// links. If clearing the cache in Divi didn’t help and clearing other caches also doesn’t work I’d suggest to contact Divi about this issue. The clear cache button should clear the cache and resolve your issue.

Ok thanks – we designed a WP site for a client – who then changed it to this one within a month or so.. So we will just put the ball back in his court with an explanation I think!