WordPress 5.5. now parsed
WordPress 5.5, “Ekstine”, was released on 11th August 2020.
It has now been reparsed on core.wp-a2z.org.
Additionally, the following have been updated and reparsed in their appropriate sub-domains.
| Component | Previous version | Current version |
|---|---|---|
| WordPress core | 5.4.2 | 5.5 |
| Akismet | 4.1.4 | 4.1.6 |
| Hello Dolly | 1.7.2 | 1.7.2 |
| WordPress SEO | 14.3 | 14.7 |
| Genesis | 3.3.1 | 3.3.3 |
| Jetpack | 8.6.1 | 8.8 |
| WooCommerce | 4.2 | 4.4.1 |
| Twenty Fourteen | 2.8 | 2.9 |
| Twenty Fifteen | 2.6 | 2.7 |
| Twenty Sixteen | 2.1 | 2.2 |
| Twenty Seventeen | 2.3 | 2.4 |
| Twenty Nineteen | 1.6 | 1.7 |
| Twenty Twenty | 1.4 | 1.5 |
Block updates – to be done
I haven’t yet had a look at any block changes in the newer versions of WordPress core, WooCommerce or Jetpack.
Problems experienced with the 5.5 udpate
Having upgraded WordPress to version 5.5 before any plugins or themes I encountered a couple of problems in the form of unwanted messages. I haven’t yet experienced a problem requiring the Enable jQuery Migrate Helper plugin.
Unwanted messages
Deprecated: wp_make_content_images_responsive is deprecated since version 5.5.0!
Use wp_filter_content_tags() instead.
in /home/customer/www/bobbingwide.org.uk/public_html/wp-includes/functions.php on line 4773Notice: register_rest_route was called incorrectly.
The REST API route definition for yoast/v1/get_head
is missing the required permission_callback argument.
For REST API routes that are intended to be public,
use __return_true as the permission callback. And four messages from Genesis. e.g.
Notice: register_rest_route was called incorrectly.
The REST API route definition for genesis/v1/layouts/(?P<type>[a-z0-9,_-]+)
is missing the required permission_callback argument.
For REST API routes that are intended to be public,
use __return_true as the permission callback. For the register_rest_route messages we were also told to that the message was added in version 5.5. and to see Debugging in WordPress for more information.
It looked like I had to update WordPress SEO (was at 14.3) and the Genesis Theme Framework (at 3.3.2 ) to stop getting these Deprecated messages.
