How an art history lesson will help you be a better judge of what plugins are safe(r) to install on your WordPress site.
If you can’t obfuscate your code, or have an API just to check a license, how are you supposed to earn any money with a plugin in the WordPress repository? Stop thinking about hiding your code and start extending it.
Third Party code in your plugins are great, but you have to know what you’re getting in to, be willing and ready to support it, and know how to secure it. So. Do ya, punk?
A weekend spent sorting out ColorBox and how to bring a gallery into the 2010s.
No one app can do it all, and don’t take it personally when it doesn’t. You can please some people sometime, but you cannot please all the people all of the time, after all.
There are some pretty basic things done wrong when calling js files in WordPress plugins. Let’s fix that.
Extending Mark Jaquith’s “I Make Plugins” plugin to work with Custom Post Types.
Add a link to Jetpack’s ‘Stats’ in your per-site menu on the toolbar.
Not quite everything, but it’s better than functions.php!
The risk of keeping a public list of all ‘naughty WordPress plugins’ does not outweigh the benefits of having such a list.
Yourls? Myurls! It’s easy, it’s painless and it works.
There’s just one problem with this. Plugins exist for a very good reason: to add non-core functionality 1 to your site without hosing up the whole lot. Via “Without a plugin” considered dangerous | sabreuse