Ryan. Reluctantly, I remain.

I finally found the ad I've been referencing for the past 20 years. youtube.com/watch?v=Bzapn4…

Why does the restaurant industry have to add moral and economic theory questions to the total cost of my meal?

Don't sleep on late.sh.

@vinnysgreen Yes.

Wouldn't WordPress be better if they started moving things out of core and into plugins? Like shouldn't comments just be a plugin

@lorianebird The onboard traffic collision avoidance system is really cool and this is an example of it working as intended. Technology is awesome!

HOLY SHIT.

@levisan do you hate fun?

Be the change I wish to see in the world: stop clapping along to every single song at a concert

@MeiDoctor @SybreWaaijer @grok With the exception of the 4th bug, they have all be fixed for nearly 2 years or longer. Are you saying that subscriptions created prior to those bug fixes are still broken?

@SybreWaaijer @grok summarize this for me

100,000+ stores run this WooCommerce plugin. I doubt any of them know their payments are broken. Any store with $1M ARR could be missing $700k+ in revenue. If you run WooCommerce Subscriptions, check your store. Yesterday, I reported a bug to WooCommerce that silently broke subscription payments after a product switch. Then I got worried: if they missed something this obvious, what else did they get wrong? So I started auditing. Within hours, I had found three more bugs. There were 121 affected subscriptions, and $43,274 in lost revenue. Here's what I found. WooCommerce Subscriptions has an internal flag that controls whether a subscription charges the customer automatically or waits for them to pay manually. When a customer checks out with (for example) Stripe or PayPal, this flag should be set to "automatic." If it isn't, subscription renewals silently stop working: no charge is attempted, no failure email is sent, and the subscription goes on hold until the customer notices and pays manually, or doesn't and churns. Bug 1 (stale cache): After saving subscription dates, the order cache was never cleared. Subsequent saves could serve a stale object with the flag still set to its default: manual. Fixed in subscriptions-core 6.9.0. Bug 2 (broken HPOS backfill): Missing getter/setter methods prevented subscription metadata from being properly synced to postmeta in HPOS when data sync is enabled. Fixed in subscriptions-core 6.5.0. Bug 3 (unnecessary re-fetch): wcs_create_subscription() returned a freshly fetched instance from cache/DB instead of the already-configured object. Any unsaved state, including the corrected flag, was silently discarded. Fixed in subscriptions-core 7.1.0. These three combined accounted for roughly 7% of all subscriptions created at checkout that were silently born broken, despite the customer paying successfully. For 7+ years (we have data from 2017–2024). Automatic payments NEVER fired for these subscriptions. Users never got renewal emails, either. The only way to know they were broken was if the customer noticed they lost access and contacted support, or if the merchant audited their database manually. Bug 4 (switch): When a customer upgrades or downgrades their subscription, the switcher flags the subscription as manual renewal; it only corrects the flag if the payment gateway changes. A customer switching plans while keeping the same gateway (e.g. Stripe to Stripe) cements the flag stuck on manual. I discovered this two days ago, when I found a happy customer in the store overview that I had just helped upgrade, with multiple valid cards on file, put "On Hold" because of a missed payment. For years, I've offered to help WooCommerce improve its code quality and performance. I dry-run code: I find bugs by reading. All four of these bugs are clearly visible in the source without needing to use the software. They could have been caught early. They weren't. The incompetence is immeasurable (well, actually, with the diagnostic queries in my next post, it might be measurable). Our store is small. WooCommerce Subscriptions powers hundreds of thousands of stores. If 7% of subscriptions were silently broken across even a fraction of them, we're looking at potentially millions of dollars in spoiled revenue industry-wide that could have been prevented. Perhaps even billions. None of this was disclosed well or at all. No admin notice. No email. No advisory. The fixes shipped under vague changelog lines like "Make sure we always clear the subscription object from cache after updating dates" and "Ensure proper backfilling of subscription metadata." One fix was labeled "Dev" instead of "Fix." Two don't appear in the GitHub release notes at all. No remediation tool or diagnostic query was provided. Store owners have NO way to know they're affected unless they manually audit their database. The woocommerce-subscriptions-core repo was archived in May 2025 after the code was absorbed into WooCommerce core — making the fix history harder to trace. If you run WooCommerce Subscriptions and used HPOS before mid-2024, check your store. Queries are linked in the tweet below.

@theCTO There's WordPress meetups and WordCamps all around the world full of people who love WordPress. Maybe "touch grass" or whatever the kids say.

i know a lot of people that LOVE tech, but... github.com/bullenweg/bull… no one i know loves Wordpress, it's one of these things that "ugh i guess it's the only choice". I've never once used it and not got spammed with plugins advertising their sales, upselling, banners everywhere. the ecosystem is terrible, filled with slop that no one maintains. time for a change.

How about an AI assistant for Debug Bar Console? github.com/ohryan/debug-b…

@jonathan_dejong It’s quite something this technology we’ve created.

@ohryan In reality. I'm saddened that our sysops practises prevents me from experiencing the poop rain 💩

I created a WordPress plugin to destroy all WordPress plugin businesses. Sorry. ohryan.ca/2026/04/01/plu…

@ohryan define( "DISALLOW_FILE_EDIT", true);

@jon_bossenger I was seeing similar too. Even in Claude code itself. I don’t know if you’ll be able to tell an LLM to do a web fetch to update its knowledge via the API. But it’s worth a shot.

@ohryan Ha! Apparently my models aren't up to date with the latest WordPress developments 🤣

@jon_bossenger Nice! It basically works. But might be slightly buggy? Feel free to submit PRs.

@ohryan I have to try it now!

I wrote this post about the vibe coding I've been up to. If things continue to move in this direction, i think there's a near future were most software products are unnecessary. ohryan.ca/2026/03/23/adv…

@levisan Aw shucks.

This is the greatest thing on the internet today

@levisan @acedtect @mollywood Ditto

@acedtect @mollywood We Canadians also say gen zee not zed in my experience (in Alberta and in cyberspace) with zero exceptions

Why is it pfp and not pfpt and if the answer is “profile pic” then why not “prof pic”

@levisan FWIW a lot of system turn this into a proper emdash: OTTOH iOS keyboard, WordPress, and maybe Google Docs (in markdown, its 3). If you see me do it, it’s in protest of the system not doing it for me.

I don’t think I can take seriously anyone who has the knowledge of how to use an em dash properly but lacks the knowledge to type it. Has a Ph.D., still types "--"

@rouchefort73 @brent_bellamy And… croissants?..

@ohryan @brent_bellamy and Crime?..

Welcome to Osborne Village. 🎩 @brent_bellamy

@levisan What kind of restos you eating at! 😱

This was originally composed as a speech-to-text note ending with "…take my dick home"