=v2.11 (updated 2020-02-22)=
\n##### Add to
\nAdded character editor. You can assign\/delete role functions, create custom roles, delete roles and more. This is a new complication. If you find any bugs or other issues, please report them.
\nAdded ability to add custom CSS to WordPress admin. To enter the CSS code, go to the "Adjustments" tab and find the new "Admin CSS" section. You can add multiple CSS snippets and enable\/disable each snippet for a specific role or user.
\nAdded "Reset Permissions" toolbar button. It resets all menu permissions and visibility settings for the selected role or user to default values. This does not affect custom permissions applied by other plugins. To reveal the new button, click the "V" button on the right side of the toolbar.
\nAdded Title and Content Editor options to the Meta Box tab. They allow you to hide the post title field and the main post editor respectively.
\nAdded ability to hide specific Gutenberg blocks from roles or users. This feature is in the Adjustments tab.
\nAdded an option to hide the Gutenberg options menu. This is the "More Tools and Options" menu, which you can open by clicking the three vertical dots in the upper right corner of the editor.
\nHiding the Format and Publish meta boxes now also hides the corresponding lines in Gutenberg's Status and Visibility panel: Publish Format and Publish.<\/p>\n
#####fixed
\nFixed admin notifications showing briefly even when the "Hide all admin notifications" option was enabled.
\nAdded compatibility workaround for MailPoet 3. Custom menu colors and FontAwesome icons will now display correctly on MailPoet's admin page.
\nWhen you activate the Admin Menu Editor, the hidden "Getting Started" menu item created by the plugin extension widget option will no longer be visible.
\nSlightly reduced chance of encountering race conditions when saving metabox settings.<\/p>\n
corrected
\nReduced the amount of space used by plugin visibility settings. This change will take effect the next time these settings are saved.
\nExpanded the "Compress Menu Configuration Data" feature to use ZLIB compression in addition to menu data reorganization. This greatly reduces the amount of data stored in the database, but increases decompression overhead. Configuration compression is disabled by default. You can enable it in the Settings tab.<\/p>\n
<\/p>\n