WordPress made the decision to focus on what can be completed, the widgets screen. The widget area (also referred to as the sidebar area) is important so it makes sense to focus on finishing it, even at the expense of the Gutenberg Navigation Screen.
WordPress 5.6 due December 2020 was scaled back. An important Gutenberg feature was removed because development fell behind.
WordPress had intended to include the menu Navigation Screen in Gutenberg 9.1 and WordPress 5.6. Development fell behind and it was decided to remove the Gutenberg Navigation Screen as a goal for WordPress 5.6 and instead focus on the Gutenberg Widgets Screen functionality instead.
Both the Widgets and Navigation Screens are important.Yet without the Navigation Screen, an important functionality for WordPress sites, the Gutenberg interface may feel like a ghost of the modern interface it is intended to be.
An important feature of WordPress 5.6 was removed because it was nowhere near ready. Opens the door for progress on a bigger feature. The WordPress 5.6 Widgets Screen will be moved back to version 5.7, according to WordPress. This is because WordPress wanted to remove the navigation screen in order to concentrate on the widget screen.
Are you looking to upgrade to WordPress 5.6? This blog provides the latest features of the new version WordPress 5.6. Partner with a WordPres development company to leverage new features.
WordPress 5.6 is largely a success. There’s much that is so right with it. While it’s not a major advance it does have incremental improvements into site design functionality and improvements to functionality.
If you’re currently using the Enable jQuery Migrate Helper plugin and when logged into your admin panel you see error messages, then yes, you may experience unexpected website behavior when WordPress updates to version 5.6.
Bug warns publishers from leaving editing window in WordPress 5.6.1. WordPress 5.6.1, which many sites auto-updated to, has introduced a bug that makes it difficult to save a post. A temporary patch has been created to address the issue but it’s not an official update to solve the problem.