Version 2.11 – Role Editor, Admin CSS, and a Few Gutenberg Tweaks

This release includes a few frequently requested features and a number of bug fixes.

Role Editor

Admin Menu Editor Pro has always been limited by the fact that it could only change those role permissions that have a corresponding admin menu item. For example, you could use  it to hide the Appearance -> Themes menu from a role or user, but if you just wanted to prevent someone from installing new themes, you wouldn’t be able to do that because there is no “add new themes” menu item. Instead, you would have to install a separate role editing plugin and disable the install_themes capability.

Version 2.11 adds a built-in role editor to Admin Menu Editor Pro. You can find it in the new “Roles” tab on the Settings -> Menu Editor Pro page. You can use it to assign/deny capabilities to roles or users, create new roles, delete roles, and more.

Screenshot of the "Roles" tab

Keep in mind that this is a new and complex feature, so it may not be as stable as the rest of the plugin. If you notice any bugs or other issues, please report them.

Custom Admin CSS

This release also adds the ability to add your own CSS code to the WordPress admin back-end. You can add multiple CSS snippets and you can enable each snippet for all users or only for specific roles.

Screenshot of the "Admin CSS" section in the "Tweaks" tab

Gutenberg Tweaks

Finally, version 2.11 includes a few Gutenberg-related features:

  • You can hide individual Gutenberg blocks from roles or users. Go to the “Tweaks” tab to find these settings.
  • You can also hide the Gutenberg options menu.
  • Hiding the “Format” and “Publish” meta boxes now also hides the corresponding rows in Gutenberg’s “Status & Visibility” panel.

Screenshot of the "Hide Gutenberg Blocks" section in the "Tweaks" tab

See the full list of changes in the changelog.

Version 2.10 – Tweaks

This release adds a new tab called “Tweaks” to the plugin settings page.

Tweaks tab

This tab contains miscellaneous small modifications (“tweaks”) that you can enable for specific roles or users. These tweaks are available in version 2.10:

  • Hide “Screen Options” and “Help”.
  • Hide all admin notices. This includes even core notices like “settings saved”.
  • Hide specific user profile fields.
  • Hide sidebars and sidebar widgets. This applies to Appearance -> Widgets but not to the site front-end.
  • Hide TinyMCE buttons (TinyMCE is the classic post editor).

The plugin updates the list of available TinyMCE buttons when you open the post editor, so if you notice that the list is missing a button, try editing a post or page.

Why Add Tweaks?

Over the years, users have sent me many feature suggestions. Some of the suggestions are both valuable and relatively easy to implement, but they don’t quite fit anywhere. Adding more and more options to the menu editor wouldn’t work: every top level menu item already has 10+ settings and expanding that list without limit would make it difficult to find the settings that you actually need. Trying to sort the settings into separate tabs is also impractical because many of the feature suggestions have little in common. You would end up with a lot of new tabs that each contain just a handful of checkboxes. The plugin already has 8 tabs (more if you install the Branding add-on), so this approach also runs the risk of making the settings too cluttered.

The “Tweaks” tab is a compromise: one new tab for all the little customizations that don’t fit anywhere else, organized in sections. That’s still a lot of disparate settings in one place, but it’s somewhat orderly and you can collapse the sections that you’re not interested in. The plugin will remember which sections were open and which were closed.

If you don’t need any of the available tweaks, you can slightly improve plugin performance by turning off the “Tweaks” module in the “Settings” tab.

Other Changes

Version 2.10 also includes a few minor bug fixes related to meta boxes, plugin compatibility, and error handling.

Version 2.7 – Import and Export

The biggest change in this release is the improved import/export feature. Previously, you could only export some parts of the plugin configuration like the admin menu and dashboard widgets. You also had to go to each individual tab to export the settings in that tab.

This version adds a new “Export” tab – a central location for all your configuration export needs.

Export settings

You can also export much more of the configuration, including meta box settings, plugin visibility, Branding add-on settings (if you have that installed), submenu icon settings, UI color scheme settings, and more. There are still some things that cannot be exported, like some debugging settings. If you notice anything important missing, let me know.

Once you have an export file, you can import it through the “Import” tab.

Import settings - Step #1

You can choose which parts of the configuration to import:

Import settings - Step #2

You can also export plugin configuration using the command line (requires WP-CLI):

wp admin-menu-editor export filename.json --all

Import it like this:

wp admin-menu-editor import filename.json

The old import/export features like the “Export” button in the menu editor are still in place and still work like they did before, at least for now. They will be removed in a future release because having multiple “Export” buttons that all do different things would probably be confusing.