Strategies for supporting WordPress plugins
Thinking about releasing either a free or commercial WordPress plugin? Read this post by Tom McFarlin on wpTuts+ first, along with the discussion in the comments.
Thinking about releasing either a free or commercial WordPress plugin? Read this post by Tom McFarlin on wpTuts+ first, along with the discussion in the comments.
Joost de Valk posted on his Tumblr, of all things, that their commercial plugins at Yoast.com have undergone a licensing structure change. They’ve changed to yearly based support, and also removed their unlimited site license. They’re hoping to eliminate abuses with the move, and he cites the statistic, “2% of our licenses to be responsible for over 30%…
It always gets my goat when people leave off escaping in tutorials just to make it easier. The code you just provided will be copied and pasted and then you are the cause of bad code out there.
Wordfence is getting into the “forensic” and malware cleaning business for WordPress sites. The service is a pretty logical extension of the plugin, and they’re charging $179 to clean sites, or $120 for Wordfence Pro customers.
What if you want to show hidden information only to “administrators” or “shop managers?” What about displaying a custom “My Account” tab just for logged-in customers?
The First WordSesh was a huge success and we are crazy enough to do it again. We’re currently pulling ourselves together and have begun planning the next event. We hope to have firm dates and additional details for you as soon as possible. Are you ready for more sleepless hours of incredibly awesome and free WordPress presentations?
WordPress 3.6 introduced the Heartbeat API. It’s an exciting API that opens up a whole bunch of possibilities for various core features or plugins, or even themes, to utilize. Pippin Williamson gives a nice introduction and example use case for the Heartbeat API, and Stephen Harris has also completed a three part series for wpTuts+…