Author name: John

Open Channels FM: Shaping Data Sovereignty and Internet Resilience

In recent years, the concept of data sovereignty has become increasingly important. As more countries introduce or tighten regulations around where and how data must be stored and protected, companies serving the global internet community face a unique set of challenges. These regulatory requirements force hosting providers and infrastructure companies to think not just about […]

Open Channels FM: Shaping Data Sovereignty and Internet Resilience Read More »

Uncategorized

Stop Losing Sales: How to Add a WooCommerce Cart Reserved Timer

The most frustrating part of running a WooCommerce store is watching a customer add a product to their cart only to disappear at the final second. You did the hard work of getting them to your site, but you miss out on the sale. When shoppers leave your products sitting in an open tab, they often get distracted and forget why they wanted them in the first place. This leads to a high cart abandonment rate that leaves money on the table. I recommend solving this by adding a ‘Cart Reserved’ timer. This simple tool gives shoppers a gentle nudge by letting them know their items are safe for a limited time. In this guide, I’ll show you how to use a cart timer to reduce abandonment in WooCommerce. Quick Summary: To add a cart timer to WooCommerce, enable the ‘Cart Reserved Timer’ module in the Merchant Pro plugin. You can then set a timer duration and choose an ‘Expiration Action’ like clearing the cart to keep your inventory moving and your customers focused. Here are the topics I will cover in this tutorial: Why Use a Cart Reserved Timer in WooCommerce? Step 1: Install and Activate the Merchant Plugin Step 2: Change to the Classic WooCommerce Cart Step 3: Enable the Cart Reserved Timer Module Step 4: Configure Your Reservation Rules Step 5: Styling the Timer to Match Your Brand Step 6: Testing the Merchant Experience Bonus Methods to Reduce Cart Abandonment in WooCommerce Frequently Asked Questions About WooCommerce Cart Timers Additional Resources for WooCommerce Stores Why Use a Cart Reserved Timer in WooCommerce? I used to think that creating urgency was just a pushy marketing trick. However, when I started talking to people who sell on WooCommerce, I realized that it is actually a highly effective way to overcome shopper hesitation and stop losing sales to minor distractions. When a shopper sees a dedicated timer counting down, it creates a sense of urgency that encourages them to grab their credit card and complete the purchase right then and there. Adding a reservation timer helps in several ways: Reduces ‘Tab Parking’: This is a common habit where users treat your cart like a temporary bookmark while they compare prices on other sites. A timer encourages them to finish the transaction now instead of leaving that tab open indefinitely. Enforces True Scarcity: By automatically clearing the cart when the timer expires, you prove to your shoppers that the time limit is real. They must make a buying decision now rather than using the cart as a permanent bookmark. Builds Professional Trust: This mirrors the high-end checkout experience used by airlines and ticket agencies. Increases Conversions: The timer automatically handles the ‘nudging’ for you, which can lead to more sales even when you’re not actively working on your online store. Instead of manually chasing down lost sales, this small change automates your checkout process. Here’s how to set it up on your website. Step 1: Install and Activate the Merchant Plugin Before we begin, make sure you already have the WooCommerce plugin installed and active on your website, as Merchant relies on it for the cart timer to work. I specifically chose the Merchant toolkit because it’s an all-in-one WooCommerce growth tool. It offers dozens of modules to improve an online store’s functionality, which is much faster than installing several different plugins for each small feature. Because Merchant Pro acts as an advanced extension to the free core plugin, you actually need to install two plugins for this to work. Merchant Pro adds the extra Cart Reserved Timer feature you will need for this tutorial. First, you need to install and activate the free Merchant plugin directly from the WordPress plugin repository. Because ‘merchant’ is a common word, the easiest way to find the right one is to type ‘aThemes Merchant’ into the search bar. Next, you need to download the Merchant Pro plugin from your account area and install and activate it on your WordPress site. If you haven’t done this before, our guide on how to install a WordPress plugin shows you exactly how to search for free plugins and upload premium zip files. Upon activation, you will need to enter your license key to unlock the premium modules. Simply head over to Merchant » Settings in your WordPress dashboard and look for the ‘License’ field. You can find this key in your purchase welcome email. Alternatively, you can log in to your aThemes account, go to the licenses section, and click the key (🔑) icon to reveal and copy your unique number. Just paste that key into the settings field on your website and click the ‘Activate’ button, and you’ll be ready to start converting those hesitant customers. Step 2: Change to the Classic WooCommerce Cart If you recently installed WooCommerce, your store is likely using the new WooCommerce cart block by default. However, the Merchant timer requires the classic cart layout to display correctly. Before you enable the Cart Reserved Timer module, you need to quickly swap the block on your Cart page. Don’t worry, this only takes a few seconds. First, go to Pages » All Pages in your WordPress dashboard. From here, hover over your ‘Cart’ page and click the ‘Edit’ link. Once you are inside the WordPress content editor, you need to delete the default cart. Because the WooCommerce cart is made up of many locked inner blocks (like ‘Cart Line Items’), the easiest way to remove the whole thing is by using the List View. Simply click the Document Overview icon (it looks like three staggered lines) at the top left of the editor screen. This will open a list of all the blocks on your page. Find the main ‘Cart’ block in that list, click the three-dot menu next to it, and select ‘Delete’ to remove the entire block from your page. Don’t worry, this only removes the visual layout. It does not delete your WooCommerce products or store data. Next,

Stop Losing Sales: How to Add a WooCommerce Cart Reserved Timer Read More »

Uncategorized

WordPress.org blog: WordPress 7.0 Release Candidate 2

The second Release Candidate (“RC2”) for WordPress 7.0 is ready for download and testing! This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC2 on a test server and site. Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 7.0 is the best it can be. You can test WordPress 7.0 RC2 in four ways: Plugin Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edge” channel and “Beta/RC Only” stream.) Direct Download Download the RC2 version (zip) and install it on a WordPress website. Command Line Use this WP-CLI command: wp core update –version=7.0-rc2 WordPress Playground Use the WordPress Playground instance to test the software directly in your browser. No setup required – just click and go! The scheduled final release date for WordPress 7.0 is April 9, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who helps with testing! Please continue checking the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information. What’s in WordPress 7.0 RC2? What’s new in WordPress 7.0? Check out the Beta 1 announcement and 7.0 Developer Notes for details and highlights. For technical information related to issues addressed since RC1, you can browse the following links: GitHub commits since March 24, 2026 Closed Trac tickets since March 24, 2026 How you can contribute WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise. Get involved in testing Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. Your help testing the WordPress 7.0 RC1 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.0. For those new to testing, follow this general testing guide for more details on getting set up. What else to test: Real Time Collaboration Pattern Editing and content-only Interactivity If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs. Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack. Test on your hosting platforms Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue. Want to test WordPress on your hosting system? Get started with configuring distributed hosting tests here. Update your theme or plugin For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users. Thanks for continuing to test your themes and plugins with the WordPress 7.0 beta releases. If you haven’t yet, make sure to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 7.0. If you find compatibility issues, please post detailed information to the support forum. Help translate WordPress Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ? You can help translate WordPress into more than 100 languages. This release milestone (RC2) also marks the hard string freeze point of the 7.0 release cycle. An RC2 haiku Once just a dream, RC2 flows like a stream with seven-oh gleam. Props to @amykamala @annezazu for proofreading and review.

WordPress.org blog: WordPress 7.0 Release Candidate 2 Read More »

Uncategorized

Open Channels FM: How AI and Cloud Tools Are Transforming WooCommerce Development and Testing

In this episode, Derek talks with WooCommerce’s Brian Coords about how AI is reshaping e-commerce, from automating tasks to enhancing flexibility for developers and merchants. Brian shares insights on using AI for better workflows and community engagement.

Open Channels FM: How AI and Cloud Tools Are Transforming WooCommerce Development and Testing Read More »

Uncategorized

Gary: Embed All The Things!

Over 10 years ago, we introduced the oEmbed API to WordPress, expanding how WordPress handled embedding to cover all WordPress sites. It was an intentional decision to focus on oEmbed at the time: we wanted to focus on the embedding mechanism that would give site owners maximum control over what their embeds looked like. The code we wrote back then still runs on tens of millions of WordPress sites every day. There was something extra that continued to bug me, however. What about all the other sites? oEmbed provides rich embed experiences, but not every site needs that. Sometimes, you just need a card with an image and a description, which is where OpenGraph has similarly stood the test of time. It provides a straightforward method for both site owners to create simple, rich embeds, and for service providers like Slack, Discord, or even Apple Messages to safely create a rich card to place alongside links. WordPress has grown since then, too. The big change is Gutenberg, of course, which really brought forward the idea that the editor should be a rich content experience, that shouldn’t just be reserved for the front end. With that in mind, I build a plugin to handle embedding all the other sites. OpenGraph Fallback Embed This is a block plugin that tries to avoid you using the block it provides if at all possible! Instead, it hooks into the end of the Embed block rendering process – if the URL you pasted couldn’t be embedded all the normal ways, this plugin will try a few more fall back options: OpenGraph, Twitter Card tags, or even just a plain description in the meta tags. It’s the kind of plugin that you can install, and never have to think about again. One of the nicest things about WordPress is how pluggable it is. Even as a long time WordPress Core developer, I don’t think everything needs to land in Core, sometimes a feature can live as handy little plugin. If you like everything just magically embedding, give this plugin a try!

Gary: Embed All The Things! Read More »

Uncategorized

Matt: Ari & X

I’m in NYC for the Stephan Wolfram dev/ai/nyc conversation tomorrow at the Automattic Noho space. While walking back from the Apple Store in Soho where I had picked up a new Studio Display XDR to try out, ran into one of my favorite YouTube accounts to follow right now, Ari at Home! I ran into him around 32 minutes into this Twitch stream. Here’s how he set up his rig. Ran into @ARIatTWIT walking back from @Apple store with new Studio XDR. ? Offered to get him set up on @WordPress or @Tumblr. Carrying the display was my workout for the day. pic.twitter.com/q3vgAG7Hxm — Matt Mullenweg (@photomatt) March 25, 2026 A video I’ve shared with friends recently is when Harry Mack ran into Ari, which was fun for me because they’re two of my favorite accounts to follow. Sorry I didn’t freestyle! I had to get back to do some work, which is why I got the monitor. In other cool X/Twitter news, they launched an awesome feature today that lets you restrict replies not just to people you follow, but to people they follow as well. Nikita gave a hat tip to the conversation I had with Peter Levels / @levelsio. Credit to @rsrbk123 @striedinger @x_belous @singhai for their work on this. And thanks @photomatt for the suggestion https://t.co/Gr2iD1O73Y — Nikita Bier (@nikitabier) March 25, 2026

Matt: Ari & X Read More »

Uncategorized

WordPress.org blog: WP Packages is Working the Way Open Source Should

When WP Engine acquired WPackagist on March 12, the WordPress developer community faced a familiar question: what happens when critical open source infrastructure ends up under corporate control? The community already had an answer in progress. Four days later, WP Packages (formerly WP Composer) launched as a fully independent, community-funded alternative, with some neat additional features. Built by Ben Words from Roots, the team behind Bedrock, Sage, and Trellis, WP Packages is a new open source Composer repository for WordPress plugins and themes. Composer is PHP’s dependency manager, and it is how many professional WordPress developers install and update plugins and themes in their projects. Every free plugin and theme in the WordPress.org directory is available through WP Packages. Migrating from WPackagist can be done via a single script or a few terminal commands. What Happened and Why It Matters WPackagist was created in 2013 by Outlandish, a UK-based digital cooperative, and it served the WordPress Composer ecosystem for over a decade. In its later years the project suffered from deferred maintenance, slow update cycles, and little to no community input. When WP Engine announced the acquisition, developers raised immediate concerns about a private-equity-backed corporation controlling infrastructure this foundational to the WordPress developer workflow. WP Engine immediately updated the Composer info field to display a “WPackagist is now maintained by WP Engine” notice in every developer’s terminal. A small thing, but telling. That’s how corporate ownership changes the relationship between a tool and its users. And it only took less than 24h for this to pop up on every composer run:“Info from https://t.co/1EEb4PZ9N2: WPackagist is now maintained by WP Engine. Learn more at https://t.co/89b2hBWxd9“Which I’m sure is a permanent message that will just shift to marketing. Prove me wrong https://t.co/HdcuQPkUqV — Jonathan de Jong (@jonathan_dejong) March 13, 2026 Ben had already started building a WPackagist replacement last August, long before the acquisition made headlines. When WP Engine’s deal landed, he accelerated the launch, going live on March 16 with a fully open source repository on GitHub. Open source repo ≠ transparent system. WP Packages makes everything public, including infrastructure and build process. – Ben Word on X It’s also just a better tool. WP Packages supports Composer v2’s metadata-url protocol, which lets Composer fetch metadata only for the packages a project actually needs. WPackagist still relies on the older provider-includes approach, forcing Composer to download large index files before resolving dependencies. Cold dependency resolves on WP Packages are roughly 17x faster: 0.7 seconds for 10 plugins compared to 12.3 seconds on WPackagist. WP Packages also uses CDN caching with public cache headers and serves immutable, content-addressed per-package files. Package naming is cleaner (wp-plugin/ and wp-theme/ instead of wpackagist-plugin/ and wpackagist-theme/), metadata includes plugin and theme authors, descriptions, and homepage URLs that WPackagist has been missing for years, and updates sync every five minutes rather than WPackagist’s roughly 90-minute cycle. How to Switch Switching from WPackagist to WP Packages requires just a few terminal commands. Remove your existing WPackagist packages: composer remove wpackagist-theme/twentytwentyfive Remove the WPackagist repository and add WP Packages: composer config –unset repositories.wpackagist && composer config repositories.wp-composer composer https://repo.wp-packages.org Require packages with the new naming: composer require wp-theme/twentytwentyfive Alternatively, use the migration script to automatically update your composer.json: curl -sO https://raw.githubusercontent.com/roots/wp-packages/main/scripts/migrate-from-wpackagist.sh && bash migrate-from-wpackagist.sh Roots also provides a WP Packages Changelog Action for GitHub workflows that tracks dependency updates using the new naming format. Projects using Bedrock already ship with WP Packages configured out of the box. Open Source Wins The entire WP Packages project is public. The application code, documentation, and even the full Ansible deployment configuration are available on GitHub. Anyone can fork the repository and run their own WordPress Composer registry. Ben has also committed publicly that WP Packages will never use the Composer info field to push messages, ads, or upsells into developer terminals. That kind of restraint is easier to promise when a project answers to its community rather than to a corporate parent. WP Packages is funded through GitHub Sponsors. Current sponsors include Carrot, Kinsta, WordPress.com, and Itineris. The WordPress ecosystem has always been at its strongest when the community builds the tools it needs in the open. Ben saw a gap forming months before anyone else was paying attention, built something better than what existed, and released it for everyone. No acquisition required. No boardroom decisions about availability or pricing. Just developers solving a problem for other developers and sharing the result. Open source wins.

WordPress.org blog: WP Packages is Working the Way Open Source Should Read More »

Uncategorized
Exit mobile version
%%footer%%