A marketing team could not find a campaign page in Appearance > Menus. WordPress 6.9 narrowed the menu search to post titles, and one filter on wp_ajax_menu_quick_search_args brings the old behavior back.
A pre-release WordPress install killed a client’s publish button. The cause was a core bug in hidden async-upload fields, one of several things the 6.9 release candidates cleaned up alongside alternate cron and REST API errors.
A client’s booking plugin started throwing fatal errors after a theme update, because both files defined get_data(). Prefixing the function bought five minutes. Here is what proper PHP namespacing does instead.
A client’s whole API auth was a hardcoded key checked against a query parameter. Here is how I rebuild API key authentication in WordPress as a real security layer, using the REST authentication filter.
A vague “Bug fixes” changelog leaves your team guessing after an update. Clear changelogs with dated, categorized entries cut support headaches and protect your reputation.
A real case from a client site: how the WordPress 6.9 heading block CSS specificity fix changed padding on custom feature boxes, and why a proper fix beats a quick override.
A client’s membership site was buried under millions of postmeta rows from a badge plugin. Moving that data to a custom table fixed the slowdown, and here’s when it’s worth doing.
An agency told a client WordPress couldn’t handle their e-commerce project. Most WordPress myths about security, speed, and scale come down to bad implementation, not the platform itself.
A WooCommerce migration left European customers’ accented characters showing as garbled symbols. WordPress 6.9 replaces the old guesswork functions with validation, and here’s how to use them.
A client’s save button kept spinning with no error at all. The cause was a WP_Error object a plugin ignored, and this is how WordPress fails silently and how to get those errors into your logs.