WordPress Release: 6.5.3

Tag Name: 6.5.3

Release Date: 5/7/2024

WordPress LogoWordPress

World's most popular open-source content management system powering over 40% of all websites. Offers extensive plugin ecosystem, themes, and robust community support for blogs, e-commerce, and corporate websites. Highly customizable and scalable platform suitable for beginners and advanced developers.

TL;DR

WordPress 6.5.3 is a maintenance release that addresses several bugs and improves compatibility across browsers. Key updates include fixes to the Block Hooks API, layout rendering for themes without theme.json, media handling improvements, and better plugin activation feedback. This release enhances stability for both classic themes and block themes while improving accessibility and internationalization support.

Highlight of the Release

    • Fixed Block Hooks API to correctly pass context to filters
    • Improved layout rendering for themes without theme.json
    • Added admin notice for successful plugin activation
    • Fixed wp_localize_script() functionality when called early
    • Improved browser compatibility for media handling
    • Enhanced internationalization with better text domain handling

Migration Guide

No significant migration steps are required for this maintenance release. After updating to WordPress 6.5.3, it's recommended to:

  1. Test your site's functionality, especially if you're using custom themes without theme.json
  2. Check any custom plugins that might be affected by the fixes to wp_localize_script() or text domain handling
  3. If you're a developer working with Block Hooks API, review your implementation to ensure compatibility with the updated context handling

Upgrade Recommendations

This is a maintenance release that addresses several bugs and improves compatibility. It's recommended for all WordPress 6.5.x users to upgrade to version 6.5.3 to benefit from these fixes and improvements.

The update process should be straightforward and can be performed through the WordPress dashboard or via manual update. As with any update, it's always a good practice to back up your site before proceeding.

Bug Fixes

Block Editor Fixes

  • Block Hooks API: Fixed issues with passing the correct context to filters like hooked_block_types, hooked_block, and hooked_block_{$hooked_block_type}. This ensures proper conditional insertion of hooked blocks when an anchor block is contained in a template or template part.

  • Layout Rendering: Fixed issues with layout rules that reference content and wide sizes CSS variables when no layout sizes exist in the current theme.json. The system now skips outputting these rules when appropriate.

  • Template Handling: Fixed the REST API endpoint for template lookup to return an empty object when no fallback templates are found, preventing PHP notices.

  • Editor UI: Fixed several UI issues including pattern pagination focus loss, Font Library modal scrollbar problems, and List View stuck dragging mode in Firefox.

Script Loading and Internationalization

  • wp_localize_script(): Fixed functionality when called early in the load process, ensuring it works properly in contexts like login_enqueue_scripts.

  • Text Domain Handling: Added early bailout when invalid text domains are passed to load_textdomain() and related functions, preventing warnings or fatal errors.

Media Handling

  • AVIF Support: Fixed a potential fatal error in the AVIF image information handling by importing an upstream fix from libavifinfo.

CSS and Layout

  • Layout Rules: Removed output of base rules for flow and constrained layout types on themes without theme.json, preventing potential styling issues.

  • Media CSS: Updated CSS to use flex-start instead of start for better browser compatibility, particularly for Opera Mini which has 1.01% usage.

New Features

New Admin Notice for Plugin Activation

A new admin notice has been added when activating plugins from the Plugins > Add New screen. Since plugin activation on this screen is performed using AJAX without page redirects, users may not see newly activated plugin's menu items or UI elements until refreshing the page. The new notice informs users that the plugin was successfully activated and that some changes may not appear until the page is refreshed.

Security Updates

No specific security fixes were included in this release.

Performance Improvements

Layout Rendering Optimization

The release includes optimizations for layout rendering by:

  1. Skipping the output of unnecessary layout rules when content and wide size values don't exist in the current theme configuration
  2. Limiting layout rules on themes without theme.json
  3. Improving the handling of base layout rules

These changes help reduce CSS bloat and improve rendering performance, particularly for classic themes and themes without theme.json configuration.

Impact Summary

WordPress 6.5.3 is primarily a bug fix and compatibility release that addresses several issues reported since the 6.5 release. The changes focus on improving the stability and reliability of the WordPress core, particularly around the Block Editor, layout rendering, and internationalization.

Key improvements include better handling of layout styles for themes without theme.json, fixes to the Block Hooks API, enhanced plugin activation feedback, and improved browser compatibility. These changes collectively provide a more stable and consistent experience for both users and developers.

The release doesn't introduce any breaking changes and should be a smooth upgrade for sites running WordPress 6.5.x. The fixes to wp_localize_script() functionality and text domain handling are particularly important for plugin developers, while the improvements to layout rendering will benefit theme developers working with both classic and block themes.

Statistics:

File Changed26
Line Additions1,240
Line Deletions461
Line Changes1,701
Total Commits21

User Affected:

  • Improved plugin activation experience with new admin notice after successful activation
  • Fixed issues with Block Hooks API for template management
  • Better handling of templates lookup in the REST API

Contributors:

johnbillionjoedolsonaudrasjbockhamadamsilversteintellthemachinesswissspidyaaronjorbin