WordPress 6.8.2 RC1 Released: Updates, Testing Methods and Official Release Date

WordPress officially released on the night of July 8th the First Release Candidate for WordPress 6.8.2 (RC1). Although this version is close to its final form, it is still in the development stage and is not suitable for use in production environments or mission-critical sites. Developers and users are invited to experience RC1 in a test environment and submit feedback to help the team improve the stability and performance of the release.

Image[1]- WordPress 6.8.2 RC1 Released: Updates, Test Methods & Official Release Date

Testing WordPress 6.8.2 RC1

Users and developers can test the RC1 version using the following methods.

Using plug-ins

Installation and activation WordPress Beta Tester Plug-ins.
Select the Point Release channel and Nightlies stream.

Direct Download

Download the RC1 version of the zip package from the official WordPress site and install it manually on the test site.

Using WP-CLI

utilization WP-CLI Execute the following command to update to the RC1 version:

wp core update https://wordpress.org/wordpress-6.8.2-RC1.zip

WordPress 6.8.2 Official Release Plan

WordPress 6.8.2 is expected to be released on Tuesday, July 15, 2025. The release date may be adjusted if issues are discovered during the RC1 testing phase.

WordPress 6.8.2 RC1 update highlights

Core Updates (fixes 20 issues)

This update fixes the following issues:

  • Twenty Twenty-Five Theme editor style not loaded.
  • Add height and width attributes to the wp_get_attachment_image_attributes filter.
  • rpc.pingomatic.com upgraded to HTTPS.
  • Reevaluate the HTML5 novalidate attribute for comment forms.
  • Remove app.screencast.com oEmbed provider.
  • Uploading a Mac screenshot with a question mark in the file name causes the image to become corrupted.
  • Mobile restores revision button alignment.
  • The Twenty Twelve theme figcaption style is not applied in the editor.
  • pull intoBlock EditorStyle Development Mode.
  • Update tinymce cache keys.
  • Updated Twemoji to v16.0.1.
  • Fixed version of the Gutenberg plugin for 6.6 branching E2E tests.
  • Add version number testing to package-lock and composer files.
  • Twenty Sixteen Themes Quote Block Plain styles show borders in the editor.
  • Twenty Fourteen Themes Latest Comments Block link color error.
  • wordpress-develop environment setting WP_CONFIG_PATH environment variable.
  • Development environment integration with wp-env improves speed.
  • The do_blocks function releases transient memory leaks.
  • Discontinued support for WordPress 4.1 - 4.6.
  • Twenty Twenty-One theme menu toggle buttons are unresponsive before loading.

Block editor update (fixes 15 issues)

Block editor updates include:

  • The Navigation Link block does not check for validity when editing is disabled.
  • Optimize Navigation Link block getBlockParentsByBlockName selector call.
  • The Navigation Link block requests entities only when selected.
  • The Query Loop block does not override the value of the query.inherit property.
  • Remove the truncation in the Media Label Preview tooltip.
  • Avoid using old URLs when re-selecting the same image.
  • Post Template blocks do not depend on ignore_sticky. REST API Default Value.
  • Fix MediaPlaceholder media URL input type issue.
  • DOM adds summary elements to focusable elements.
  • Button blocks limit the range of link width styles.
  • The Details block enables all non-interactive formats.
  • Fix a keyboard accessibility issue with Details blocks, where the list view is selected to show sub-blocks.
  • URL slug Handling on cleanup HTML entity with the & symbol.
  • Remove screencast.com embed block variant.
  • Fix Floating UI packages dependency issue.

Community engagement contributions

WordPress, as an open source project, relies on the active participation of the global community. Users and developers can participate in the following ways.

Submission of problem reports

If you encounter problems while testing RC1, you can submit a detailed report in the WordPress support forums or on Trac.

vulnerability testing

Until WordPress 6.8.2 is officially released, any newly discovered security vulnerabilities will be doubly rewarded. Vulnerability reports can be submitted through HackerOne and follow the Security Disclosure Policy.

Update Plugins & Themes

Plug-ins andthematicDevelopers should test the product for compatibility with WordPress 6.8.2 RC1 and update Tested up to version 6.8.2 in the readme file.If compatibility issues are found, feedback can be posted on the official Support WordPress forum.

summarize

WordPress 6.8.2 RC1 is released, marking the final testing phase of the maintenance update. Developer and user participation will help identify issues in time and drive the WordPress ecosystem to be more stable and efficient. Interested users can go to the WordPress website to download and start testing.


Contact Us
Can't read the tutorial? Contact us for a free answer! Free help for personal, small business sites!
Customer Service
Customer Service
Tel: 020-2206-9892
QQ咨询:1025174874
(iii) E-mail: info@361sale.com
Working hours: Monday to Friday, 9:30-18:30, holidays off
© Reprint statement
This article was written by lmx
THE END
If you like it, support it.
kudos722 share (joys, benefits, privileges etc) with others
commentaries sofa-buying

Please log in to post a comment

    No comments