{"id":3480,"date":"2022-07-20T11:22:10","date_gmt":"2022-07-20T11:22:10","guid":{"rendered":"https:\/\/www.hostinger.com\/blog\/?p=3480"},"modified":"2022-07-30T08:14:08","modified_gmt":"2022-07-30T08:14:08","slug":"wordpress-6-0-1","status":"publish","type":"post","link":"https:\/\/www.hostinger.com\/blog\/wordpress-6-0-1","title":{"rendered":"WordPress 6.0.1 Maintenance Update"},"content":{"rendered":"<p>WordPress 6.0 was released recently on May 24, 2022. The developers have since brought out <a href=\"https:\/\/wordpress.org\/news\/2022\/07\/wordpress-6-0-1-maintenance-release\/\" target=\"_blank\" rel=\"noopener\">WordPress 6.0.1<\/a> to fix bugs.<\/p><p>It introduces 13 core and 18 block editor bug fixes. In this post, we will discuss the fixes that we&rsquo;ve found the most interesting!<\/p><h2 class=\"wp-block-heading\" id=\"h-wordpress-6-0-1-bug-fixes\">WordPress 6.0.1 Bug Fixes<\/h2><p>You can review all the fixes in more detail on the <a href=\"https:\/\/core.trac.wordpress.org\/query?milestone=6.0.1\" target=\"_blank\" rel=\"noopener\">WordPress Trac<\/a> or the <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/commits\/wp\/6.0\" target=\"_blank\" rel=\"noopener\">GitHub repository<\/a>. Some improvements may not be related to user experience, such as the <strong>About<\/strong> page video thumbnail update or the reversion of the Twenty Ten theme.&nbsp;<\/p><p>That said, we&rsquo;ve tested WordPress 6.0.1 and identified the fixes that significantly improve the block editor.<\/p><h3 class=\"wp-block-heading\" id=\"h-default-template-for-new-post\">Default Template for New Post<\/h3><p>We&rsquo;ve found the <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/56163\" target=\"_blank\" rel=\"noopener\">default template bug fix<\/a> to be the most significant of all 6.0.1 improvements.&nbsp;<\/p><p>When adding a new post, the default template selected by the editor used to be the <strong>404 <\/strong>error page. This wasn&rsquo;t logical or convenient &ndash; you had to change the template settings whenever you would add a new post.<\/p><figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"915\" height=\"281\" src=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/post-default-template.png\/public\" alt=\"WordPress post editor, showing the template settings and the default 404 template.\" class=\"wp-image-3481\" srcset=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/post-default-template.png\/w=915,fit=scale-down 915w, https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/post-default-template.png\/w=300,fit=scale-down 300w, https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/post-default-template.png\/w=768,fit=scale-down 768w\" sizes=\"(max-width: 915px) 100vw, 915px\" \/><\/figure><p>WordPress 6.0.1 has fixed this issue. The default template is now the <strong>Single<\/strong> post template. You won&rsquo;t have to change the template settings unless you wish to use another post template.<\/p><h3 class=\"wp-block-heading\" id=\"h-pattern-keywords\">Pattern Keywords<\/h3><p>The ability to <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/38323\" target=\"_blank\" rel=\"noopener\">register block patterns<\/a> from the WordPress pattern directory in the <strong>theme.json <\/strong>file was a highly anticipated feature of the WordPress 6.0 major release.&nbsp;<\/p><p>The process was meant to be quite simple &ndash; you&rsquo;d only need to add pattern slugs to the <strong>theme.json <\/strong>file, and you&rsquo;d be able to insert the added theme via the pattern inserter of the block editor.<\/p><p>However, keywords are now stored based on their meta value instead of the taxonomy in the pattern directory. This made it impossible to find a registered pattern in the editor.<\/p><p>WordPress 6.0.1 now <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/56126\" target=\"_blank\" rel=\"noopener\">implements the same values<\/a> for keywords, and you can register patterns in the <strong>theme.json <\/strong>file and use them via the theme editor.<\/p><figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"681\" height=\"584\" src=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/pattern-browser.png\/public\" alt=\"WordPress pattern inserter, showing a registered custom pattern.\" class=\"wp-image-3482\" srcset=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/pattern-browser.png\/w=681,fit=scale-down 681w, https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/pattern-browser.png\/w=300,fit=scale-down 300w\" sizes=\"(max-width: 681px) 100vw, 681px\" \/><\/figure><h3 class=\"wp-block-heading\" id=\"h-prevent-opening-links-in-the-latest-posts-block\">Prevent Opening Links in the Latest Posts Block<\/h3><p>The <strong>latest posts<\/strong> block has a default behavior that allows users to click links in the theme editor. However, accidentally clicking the link would&rsquo;ve taken you away from the content you were editing.<\/p><p>The developers have decided to implement <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/40593#issuecomment-1111295332\" target=\"_blank\" rel=\"noopener\">a pop-up alert<\/a> to inform users that the link is disabled. This way, links are still recognized and communicated as such, but clicking them won&rsquo;t interfere with whatever you&rsquo;re doing.&nbsp;<\/p><figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"587\" height=\"292\" src=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/link-disable-popup.png\/public\" alt=\"WordPress latest posts block, highlighting the pop-up that appears when users click on the link.\" class=\"wp-image-3483\" srcset=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/link-disable-popup.png\/w=587,fit=scale-down 587w, https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/link-disable-popup.png\/w=300,fit=scale-down 300w\" sizes=\"(max-width: 587px) 100vw, 587px\" \/><\/figure><h3 class=\"wp-block-heading\" id=\"h-navigation-block-submenu-style\">Navigation Block Submenu Style<\/h3><p>The navigation block allows you to be creative with your website menu. Unfortunately, a bug has been discovered &ndash; issues could arise when creating a submenu with the <strong>open on click <\/strong>option enabled.<\/p><p>The bug resulted in the submenus not retaining the same style as the parent menus, requiring you to customize the style to make them uniform. This was especially inconvenient when working with parent menus with custom typography and colors.<\/p><p>WordPress 6.0.1 has solved this issue &ndash; now, you can add submenus with <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/40671\" target=\"_blank\" rel=\"noopener\">styles inherited from their parent menus<\/a>.<\/p><figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"839\" height=\"331\" src=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/submenu-style.png\/public\" alt=\"WordPress navigation block with a submenu, showing the inherited style.\" class=\"wp-image-3484\" srcset=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/submenu-style.png\/w=839,fit=scale-down 839w, https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/submenu-style.png\/w=300,fit=scale-down 300w, https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/submenu-style.png\/w=768,fit=scale-down 768w\" sizes=\"(max-width: 839px) 100vw, 839px\" \/><\/figure><h2 class=\"wp-block-heading\" id=\"h-how-to-update-your-wordpress-version\">How to Update Your WordPress Version<\/h2><p>There are two easy ways to update WordPress:<\/p><ul class=\"wp-block-list\"><li><strong>Via the WordPress dashboard<\/strong>. Whenever an update is available, this banner sits at the top of your admin panel. Click on the link &ndash; it will take you to the WordPress update page.<\/li><\/ul><figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"675\" height=\"98\" src=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/wordpress-update-banner.png\/public\" alt=\"WordPress update banner that appears on the admin panel.\" class=\"wp-image-3485\" srcset=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/wordpress-update-banner.png\/w=675,fit=scale-down 675w, https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/wordpress-update-banner.png\/w=300,fit=scale-down 300w\" sizes=\"(max-width: 675px) 100vw, 675px\" \/><\/figure><ul class=\"wp-block-list\"><li><strong>Via hPanel<\/strong>. Open the WordPress dashboard on hPanel and check the WordPress version in the bottom-right section. You should see a button to update WordPress.<\/li><\/ul><figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"445\" height=\"300\" src=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/hpanel-wordpress-update.png\/public\" alt=\"WordPress version section on hPanel that contains the Update to 6.0.1 button.\" class=\"wp-image-3486\" srcset=\"https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/hpanel-wordpress-update.png\/w=445,fit=scale-down 445w, https:\/\/imagedelivery.net\/LqiWLm-3MGbYHtFuUbcBtA\/wp-content\/uploads\/sites\/4\/2022\/07\/hpanel-wordpress-update.png\/w=300,fit=scale-down 300w\" sizes=\"(max-width: 445px) 100vw, 445px\" \/><\/figure><p>If you need more information, read our tutorial on <a href=\"https:\/\/www.hostinger.com\/tutorials\/how-to-update-wordpress\">updating a WordPress site<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>WordPress 6.0 was released recently on May 24, 2022. The developers have since brought out WordPress 6.0.1 to fix bugs.<\/p>\n<p>It introduces 13 core and 18 block editor bug fixes. In \u2026<\/p>\n","protected":false},"author":172,"featured_media":3568,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2365],"tags":[],"hashtags":[],"class_list":["post-3480","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress"],"hreflangs":[],"_links":{"self":[{"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/posts\/3480","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/users\/172"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/comments?post=3480"}],"version-history":[{"count":3,"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/posts\/3480\/revisions"}],"predecessor-version":[{"id":3575,"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/posts\/3480\/revisions\/3575"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/media\/3568"}],"wp:attachment":[{"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/media?parent=3480"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/categories?post=3480"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/tags?post=3480"},{"taxonomy":"hashtags","embeddable":true,"href":"https:\/\/www.hostinger.com\/blog\/wp-json\/wp\/v2\/hashtags?post=3480"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}