Hi gecko_guy,
Thanks for reaching out. It’s a very valid concern indeed. The last thing you’d want is some stale software with a bug waiting to be exploited. At the same time, there’s no guarantee that a newly developed, or frequently updated plugin is free of bugs or security holes.
I believe that this plugin is simple and small enough not to warrant too many updates. It does one thing, and I hope it does it well. For better or worse, it’s not something that you’ll add a ton of features to and get a lively community around. I did build it with security in mind, as you can hopefully see from the documentation and the code. However, I cannot possibly claim that it’s free of bugs or security holes. Just that I haven’t come across any that warranted an update.
I would encourage you and anybody else to look into the code and let me know if there’s any problem worth fixing. It’s open-source and I would love not to be the only one who actively maintains it.
You’re right that I should update and indicate its compatibility with latest versions of wordpress. I’m running it on the latest version just fine. It’s mostly out of lazyness (and slightly to blame svn and the wordpress plugin ecosystem which feels a bit clunky to work with for me).
Hope this answers your questions and concern. If there’s anything else, let me know.
Cheers,
Yoav
Hi Yoav,
Thanks for the very quick reply. I did browse the code in SVN and it all looks fine to me, but it would be nice just to see that it is certified compatible with 4.5+.
If you manage to find a bit of time to get it verified that would be great, although with your reply I will give it a try now anyway.
Best,
Guy
You’re welcome, Guy.
I just pushed an update after testing it with 4.5.2 …
Cheers,
Yoav
If you’d like to help, please test it and vote for its compatibility.
Once you use it, and if you find it useful, would be great if you could also rate it 🙂
yes of course. happy to provide feedback and rating (and if I run into problems will open a support post before rating of course 🙂