The support forums here at WordPress work great! I try to respond to them at least once a week. Also, I responded to your email, which I don’t normally do for support.
But still no update for the error? You’re defending your plugin and support, and we still don’t have an update that makes your plugin useable for WP 4.3
Jeff….with all due respect….I will have to agree with bluedotproductions. I must admit I felt in love with your plugin, but currently I´m using another that does the complete logistics.
And yes, indeed, WP 4.3 threw you off. So let´s get to work on fixing such a wonderful piece of code.
You go, Jeff.
With all due respect to both of you, a version incompatibility is an incomprehensible reason to rate the whole of a long-standing plugin as 1 star.
Is it fixed yet jeff? Or are you just defending comments?
Really, if you don’t want to fix it….which is what you said earlier, just admit the plugin is dead so we can move on.
I feel this is an emotional reaction as you defend a broken plugin. I appreciated your plugin, but it broke a site with 28k users that couldn’t get their password retrieval. And thats just 1, and you have 1m downloads. Running a website, I don’t have time for the vagaries – I have to have it run.
So yes, 1 star shows it’s broken and you don’t want to fix it.
Did you not read the bit saying “Compatible up to: 4.2.4” before breaking your site?
Johathan….you sound like a lawyer in a criminal trial that will take sides with the criminal just because of technicalities in the case and not for the damage done.
LOL… Tony, the damage done here sounds more like an error of the webmaster than the author of one plugin he uses.
If he updates the core and does not check at all if the dependencies work (no matter what it says it is compatible with, but on top of that, it was clearly not much tested with the latest WordPress), then you are playing with fire!
If it is really a 28k+ users website, then you have to manage your upgrades a better way. Of course, you cannot re-test everything efficiently. But hoping nothing will break sooner or later and have no revert plan, and then blame the others, then you are a big reason of the problem, and you have to learn to be a bit more prudent, or develop the skill to be able to fix, revert, or whatever (or at least have access to a ressource that does).
Plus, it only affected the password retrieval part, and not the login/registration if I understand what you guys said. Maybe it is a feature widely used, but that is not the main one and you can always do a quick fix until your _dependencies_ adjust.
bluedotproductions make me laugh when he said “I feel this is an emotional reaction as you defend a broken plugin.”… if someone react emotionally here it is you, since you react after you found out a part is broken.
The author is right in saying that the purpose of review is to rate the plugins itself, and not a reaction to a punctual problems, but we are not gonna make people smarter or understand that as it is pretty common to do this. You have an issue, communicate, wait, and see. Reacting that way won’t do any good to no one. C’mon…
And due to timing, I switched plugins and moved on. I would rather pay for a plugin that stays current than a free one with a slow upgrade cycle. It’s good for people to know this authors approach and response, and hence I reviewed. But after this diatribe, it would have been easier to have said nothing, and not helped other mission critical sites. Naw. I’d do it again. 😇
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Off topic for a moment…
@bluedot, You should only have one account on the forums, which means one will be made inactive. Which one would you prefer to keep active?
This account is fine Andrew. Sorry for any confusion.
