on May 7 , WordPress 5.2 “Jaco” was released, and brought some useful site management tools, such as the Site Health Check and PHP Error Protection, as well as a number of accessibility, privacy, and developer updates.
PHP Error Protection features better handling of the “white screen of death.”. An administrator focused update that lets you safely fix or manage fatal errors, It also offers a way to enter recovery mode, which pauses error-causing plugins or themes, while SIte Health Check, a suite of features focused on security and speed, which adds two new pages to help debug common configuration issues.
WordPress 5.2, developed by 327 volunteer contributors, can help you identify and fix configuration issues and fatal errors, whether you are building a site for personal use or managing multiple sites for clients.
The new WordPress 5.2 updates improve contextual awareness and keyboard navigation flow for those using screen readers and other assistive technologies! Adding also extra block editor improvements, new dashicons and emojis.
WordPress now helping to educate users and give developers the essential information they need.
On Ticket #47046 you can find an interesting discussion whether or not a grading system should exist.
- PHP Version Bump: The minimum supported PHP version is now 5.6.20. As of WordPress 5.2, themes and plugins can safely take advantage of namespaces, anonymous functions, and more.
- New Body Hook: 5.2 introduces a wp_body_open hook, which lets themes support injecting code right at the beginning of the element.
Updated Plugin Guidelines Proposal
The Plugins team has proposed some updates to the guidelines for developers on the Plugin Directory. This proposal will remain open until after WordCamp EU 2019, at which point it will be closed and either re-proposed if there are significant changes, implemented, or scrapped. Following more interesting details:
- Admin messages and advertisements must be limited to one per common page.
- Messages must only be shown to people who can action on them. For example, don’t show ‘install X!’ to a user who can’t install anything.
- All messages must be permanently dismissible by an action on a page (such as clicking a dismiss button or an X to close). Filters are insufficient, as not all users are capable of implementing them.
- No repeatable messages. If a user has been asked to “Try this add-on!” and said no, their choice must be respected. (nb. exceptions will be granted for reminders to complete setup, or if they action in a way that would require that add-on.)
- All ‘advertisement’ type messages have to directly relate to the developer or the plugin. Ads for other things a developer happens to like aren’t permitted.
The changes can be seen here: https://github.com/WordPress/wporg-plugin-guidelines/pull/66/files
Everyone is welcome and encouraged to comment on this proposal. You can reply on the Github Pull Request, or create a new issue.
Now we can’t wait to see what is coming on WordPress 5.3! Our team closely monitoring WordPress Core upgrades and discussion, and we actively participate in the Core Progress, WordPress updates on our platform and for our clients are very important, and is one of our main goals! We will keep you posted!