There are some very good (and some funny), recent Twitter threads here full of people sharing their “WordPress stories.” Thanks to John James Jacoby for asking! 😄
Once you know these states, you can assign probabilities of transitioning from one state to another (someone hacks your account and locks you out, you forgot your own password, etc.) and then build optimal security and reliability to deal with it. It’s a truly elegant way of conceptualizing the problem.
John James Jacoby has released WP Spider Cache, and it looks really great. Specifically, he’s done some work to cater it for use with Jetpack, WooCommerce, EDD, BuddyPress, bbPress, and in networks. Definitely check it out.
bbPress 2.6.0 is out after only six years (years?!) of development. John James Jacoby explains the reason for this timeframe was mainly because there are only far “less than part-time folks” actively working on the project. bbPress is installed on “over 300k sites, each with their own thousands of users.” This release addressed 420 tickets…
Join WP core contributor and developer John James Jacoby for this live coding workshop on Friday, June 26, from 1-3 p.m. Central. JJJ will walk through best practices and steps for building your first WordPress plugin. JJJ is co-author of Professional WordPress Plugin Development (2nd Edition) and will be joined by fellow authors Justin Tadlock…
John James Jacoby released the initial version of BerlinDB, a “collection of PHP classes and functions that aims to provide an ORM-like experience and interface to WordPress database tables.” John touched on these concepts in his talk at WordCamp Europe about advanced database management for WordPress plugins. 🔌
We’ve seen forced updates become increasingly common and less controversial over time. But who decides, and how is that decision made? Are there unofficial channels and processes, like a decision tree, for escalating to a forced update?