Conversation
supportJust noticed your plans to sunset this light weight plugin in the coming months and I have to ask why? Is it just to drive traffic into the full blown Wordfence plugin? Because that will bite you hard. We use Wordfence Login Security throughout a number of site because we simply want and need the 2FA in specific. We will not replace those setups with the full blown Wordfence but rather replace it with another plugin to help us do the same simple task, without the overhead from the full blown plugin. Please reconsider this and keep maintaining this light weight solution to a problem that should already have been fixed in WordPress Core, for all of us that do not need the full blown Wordfence to handle this task.
Hello, @noboxjoakim Thanks for the feedback. We currently offer all of our 2FA and login security functionality in the primary Wordfence Security plugin ( https://wordpress.org/plugins/wordfence/ ). Setting up the Wordfence Security plugin will automatically carry over all 2FA entries from the standalone Login Security plugin. If at any point you are interested in setting up the Wordfence plugin to focus more on login security, we offer a guide to adjust some of the Wordfence features in our documentation here: https://www.wordfence.com/help/advanced/tuning-wordfence-resource-usage/ Thanks, Scott
Hi Scott Wordfence can not be used on Pressable and we relied on Wordfence Login Security on all of our sites, so we will not be able to use either and that’s a major issue. There will be a lot of other users affected as well. Regards.
@wfscott Either you did not read the initial post or you just don’t want to understand it, pick your preferred choice. It is not a choice of installing full blown Wordfence. That is not an option. Wordfence Login Security will be replaced by another light weight 2FA plugin and this sunsetting is causing a whole heap of issues considering that we spent a couple of years pushing for and documenting this solution due to it being light weight and well functioning, solving this specific issue without the overhead of Wordfence as a whole. We have multiple other solutions to handle what Wordfence does but without adding that bulk to every WordPress install we handle. Forcing the full Wordfence plugin to be able to continue using 2FA is just absurd and completely out of the question for our use case. And I am pretty sure that this will be a fact for a lot of other users as well. Please reconsider this move, it is not the fantastic strategy for pushing users into Wordfence that you seem to think it is.
Please, reconsider the sunsetting of this plugin. It is the best 2fa plugin for WordPress, by a lot. Probably the only one that allow regular users to set two factor via the frontend. Large user base, thousands of sites already depending on it for a critical component. I suspect that most of them can’t move to the full plugin. From a marketing perspective, it can be a great on-ramp to the full Wordfence plugin. Also from a marketing perspective, the move, unsurprisingly, hasn’t been well accepted by the community.
I’d like to respectfully add my voice to this thread, as I believe it reflects a legitimate concern shared by many users. Wordfence Login Security has been a perfect tool for those of us who need 2FA functionality without adding extra layers to our sites. Its value lies precisely in its simplicity and focus. I understand that consolidating products may make sense from a business perspective, but from a user standpoint, this decision brings real problems: — Sites that already have firewall or scanner solutions would be forced to deal with conflicts or duplicated functionality. — Performance can be affected on shared hosting or heavily optimized sites. — The configuration overhead of the full plugin is significantly higher for those who only need 2FA. A possible middle ground could be keeping Wordfence Login Security in maintenance mode (security updates only), or offering a “2FA only” mode within the full plugin that disables everything else. I hope the Wordfence team takes this feedback into account. The community using the lightweight plugin is loyal precisely because it values that approach. Losing them would be a step backwards.
Like frankly all of the above people have noted, Wordfence Login Security is something I would and do run on every possible install. Wordfence Security the main plugin is not. And that all boils down to; WFLS is lightweight, Wordfence main in all essence simply is not. WFLS has been tested and working in countless situations, Wordfence main has always had a love/hate relationship with multiple plugins/setups. And dont get any of us wrong here we for sure love the current offering WLFS does, look at the 70K+ installs, it’s a testament you have something great there, why abandon that? If this sunset does go through, I hope someone forks this and can maintain it with security updates. If that is not the case, which I dont hope, for me and all installs I handle that means goodbye Wordfence all together. Please reconsider.
Chiming in here as well, I use this plugin on quite a few websites that just need the 2FA, not a whole security suite, mostly because we fully manage the hosting environment and close down file edits etc. So for me, this plugin just works. Please I would like you to reconsider closing down this plugin as well. If that is not happening, I will probably try to fork this plugin.
Hello, @noboxjoakim Thanks for the feedback. We currently offer all of our 2FA and login security functionality in the primary Wordfence Security plugin ( https://wordpress.org/plugins/wordfence/ ). Setting up the Wordfence Security plugin will automatically carry over all 2FA entries from the standalone Login Security plugin. If at any point you are interested in setting up the Wordfence plugin to focus more on login security, we offer a guide to adjust some of the Wordfence features in our documentation here: https://www.wordfence.com/help/advanced/tuning-wordfence-resource-usage/ Thanks, Scott
Hi Scott Wordfence can not be used on Pressable and we relied on Wordfence Login Security on all of our sites, so we will not be able to use either and that’s a major issue. There will be a lot of other users affected as well. Regards.
@wfscott Either you did not read the initial post or you just don’t want to understand it, pick your preferred choice. It is not a choice of installing full blown Wordfence. That is not an option. Wordfence Login Security will be replaced by another light weight 2FA plugin and this sunsetting is causing a whole heap of issues considering that we spent a couple of years pushing for and documenting this solution due to it being light weight and well functioning, solving this specific issue without the overhead of Wordfence as a whole. We have multiple other solutions to handle what Wordfence does but without adding that bulk to every WordPress install we handle. Forcing the full Wordfence plugin to be able to continue using 2FA is just absurd and completely out of the question for our use case. And I am pretty sure that this will be a fact for a lot of other users as well. Please reconsider this move, it is not the fantastic strategy for pushing users into Wordfence that you seem to think it is.
Please, reconsider the sunsetting of this plugin. It is the best 2fa plugin for WordPress, by a lot. Probably the only one that allow regular users to set two factor via the frontend. Large user base, thousands of sites already depending on it for a critical component. I suspect that most of them can’t move to the full plugin. From a marketing perspective, it can be a great on-ramp to the full Wordfence plugin. Also from a marketing perspective, the move, unsurprisingly, hasn’t been well accepted by the community.
I’d like to respectfully add my voice to this thread, as I believe it reflects a legitimate concern shared by many users. Wordfence Login Security has been a perfect tool for those of us who need 2FA functionality without adding extra layers to our sites. Its value lies precisely in its simplicity and focus. I understand that consolidating products may make sense from a business perspective, but from a user standpoint, this decision brings real problems: — Sites that already have firewall or scanner solutions would be forced to deal with conflicts or duplicated functionality. — Performance can be affected on shared hosting or heavily optimized sites. — The configuration overhead of the full plugin is significantly higher for those who only need 2FA. A possible middle ground could be keeping Wordfence Login Security in maintenance mode (security updates only), or offering a “2FA only” mode within the full plugin that disables everything else. I hope the Wordfence team takes this feedback into account. The community using the lightweight plugin is loyal precisely because it values that approach. Losing them would be a step backwards.
Like frankly all of the above people have noted, Wordfence Login Security is something I would and do run on every possible install. Wordfence Security the main plugin is not. And that all boils down to; WFLS is lightweight, Wordfence main in all essence simply is not. WFLS has been tested and working in countless situations, Wordfence main has always had a love/hate relationship with multiple plugins/setups. And dont get any of us wrong here we for sure love the current offering WLFS does, look at the 70K+ installs, it’s a testament you have something great there, why abandon that? If this sunset does go through, I hope someone forks this and can maintain it with security updates. If that is not the case, which I dont hope, for me and all installs I handle that means goodbye Wordfence all together. Please reconsider.
Chiming in here as well, I use this plugin on quite a few websites that just need the 2FA, not a whole security suite, mostly because we fully manage the hosting environment and close down file edits etc. So for me, this plugin just works. Please I would like you to reconsider closing down this plugin as well. If that is not happening, I will probably try to fork this plugin.