Latest update destroyed login

Hi,

I am very sorry that this happened to you.

Removing a component from the main plugin does not destroed the site, just access to the admin panel becomes the default.

In addition, we warned users that it is worth overloading the component that hides the login page and highlighted this warning in red.

However, on some sites that have the plugin Really simple ssl, there could be unforeseen conflicts. Even if we remove our plugin, access to the site may be lost, but I’m currently looking for the cause of this conflict.

I’m sorry, unfortunately I myself am very upset that this update had a lot of problems.

I will try to fix everything in the nearest minor updates.

Best regards, Alex

If you still face a problem. You can try this solution:

Try simply deactivating Really simple ssl by following these instructions:
https://really-simple-ssl.com/knowledge-base/uninstall-websitebackend-not-accessible/

After that, go to the admin panel of your site and activate again, Realy Simple ssl. The problem should be solved.

Best regards, Alex

“Removing a component from the main plugin does not destroed the site, just access to the admin panel becomes the default.”
This is factually wrong. Login was impossible after your plugin changes!

“we warned users that it is worth overloading the component that hides the login page and highlighted this warning in red”
This has nothing to do with the plugin flaw and harmful business decision of the plugin maker that I reported. Besides, “overloading the component” requires guesswork what you might mean.

“Really simple ssl” No we do not have that plugin “really simple ssl” because real ssl is much simpler than adding a plugin for that, tsss.

“unfortunately I myself am very upset that this update had a lot of problems.”
Appreciated that you admit it. I suggest not to make “updates” that corrupt sites of users that had installed your plugin, instead sell those as UPGRADE.

Either way, what plugin authors normally do if they want or have to turn some functionality into a separate plugin, is, they prompt in RED *before* someone CAN update the plugin. You did not, as mentioned “There was no warning message upon updating, so I credulously proceeded”.

Whatever, mistakes can happen, and you admit it was one, so let’s forget it. Please think: Does the distinct login url really justify an extra plugin???
Why didn’t you leave such a tiny feature within the core plugin?
Be aware that any webmaster other than a noob DOES ALL HE/SHE CAN TO AVOID AN ADDITIONAL PLUGIN.

Hi,

I want to share with you my ideas for the development of the plugin. We want to make a constructor, that is, a plugin that will be built from modules. For example, you use as a webmaster, only the components you need (Hide’s login paget, Assets manage, Update Manager). And now, imagine that there will not be any extra functions and components in your plugin and you will be able to build them, just what you need for optimize.

Now we just excluded the components Hide login page, because this function is available in almost all plugins to protect WordPress and is rarely used.

But when we finish the work on optimization builder, you can build your plugin from the functions you need.

I promise to you that we will no longer make such abrupt updates and we will better test the plugin. At this point you can install the component as a regular plugin.

Best regards, Alex

I would like to express my respect for your professional and friendly attitude, Alex. Thank you!
Other plugin authors post false excuses when users say what doesn’t work, but you actually READ and CONSIDER what users write. Kudos to you!

“We want to make a constructor, that is, a plugin that will be built from modules.”
Hm, I always felt your plugin is already a “constructor”, if that is the term. For me, that’s what “Components” in your plugin is.
My impression however is that
– before, hide login was a core part, now it’s gone (in a separate plugin, it seems)
– and the “components” always allowed to activate/deactivate individual parts WITHIN the plugin (without installing separate plugins).

At least that was, and is, my understanding of the plugin, lol.
What is really funny is, you say “Now we just excluded the components Hide login page, because this function is available in almost all plugins to protect WordPress and is rarely used.”, but you removed the component and created an EXTRA PLUGIN just for that tiny thing (so you think it is).

Also note that “smart” users do not install ANY plugin that is absolutely considered helpful or needed. So arguing “this function is available in almost all plugins to protect WordPress” (if true at all??) isn’t wise: users DON’T want to install two plugins that widely overlap. If you think it’s basic functionality then leave it in, unless you want that users choose another plugin over yours altogether. Just my 50cent.

Again, thank you very much!!