It was a great run, but this plugin never got the momentum. Since it’s so small and barely used, I’ve retired it so I have less to support.
You can download it from GitHub and you’re free to fork as you like. The code is perfectly safe.
]]>Just noticed this isn’t working for us again, but not sure when it stopped. Has it been tested recently? (Funny this is the same as last support topic but it has been working great since then… also funny, the particular imposter name we are having trouble with is Mike)
]]>Just noticed this isn’t working for us again, but not sure when it stopped. I tested with all plugins deactivated and Twenty Twenty theme. Has it been tested recently?
]]>Mika and Scott,
I have rewritten this plugin as I liked it but I found it limitting.
Basically instead of exiting on wp_die my approach is to mark the comment as pending (flagging it as a potential imposter comment), then redirect the visitor to the login page (with a message), then on login autoapprove the comment.
My question to you both is whether you would prefer I contribute the code to this plugin or create my own fork?
Pete
]]>Hello, this plugin worked fabulous for us until recently. Each time I test it, in three different browsers, it works. However I continue to have users post as Anonymous. I can’t figure out how some users are getting by the check. Our site has a lot of comment activity and we allow users to post without logging in, so this plugin is awesome at helping multiple users not user the same nicknames. Any suggestions? Here is our site: https://wp.me/P2in2v-44B
]]>I recently upgraded to 3.7, and I think it broke this plugin. It no longer blocks names from being used. I know it hasn’t been updated in awhile, but any suggestions for fixes? I’ve tried to locate changes in the core files, but was unsuccessful. I found this plugin to be useful and hope it works again.
]]>I tested the plugin and it works (non-WPMU).
I’m not sure if it’s WP default behavior or because I have ‘cookies for comments’ plugin activated, but without Impostercide, the spoof comment went to Spam. With it activated, it went to your notification message.
Unless my blog is set to auto-approve comments, I’m leaning toward thinking it’s better to deactivate this plugin because a really clever hacker-type person could figure out which username and/or email address(es) are registered on the blog. Then all they have to figure out is a password.
I’m not saying it’s easy to do that, but I think I’d rather let it go to Spam and not “give them a hint”.
Even if I did auto-approve comments, apparently it would still end up in Spam and not be approved.
I think the plugin should have a backend configuration that allows the notification message to be edited. Then I would have a bit friendlier message (never using the word Imposter) and wouldn’t be as specific about the reason for the error. And, ideally, it would all happen on the same page, but that’s not necessary.
Just sharing some thoughts. Appreciate your work on the plugin.
]]>