First update of WordPress 6 released
As expected, the first update of WordPress has been released. After a full version update, it is always a question of when the first subsequent update will be released. WordPress 6.0.1 brings with it many fixes, however no groundbreaking improvements. Since this update focuses on ensuring the stability and security of WordPress. Let's cover these in more detail in this article as to what was released in this update.
The following issues have been fixed to the Core of WordPress:
- Build/Test Tools: Pass GitHub Actions environment variables to the Docker container.
- Fix block-templates theme support not present in /themes REST API endpoint.
- About page: Replace video thumbnail image.
- Resolve WP_Term_Query cache problem.
- Fix caching issues in WP_Term_Query class.
- Remove meetup from oembed allow list.
- Register Comments Query Loop from metadata to enable title and description translation...
- Themes: Revert the change of theme preview width on Add Themes screen...
- Block Patterns: Update the value used for keywords...
- Bundled Themes: Revert the Twenty Ten theme version to 3.6...
And the following issues have been fixed for the Block editor of WordPress:
- Lower the priority of the gallery gap css so it loads after the block layout css
- Add utility classnames back to blocks that have layout attributes specified
- Block Library: Fix JS Error in Avatar Block
- Media & Text: Remove font size declaration from template
- Comment Author and Date blocks: aligned editor markup with the frontend
- Handle no variation case in the block transform menu
- Fix/block meta icon prop errors
- Prevent opening the links in editor for Latest Posts
- Navigation block "Open on click": Inherit font style and font weight
- Comments Block: fixed issue with custom font sizes and links color
- Reuse code of the editor placeholder across Post Comments and Post Comments Form
- Improve the logic for warnings for Post Comments Form placeholder
- Post Comments Form: Add button that enables commenting to warning
- Ensure only the main query is modified when resolving template for new posts
- Strip whitespaces in render_block_core_cover before injecting the featured image.
- Post Template: Ensure layout classnames are not attached to inner li elements
- Pasting: Fix performance regression due to removeWindowsFragments
- Post Comments Form: Fix warning i18n
If you want to read the WordPress post about this you can do so at the following link:
https://wordpress.org/news/2022/07/wordpress-6-0-1-maintenance-release/
The GitHub links are also included and can give you more information if needed.
Update is automatically installed
Like all Core updates to WordPress itself, this is automatically installed by default. Yesterday you will already have received an email if you have configured your SMTP correctly. With the automatic mail of this. So it is important that you take a look at the website hosting and check if everything is still functional on your website. However, this will be the case.
With such updates that focus on security and bug fixes, there is less chance of something essential to your website breaking down. But of course, there is always a chance that just one of your plugins will suffer from this. So always check manually after each update if your website is still fully functional and does not show any error messages. Both visible and invisible.
The WordPress Core is automatically set to update is the default setting since a number of versions. In this way WordPress tries to ensure that no websites remain stuck in previous versions. And become at risk over time because of this. The number one reason WordPress websites get hacked and lost is because of an outdated plug-in, theme or core version on the one hand. Where a security update is not installed. This is asking for trouble. Therefore WordPress has ensured that at least the Core version updates are now applied automatically. This can save a lot of trouble.
Automatic updates for plugins and themes are also possible to set, but we generally recommend that you check this manually once a week and update where necessary. Many webmasters will be working on their website on a daily basis, if you do not have daily contact with your website, then set reminder mails for this. Or add this to your monthly calendar to manually run through all.
Experience shows that automatic updates of plugins can be problematic if not controlled. We also recommend you to keep your plugin list as small as possible, as it can cause more problems than just incidents with automatic updates. Like slowing down the website itself.
Don't want to worry about automatic updates on your WordPress website anymore? Then take a look at our Managed WordPress hosting packages. We will take care of the updates for you!
