Ozh has always been a good guide in helping plugin authors get their coding right. In his article, Ozh has highlighted some very common errors / bad coding exercises that are present in a lot of plugins. As a plugin author, I must admit that I am guilty of some of these mistakes, but am constantly working towards improving and bettering this.
If you’re a plugin author, I suggest you taking a look at your plugins and seeing how you can improve them to make your plugin more secure, compatible and cleaner to use
… asks Jeff. The recent security issue with WordPress isn’t the first and I am sure it won’t be the last. But, does this mean you should abandon WordPress? Well, I don’t see any reason to do so. In fact, almost every software I have seen has its share of bugs which cause minors problems to major attacks and disruptions of your site.
There was a time when you had to monitor the WordPress Dev Blog to find out when a new version is released. And, then the process of upgrading was extremely painful. WordPress 2.7 changed all of that. You now get a notification and even a few-clicks upgrade. So, why are you still running that old version of WordPress?
Ekin has published a simple cheat sheet, that can serve as a quick reference for plugin and theme authors. Available in PDF, you can print it out and keep it by your side while you code.
Again, fed up of the frequent WordPress releases? Jeff has some observations about the past releases and pointers about what the WordPress team can do to smoothen the release.
Points he talks about are better release posts, WordPress threat levels and email notifications.