We admit we didn’t take enough precaution here and issued an update that broke backwards compatibility a bit too swiftly, and we apologize.
Please see this post for more details.
Thread Starter
Saturn
(@asaturn)
No big deal — not far beyond what to expect when updating 2+ year old code. Nothing is free forever 🙂 Just wanted to warn people who may be looking to update.
I now have a new checklist item before I do any updates — check the 1* ratings to see if anyone has posted about problems with the upgrade. What these guys did with this hijack is totally unacceptable!
Thread Starter
Saturn
(@asaturn)
soulgeekguru note that this isn’t a “hijack” in that someone stole the name, but a hijack in that the old developer and a bunch of new ones got together and used the original product’s name for a completely different thing… this is what screws up installs. see my link if you want the latest version of the old plugin.
I;m sorry you feel that way. Really the only thing that was changed was the UI, all of the functionality of the plugin should be the same as the old one. As posted above we did learn a lot from this experience and will have a better idea how to handle situations like these in the future.
If you have feedback or suggestions you can always let us know on the forums and we will be glad to talk about it with you.
Thanks!
