Effective immediately, all licenses for WP Tweets PRO and My Calendar: Submissions, as well as my future premium plug-in projects, will be sold on new license terms. The new license terms are compatible with the General Public Licensing model (GPL (GNU General Public License)). Until today, all licenses I sold were based on restricting the number of sites you could use the software on: either a single site license or a multi-site license. The new license removes that restriction, and […]
Continue reading “Software Licensing Change” »Author: Joe Dolson
The Headings Hierarchy Challenge
TL;DR: Headings are super-important. There are many reasonable models, but consistency is more important than either choice. Working in an environment like WordPress, control over those models is limited.
Continue reading “The Headings Hierarchy Challenge” »Good Coding Habits for Accessibility
This is the written version of my talk at WordCamp San Francisco 2014. Watch the video at WordPress.tv. Do you think web accessibility is hard? You’re right. Web Accessibility is hard in the same way that everything else in development is hard: designing and building any perfect product is always tough – even impossible. But getting 90% of the way there is easy. But I’m an advocate for practicality. So don’t set perfection as your goal. Just make things better. […]
Continue reading “Good Coding Habits for Accessibility” »Security Update for WP to Twitter
On September 8th, the web site Vexatious Tendencies disclosed publically a security flaw in the WP to Twitter “Tweet Now” functionality, introduced in version 2.9.0. The security flaw would allow unauthenticated users to post to the administrator’s Twitter account. See WordPress plugin vulnerability dump, part 2 for more details about the vulnerability. This is a severe vulnerability, and you should update as soon as possible. If you are still running a version of WP to Twitter older than 2.9.0, you […]
Continue reading “Security Update for WP to Twitter” »The damage of examples
These are lies we tell: “This is just an example.” “This is a demo, not for use as production code.” No, it’s not. You’re wrong. It may not be code you, the author, would use in production. But as soon as you published it, the likelihood that it will become production code in somebody else’s project skyrockets. And this is inevitably damaging. These examples can be horrible in many ways – reliability, portability, security – and accessibility. In a surprising […]
Continue reading “The damage of examples” »