Admin Menu Editor plugin review and common issues

In Admin Menu Editor → All Menus, find the menu item and look for the hide/visibility option (typically a checkbox or eye icon). Ensure you save after making changes. Items hidden in Admin Menu Editor respect this setting for admin users but some items may override hiding based on user capabilities. Also: (1) the item may be a custom post type or taxonomy that uses a different hook registration than standard menus; (2) clear all admin caches; (3) check if another plugin is re-registering the menu item after Admin Menu Editor processes it.

Admin Menu Editor Pro’s access control may have restricted a menu item from a role that legitimately needs it. In Admin Menu Editor → [role-specific] menu, find the restricted item and modify the access setting. Role-based access in Admin Menu Editor works on top of WordPress capabilities — ensure the role still has the underlying WordPress capability for that admin page, and Admin Menu Editor is not additionally restricting it. Test by logging in as a user with the affected role.

Admin Menu Editor stores settings in WordPress options (wp_options table), which should persist through WordPress updates. If settings are being reset: (1) verify the plugin is not being deactivated and reactivated during updates (deactivation can trigger settings cleanup if the plugin is configured to delete settings on deactivation); (2) check if a WordPress reset or backup restore is responsible for the change; (3) use Admin Menu Editor’s export feature to back up the menu configuration regularly — this provides a restore point if settings are unexpectedly lost.

In Admin Menu Editor Pro, select “Role: Editor” from the role dropdown at the top of the editor. Configure the menu specifically for Editors: hide plugin management, theme customization, widget management, and other admin-level items. Keep Posts, Pages, Media, Comments, and any custom content type menus visible. Save. Then select “Role: Administrator” to configure the full admin menu. WordPress administrators see the full menu; Editors see only the content management items. This creates role-specific admin interfaces from a single WordPress installation.

In Admin Menu Editor, click “Add Menu Item” at the top level of the menu hierarchy. Select “Custom Link” or “Custom Page” as the type. Set: (1) the menu label (e.g., “Monthly Report”); (2) the URL (external reporting dashboard URL, Google Analytics link, etc.); (3) the icon (select from dashicons or enter a custom icon class); (4) drag the item to the desired position in the admin sidebar. Save. The custom link appears in the admin menu for all users (or specific roles in Pro) and opens the configured URL in the same or new tab.

Admin Menu Editor hides menu items visually but does not modify WordPress capabilities. A user with the “manage_options” capability can still access Settings → General directly by URL even if the Settings menu is hidden. Admin Menu Editor Pro’s access control can restrict access more strictly, but the underlying WordPress capability system is the ultimate access controller. For security-sensitive restrictions, use proper capability management (User Role Editor) in addition to Admin Menu Editor’s menu management.

Yes — Admin Menu Editor works with all admin menus registered through WordPress’s standard menu registration system (add_menu_page(), add_submenu_page()). Elementor, WooCommerce, Yoast SEO, and other plugins’ admin menu items appear in Admin Menu Editor and can be reordered, renamed, or hidden. Some plugins that register menus dynamically or outside standard WordPress functions may not appear — check the menu after plugin activation.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.