Comprehensive Guide to Upgrading to WordPress 6.9: New Features and Best Practices

WordPress 6.9 introduces several focused improvements designed to enhance collaboration, streamline the Site Editor experience, and provide developers with more robust APIs. This guide covers the most important new features, best practices for upgrading, things to watch out for, and a step-by-step plan to upgrade your site safely.

Key Features in WordPress 6.9:

1. Block-level Collaboration with Notes:
   WordPress 6.9 adds block-level Notes that let editors leave comments directly on individual blocks. Notes include simple threading (reply, resolve) and a Notes sidebar for managing feedback, which improves editorial workflows and reduces the need for external review tools.
   
   

   Feature: Block-level NotesBenefit: In-editor collaboration and faster review cycles    

   
   

2. Refined Site Editor and Template Management:
   Template navigation and organization are improved, with clearer grouping of templates and faster template switching. Color-coded block outlines and a refined layout inspector make visual debugging and global style adjustments more straightforward for designers and content teams.
   
   

3. Query Loop & Dynamic Content Enhancements:
   The Query Loop block gains more filtering and pagination controls, allowing finer control over dynamic lists (e.g., custom post types, taxonomies). This reduces reliance on custom templates and gives editors more power to build dynamic pages without developer intervention.
   
   

   Feature: Query Loop filters & paginationUse-case: Building dynamic archive and listing pages without custom PHP templates    

   
   

4. Performance and Image Delivery Improvements:
   6.9 includes optimisations in asset loading and improved defaults for responsive image handling. These changes aim to reduce Largest Contentful Paint (LCP) and improve perceived performance out of the box, especially on image-heavy sites.
   
   

5. Developer APIs and Extensibility:
   New and improved REST endpoints and JavaScript hooks make it easier to extend the editor and integrate headless workflows. Developers can build richer editor plugins and tailor collaboration experiences using well-defined extension points.
   
   

   API: Extended REST endpoints & editor hooksAction: Use to build custom integrations and collaborative tooling    

   
   

Steps to Safely Upgrade to WordPress 6.9

1. Full Backup (Files + Database):
   Before upgrading, create a complete backup of your site including the database, uploads, themes, and plugins. Use trusted tools like UpdraftPlus or All-in-One WP Migration, and store backups offsite (cloud storage or external drive) to avoid single-point failures.
   
   

   Plugin: UpdraftPlusAction: Manual or scheduled backup of DB + wp-content + wp-config.php    

   
   

2. Test in a Staging Environment:

   • Create a staging site using your host tools or plugins like WP Staging.
   • Apply WordPress 6.9 on staging first and test all critical flows (checkout, forms, login, custom post types).

   Testing in staging prevents breaking your live site and helps identify incompatibilities early.
   
   

3. Update Plugins & Themes First:

   Make sure all plugins and themes are updated to their latest versions before upgrading core. Pay attention to plugins that modify the editor, caching, or authentication, as they are more likely to require updates.
   
   

   Dashboard: Plugins > Update AllThemes: Appearance > Themes > Update Theme    

   *Tip: Check plugin changelogs for explicit 6.9 compatibility notes.*
   
   

4. Review Custom Code & Child Themes:

   Audit any custom functions, theme templates, or editor-modifying JavaScript for compatibility with new editor hooks and Query Loop changes. If you rely on custom password or authentication behavior, review related code paths for potential impacts.
   
   

   Action: Search custom code for editor hooks, query modifications, and password handling    

   
   

5. Upgrade WordPress Core:

   From the Dashboard, navigate to Updates and click "Update Now." Monitor the update process and check for warnings. If your host provides automatic updates, you may choose to update via the host panel instead.
   
   

6. Run Post-Upgrade Tests:
   After upgrading, perform a full QA pass: test critical pages, forms, login, search, custom post types, and page templates. Verify the editor experience (Notes, Query Loop settings) and check the site on multiple devices and browsers.
   
   

   Tests: Checkout flow, contact forms, login, editor Notes & Query Loop rendering    

   
   

Things to Take Care Of / Known Considerations

• Ensure your PHP version meets recommended minimums (PHP 8.0+ recommended) to benefit from performance and security improvements.
• Editor plugins that modify block behavior (page builders, block libraries) may require updates—test these thoroughly in staging.
• If you use custom caching layers, clear caches after upgrade and validate asset loading to avoid stale JS/CSS issues.
• Review any custom REST API consumers (mobile apps, headless frontends) for changes to endpoints or payload structure.
• Backwards-incompatible customizations to templates or hooks are rare but possible—keep a changelog of custom code for quick rollback.

Requirement: PHP 8.0 or higherAction: Review custom code, update extensions, and test in staging

FAQs

1. What are Notes, and how do they affect my workflow?

Notes are block-level comments inside the editor that let teams leave feedback on specific blocks. They simplify collaborative editing by keeping comments contextual and trackable. They do not alter published content until edits are saved and published by an editor.

2. Will Query Loop changes break my custom templates?

Query Loop enhancements aim to provide more control in-editor, which should reduce the need for custom templates. However, if you have custom PHP templates that rely on specific query parameters or custom loop logic, test them in staging to ensure compatibility.

3. Do I need to change my hosting because of 6.9?

Not necessarily. However, upgrading PHP to a modern supported version (PHP 8.0 or higher) is recommended to get the best performance and security. Check with your host if you're on older PHP versions or managed hosting with specific constraints.

4. Are there security implications with the new collaboration features?

Collaboration features like Notes are designed with permissions in mind—only users with editor access can add or resolve notes on content. Still, review user roles and capabilities to ensure your workflow aligns with your security posture.

5. What if a plugin breaks after the upgrade?

If a plugin breaks, revert to your backup or use your host's staging/restore features. Identify the incompatible plugin, check for updates from the plugin author, and consider reaching out to plugin support. In some cases, temporary deactivation or replacing the plugin with an alternative is necessary.

Need Assistance with the Upgrade?

If you need help upgrading to WordPress 6.9, or want a staged rollout and QA run, email us at [email protected] or schedule a consultation through our website. We provide upgrade audits, staging setups, and post-upgrade QA to ensure a smooth transition.