How to undo all the actions carried out by this plugin?

Yes, that is accurate. Please note that reverting all changes will effectively revert your site to http. So in your case, I would not recommend to choose the option to revert all changes: you don’t want your home_url to get changed to http for example.

In this situation I would recommend to use the option “deactivate, but keep https”. If you don’t activate the .htaccess redirect, there won’t be other changes on your system than the home URL. In this case it will deactivate the plugin, but lets the home URL in settings/general stay on https.
There’s one exception to this: in some cases the plugin inserts a snippet of code in the wp-config.php. You can remove this manually in that case.

For more information, see this article on manual deactivation:
https://really-simple-ssl.com/knowledge-base/when-the-built-in-deactivation-does-not-work-manual-uninstalling/

OK thanks for the info. I have some follow-up questions. It sounds like you’re saying that, if I use the plugin to help fix/troubleshoot my mixed content error, that I’ll in-turn need to keep the plugin installed on my site–removing the plugin will cause issues. Is that correct?

If with issues you mean that you get mixed content issues, that is probably correct: If installing it fixes the mixed content, removing it will return the mixed content issues again.

Thanks for your help so far.

>> If with issues you mean that you get mixed content issues, that is probably correct: If installing it fixes the mixed content, removing it will return the mixed content issues again.

Sorry, my mistake–that’s not what I’m describing. I’ll try to explain better. My site has been fully migrated to https and for the past 3 years has had no issues. This week it has suddenly began displaying one mixed content error. I was hoping to install your plugin to help me troubleshoot the cause of the mixed content error, so I could in-turn remove your plugin and resolve the issue myself. It sounds like if I install your plugin, then run it (via ‘Go ahead, activate SSL!’), then remove your plugin (via Dashboard–>Plugins), then my site will suffer from additional issues. Specifically, removing the plugin will revert my site to http, which is of course undesirable. That is what I have understood from this thread so far. Is that accurate, or have I misunderstood something?

Yes, you have misunderstood ??

If you follow my advice, and use the “deactivate but keep https” option, your site will not revert to http, and all changes will still have been reverted to the current state.

Two possible exceptions:
If you have enabled the .htaccess redirect option in the settings, and you want this to get removed (which is unusual), you can deactivate this option before deactivating.

If there a fix is inserted in the wp-config.php and you want to remove this (which is also unusual), you can remove this manually. As your site is already running on https, this fix probably won’t be needed, in that case this part does not apply.

OK thanks for that. Let me be sure I understand. If I use the “deactivate but keep https” option, that will deactivate the plugin, my site will not revert to http, and all changes will still have been reverted to the current state. Will I then be able to remove the plugin from my site without issue?

Taking into account the mentioned possible two exceptions, yes. The article I mentioned earlier lists all changes the plugin might make.

OK thanks for all that. I have one final follow-up question. Let’s say I install and run your plugin, and it manages to resolve the mixed content error on my page. Will I somehow be able to get specific details about the exact fix that was implemented? Or will the mixed content error just be gone, without any insight as to what exactly the error was or how it was resolved? I see that there is a ‘debug’ option in your plugin settings. Might that contain the information about the mixed content error fix?

Thanks.

The Really Simple SSL mixed content fixer will only replace internal links to https://, it won’t replace any external images and scripts.

If you want to know the exact cause of mixed content I’d suggest to check out this article which details how to locate and track down mixed content on your site: https://really-simple-ssl.com/knowledge-base/how-to-track-down-mixed-content-or-insecure-content/. You can then compare the results with the mixed content fixer disabled and enabled, that should let you know what has been fixed. The debug log won’t provide any insight into what links have been fixed exactly.

>> The Really Simple SSL mixed content fixer will only replace internal links to https://, it won’t replace any external images and scripts.

>> The debug log won’t provide any insight into what links have been fixed exactly.

OK understood.

>> If you want to know the exact cause of mixed content I’d suggest to check out this article which details how to locate and track down mixed content on your site: https://really-simple-ssl.com/knowledge-base/how-to-track-down-mixed-content-or-insecure-content/.

Got it. I’ve unfortunately tried all the troubleshooting steps mentioned in that article, and still can’t seem to make any headway with tracking down this particular error. That’s why I was hoping your plugin might be able to work some magic and shed some light on the issue. But since you say the plugin replaces only internal links to https, then I don’t think your plugin will be of much use in this case.

FYI the exact error is:

Mixed Content: The page at 'https://www.horizonhomes-samui.com/zh-hans/' was loaded over HTTPS, but requested an insecure font 'https:'. This request has been blocked; the content must be served over HTTPS.

(screenshot). The file/line number referenced in the error is simply the first line of my source code, which isn’t very illuminating.

Hi,

in my previous reply I stated that the mixed content fixer will only replace internal links, this is not entirely correct. The mixed content fixer will also replace external links to https://, as long as they have the src=” attribute. Possibly the https: is inserted by a CSS file or script, these are often inserted by a theme or plugin. To test if this is caused by a theme or plugin, try to temporarily switch themes and disable plugins one by one to see if that resolves your issue. If it does, you know what’s causing it.

Mark

>> To test if this is caused by a theme or plugin, try to temporarily switch themes and disable plugins one by one to see if that resolves your issue. If it does, you know what’s causing it.

Ah yes, forgot about those tests. I switched to my parent theme and the issue was no longer present. So it looks to be something about my child theme. That at least narrows it down. I’ll continue to work on it myself.

Thanks for everything. We can consider this resolved.

Mixed content means there are some part of your websites still “invoking” content over http which isn’t defined by the base URL of your WordPress.

It could be for instance a line you added in your theme header through the editor in which case no plugins would be able to alter this.

We have written a short and yet concise guide on how to set up a SSL and thoroughly check the errors you may face:

https://www.host-stage.net/blog/make-wordpress-redirect-to-https-the-right-way/

And it seems that the plugin you are using is a great shortcut.

• This reply was modified 6 years, 4 months ago by hoststage.

>> Mixed content means there are some part of your websites still “invoking” content over http which isn’t defined by the base URL of your WordPress.

>> It could be for instance a line you added in your theme header through the editor in which case no plugins would be able to alter this.

Yep, I understand all that. It’s just that tracking down this particular http call is proving difficult.