Forces change to HTTP after deactivation

Hi @strategicsys,

this has been done to make troubleshooting SSL issues easier, as it allows to quickly revert to http in case of an issue. The deactivate link in the plugins overview explicitly states ‘revert to http’. The plugin can be deactivated while keeping SSL by pressing the ‘Deactivate and keep SSL’ button in the Settings->SSL->Settings menu. In an upcoming update the deactivate link in the plugins overview will show a modal which will let you choose to revert the site to HTTP or keep HTTPS.

Mark

You cannot assume that I’m uninstalling the plugin for the reason of troubleshooting anything. I might be uninstalling it just because I don’t need it anymore. It should not be modifying anything at deactivation, except maybe its own settings — NOT the core settings.

Yes, I did see that that deactivation link explicitly states “revert to HTTP”, and I explicitly do NOT appreciate that it takes upon itself this role.

I may have installed it just to try it out, and maybe my site already had HTTPS in site URL. It is extremely unacceptable that when I decide to uninstall it, it takes upon itself to change my core settings. ESPECIALLY upon uninstallation! What if I hated the plugin and just wanted to get rid of it? Breaking things for daring to uninstall it is a coercive tactic to keep from uninstalling it (or else). Luckily I knew exactly how to fix my site URL. A bunch of other site owners wouldn’t know any better.

@strategicsys,

For your use case we have the option “deactivate and keep https”. To prevent issues like yours, we have labeled the plugin deactivation link “deactivate (revert to http).

When the plugin first started, I had angry users who complained the plugin did not revert the site back to http. Now we have angry users because the plugin reverts the site to http.

So we decided to make this as clear as possible, and make the deactivation button the most used choice: a reversion to http.

Different users have different wishes. Because most users who want to uninstall, want to revert to http (see for example the last support question), this is the default. The plugin restores the site as it was before the installation.

For users who do not want this, we have added this second option: deactivate and keep https.

As you can see, we do not assume anything, we just offer two options, both are clearly described
– deactivate (revert to http)
– deactivate and keep http.

I don’t see how we can make this any clearer.

For anybody who doesn’t know how to fix this, we’re always stand by to help, and can help fix such in issue in minutes.

With all due respect, I understand the struggle. However, I still have issues with what you’re saying:

– It’s NOT as clear as possible. In order to find the other option, I have dig in the settings (and frankly, I had no reason to know I had to dig there to find the gracious option of letting me keep my original site URL settings). I would understand if the two options were right next to each other, I could select between the two.
– “Revert to HTTP” explicitly assumes that HTTP was the “original” state. So the “plugin restores the site as it was before the installation” is actually false. If the plugin actually kept track of what the original state was and restored to THAT, then you could say it’s “reverting”. Right now, it simply forces the arbitrary “default”.
– “can help fix such in issue in minutes”? Come on, really? You don’t have to get down to that level. Obviously, you can’t help each and every free user with every hiccup, let alone “in minutes”..

I understand that you have to deal with different wishes and that a 1-star review stings, but I think owning up to these issues (and maybe even fixing them?) may be a better strategy than being all defensive and blaming the messenger.

https://mncollection9.epizy.com

@strategicsys as a matter of fact we do help each free user with issues. Every support request, free or premium, gets answered pretty fast. If it’s night here it may take a few hours to respond.