Both My Calendar and My Tickets are nearing their next major releases. I just tagged My Calendar 3.5’s first release candidate, and I’m hoping that this means I’m really pretty close to wrapping up this huge phase of development. My Calendar 3.5 My Calendar 3.5 is a big set of changes, and it does include some breaking changes in the HTML (HyperText Markup Language) output. Here are a few of the major changes: In addition to these major features, there […]
Continue reading “My Calendar & My Tickets: Major release updates” »Tag: WordPress
A day of closures
I released two plugin updates that were a bit painful. The first is for WP to Twitter – and has been coming for quite a while. In this release, I removed support forms and all of the promotional materials for WP Tweets Pro, which I’m no longer selling. I think that the reasons for discontinuing WP Tweets Pro are pretty well known at this point; but suffice to say I don’t trust Twitter enough to continue to develop for their […]
Continue reading “A day of closures” »Plugin Vulnerability fixed in My Calendar 3.3.17
This morning, I was alerted to suspicious activity in server logs referring to the My Calendar print view by a concerned user. Checking the data, it was clear that there was a significant security issue in My Calendar which was being used to generate links out to remote sites by abusing the referrer URL (Uniform Resource Locator) in the My Calendar print view. This security issue was fixed in version 3.3.17, released this morning. The issue would not impact any […]
Continue reading “Plugin Vulnerability fixed in My Calendar 3.3.17” »The real added costs of accessibility
For many years, I’ve seen repeated – and have myself repeated – the idea that an accessible website is not more expensive. That idea comes with a notable caveat. That caveat, to sum it up, is that it is not more accessible to build an accessible website from scratch than it is to build an inaccessible site from scratch. Building from scratch. When was the last time you built a website from scratch? What does it mean, in 2022, to […]
Continue reading “The real added costs of accessibility” »Don’t judge progress by the number of open issues
Recently, I’ve seen more than one person in the accessibility community sharing Tweets about the number of accessibility issues in the Gutenberg repository. The increase in issues over the last few years is presented to show that WordPress is not considering accessibility. Specifically, I’m referring to comments by Adrian Roselli & Dennis Lembree: There are plenty of legitimate reasons to criticize the accessibility of Gutenberg. Progress on accessibility has been inconsistent at best. This is heavily influenced by the lack […]
Continue reading “Don’t judge progress by the number of open issues” »