Skip to content
This repository has been archived by the owner on Jan 17, 2025. It is now read-only.

Prep for WordPress 5.5 #125

Closed
TimidRobot opened this issue Aug 3, 2020 · 1 comment
Closed

Prep for WordPress 5.5 #125

TimidRobot opened this issue Aug 3, 2020 · 1 comment
Assignees
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed ⛔️ status: discarded Will not be worked on
Milestone

Comments

@TimidRobot
Copy link
Contributor

Description

WordPress 5.5 is scheduled to be released on August 11th. Are your plugins ready?

After testing your plugins and ensuring compatibility, it only takes a few moments to change the readme "Tested up to:" value to 5.5. This information provides peace of mind to users and encourages them to update to the latest version.

Here are the current "Tested up to:" values for each of your plugins:

For each plugin that is compatible, you don't need to release a new version — just change the stable version's readme value.

Looking to get more familiar with 5.5? Read this roundup post on the core development blog to learn more about the varous changes coming to core with this major release:

https://make.wordpress.org/core/2020/07/30/wordpress-5-5-field-guide/

There are six areas that specific focus should be given as plugin-related changes coming in 5.5:

1.) Note the version of jQuery shipped in core will be updated in 5.6 and as a first step jquery-migrate is no longer enqueued by default in 5.5. Updates to your code are required if you rely on jquery-migrate or .live() to function properly as they are being removed. You can verify this by checking your code with WP_DEBUG enabled to make sure you are not using deprecated code. Please do this to avoid unnecessary support requests and negative reviews for your plugin:
https://make.wordpress.org/core/2020/06/29/updating-jquery-version-shipped-with-wordpress/

2.) Note the new plugin auto-update UI and how to ensure your plugin is ready for the new auto-updates system:
https://make.wordpress.org/core/2020/07/15/controlling-plugin-and-theme-auto-updates-ui-in-wordpress-5-5/

3.) Note the Block Directory guidelines (https://make.wordpress.org/plugins/2020/07/22/proposed-block-directory-guidelines/) and how to get your block plugin added to the Block Directory:
https://make.wordpress.org/plugins/2020/07/11/you-can-now-add-your-own-plugins-to-the-block-directory/

4.) Note the new XML sitemap feature and how it can be integrated with your plugin:
https://make.wordpress.org/core/2020/07/22/new-xml-sitemaps-functionality-in-wordpress-5-5/

5.) Note the deprecated $HTTP_RAW_POST_DATA global variable in the PHP related improvements & changes devnote:
https://make.wordpress.org/core/2020/07/14/php-related-improvements-changes-wordpress-5-5-edition/

6.) Note the various plugin recommendations in the miscellaneous changes devnote:
https://make.wordpress.org/core/2020/07/29/miscellaneous-developer-focused-changes-in-wordpress-5-5/

In order to ensure compatibility, you can download and beta test your plugin with the latest WordPress version here: https://make.wordpress.org/core/handbook/testing/beta-testing/

Thank you for all you do for the WordPress community, and we hope you enjoy 5.5 as much as we do.

@TimidRobot TimidRobot added the help wanted Open to participation from the community label Aug 3, 2020
@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Dec 2, 2020
@TimidRobot TimidRobot added this to the v2021.05.1 milestone Apr 29, 2021
@TimidRobot TimidRobot added ✨ goal: improvement Improvement to an existing feature 🏁 status: ready for work Ready for work 💻 aspect: code Concerns the software code in the repository and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Apr 29, 2021
@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Apr 30, 2021
@TimidRobot TimidRobot self-assigned this May 11, 2022
@TimidRobot TimidRobot added 🟩 priority: low Low priority and doesn't need to be rushed ⛔️ status: discarded Will not be worked on and removed help wanted Open to participation from the community 🏁 status: ready for work Ready for work Hacktoberfest 🏷 status: label work required Needs proper labelling before it can be worked on hacktoberfest-accepted labels May 11, 2022
@TimidRobot
Copy link
Contributor Author

status: discarded: superseded by #158

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed ⛔️ status: discarded Will not be worked on
Development

No branches or pull requests

4 participants