@emiubaldi totally agree, if there was any clear reason as to making such a change, an announcement, a fork of the plugin or basically whatever it would have been clear and we all would not even be here talking about it.
Not sure why they went about it like they did, but in the world of wordpress, you can have a loving support base as long as you are always transparant on why, how etc. There are enough examples in the history of wordpres where plugins, just decided to change things without prior notice or change owners and then things went a different route an all.
I’m all for calling a spade a spade, own up to everything you do .. if its bad, if its good.But if this was tested, I can not imagine this was not found out before. And sure there might have been a mixup or something … but if you see people noting all the same issue, and some even went out of their way and have looked into the code just a bit, noting having to test this on a staging site … well it is simply out of the scope of what is occuring.
Dont get me wrong I love the initial plugin for all it has done in the past and probably will continue to do in the future. But I just find it outright absurd what was pushed as an update here. So I do hope there is some form of explanation as to what happened. Because this last update experience simply put was a bad experience for probably a reasonable percentage of the install base.
As a developer, you have to earn the trust of user first to get them to use your plugin.code. And along the way people will most likely remember your missteps more then what you have done right when it comes to releases. All I’m complaining about I guess is … come clean, own up the misttake, dont sugar coat it. Because that will restore trust better then anything else.
Anyway as noted hope, they can clear up what happend and / or why. And let’s hope the plugin keeps it original functionality as that has been wonderful for years.
