Admin Menu Editor For WordPress
Admin Menu Editor is a WordPress plugin that will let you manually edit the Dashboard menu. You can reorder the menus, show/hide specific items, change access rights, and more.
Features
- Sort menu items any way you want by simple drag & drop.
- Move a menu item to a different submenu via cut & paste.
- Edit any existing menu – change the title, access rights, menu icon and so on. Note that in the free version you can’t relax menu permissions – i.e. give access rights to a role that originally didn’t have them – but you can change them to be more restrictive.
- Hide/show any menu or menu item. A hidden menu is invisible to all users, including administrators.
- Create custom menus that point to any part of the Dashboard. For example, you could create a new menu leading directly to the “Pending comments” page.
Here’s a screenshot :
This plugin also has a Pro version that offers a bunch of extra features.
Download
The latest version of the plugin is always available on WordPress.org.
Requirements :
- WordPress 4.1 or later
- PHP 5.2 or later
Known Issues
The basic idea for the plugin was suggested by several commenters way back in October. However, the internal menu system that WordPress uses is obscure and unsuitable for direct manipulation, so I spent quite a while inventing workarounds. And even after a few weeks of pondering, there are some things I haven’t quite fixed.
- If you delete any of the default menus they will reappear after saving. This is not a bug, it’s a feature 😉
- As I mentioned before, the access rights required for using a particular menu item can’t be lowered, but can be made more strict. This has been fixed in the Pro version.
- Plugin menus that are moved to a different submenu will not work unless you put the full page URL in the “URL” field. This is because WP “ties” the menu item to it’s parent menu and won’t recognize it in a different submenu.
Subscribe via RSS
Get Updates by Email
[…] Admin Menu Editor – Lets you directly edit the WordPress admin menu. You can re-order, hide or rename existing menus, add custom menus and more. Beta. By Janis Elsts. […]
[…] رابط صفحة الإضافة الرسمية من المبرمج […]
This plugin is great! This is exactly what I’ve been looking for!
Thank you so much ^^
I have had some problems with the Roles feature. I have attempted to make certain menus available to only the administrator, others available to the Author etc. After many attempts, I have found that this doesn’t do anything at all.
Any help would be appreciated! Thank you!!!!
Strange, it’s always worked fine here. Could you give me a specific example of what you did and the expected vs. actual result?
Firstly, thank you for such a wonderful plugin.
I haven’t explored it in great detail, but I found something that I didn’t quite understand:
I am not much of a coding guy, so I choose to use the user-categories (administrator,editor, contributor, author, subscriber) instead of permissions. If I restrict a panel by user-category, it appears to users of that category ONLY! So if I restrict a panel to editor, even the administrator CANNOT see it!
Has that been done on purpose? Is there any way I can restrict panesl to “{user_category} & above” instead of the current {user_category} only?
Any help would be much appreciated. 🙂
PS: I think comment #284 (Kate) may be having the same problem…
Short answer: You can accomplish this by using capabilities instead of user roles.
Long answer: Somewhat counter-intuitively, user roles like Administrator, Editor, Author and so on are not inherently “above” or “below” one another. In other words, the hierarchy is completely “flat”. What sets them apart is what “capabilities” they have.
Capabilities are things like being able to edit blog settings, publish or edit posts and so on. In theory, you could give all the capabilities that an Administrator has to the Subscriber role, making it every bit as powerful as Administrator – all without actually switching each subscriber to the “Administrator” category.
All of the above is part of WordPress core. The Admin Menu Editor just gives you the ability to manipulate some of this stuff.
So the answer to your question is to set the menu’s “Rrequired capability” that all the roles you want to access it have in common. You can find a list (and explanation) of most built-in capabilities here.
So the answer to your question is that you need
[…] By Janis Elsts | Visit plugin site […]
Hello there, hello Janis,
First of all thank you very much for this awesome plugin, it’s dead simple yet very powerful.
Though I’d like to point out that I got the same need as Dan : hiding the menu editor menu. I got it to work commenting the lines you mentioned above but I think It could be handled another way.
Your plugin is great to make wordpress look like a CMS. We often use roles to allow clients / users to work with it, but they don’t often have the administrator rights.
I then think that it could be clever to add a condition which verifies that a user with administrator level cannot hide the menu editor, and by the way allow to hide this menu to every other users, from editors to suscribers …
What do you think ?
Regards,
Max
Hmm. Perhaps something like this version, then? Install it and set the “Required capability” for Menu Editor to “administrator”.
How great, it’s perfect now. Thank you !
rats its stuffed up my admin menu on the member blogs.
Im running WPMU3.1 and BP latest ver.
First I found it would not obey the role limitations no matter how they were set.
It would only hide the menu if I hid it from everyone including super admin.
Then I tried hiding the sub menus and it seemed to work.
But then suddenly a member blog had more menus visible than it did to start off with!
And now a member with no blog is seeing only the Dashboard/MySites/CreateNewSite and the Profile menu – no Post, Media, Comments, or Tools, like before istalling the plugin.
So I tried the load default menu option and it did not fix it.
So I tried uninstalling the plugin and that did not fix it.
Guess I have to install a recent database backup 🙁
Any other suggestions before I do that?
Thanks – Dan V
I am a bit puzzled why in the comments above people say it is easy to understand and use.
I have tried dozens of plugins, and I am quite puzzled by how this one is supposed to work.
Aside from the fact that like someone else above it took me a while to find the hide button… and perhaps the setting of user levels would be straightforward if it worked for me…
but Im still trying to figure out what you mean by ‘For example, you could create a new menu’ – I think you mean ‘menu item’ as I see no way to save and them implement a new menu.
Am I missing something?
What I would like to do is simply remove many items from a members admin menu when they dont have a blog, and remove other items when they do have a blog, and not remove anything from Superadmins menu. I guess if the user role levels worked it would be fairly easy to do. Again … am I missing anything?
Thanks
Dan V
If uninstalling the plugin didn’t fix the menu you likely have other problems. Any changes the plugin can make are applied only when it’s active; it doesn’t make any permanent modifications to your menu, user accounts or roles. Whatever issues remain after uninstalling it are likely caused by one of your other plugins.
As for hiding certain menus from members that don’t have a blog, perhaps you could give them a custom role that doesn’t have any of the capabilities associated with those menu items?
@whiteshadow
is this plugin multisite capable? (ie. can you set network permissions)
More or less. If you install it in mu-plugins or activate it network-wide (see readme.txt for instructions), any menu modifications you make as the super admin will affect the entire network. Fine-grained permission tweaking can be tricky, though.
thx for the response shadow
so just to clarify if i do simple things like arrange the sidebar in different order it will propagate throughout the network?
Yes, that should work.
downloaded and its working so far just as advertised thank you
you may want to update the mu install to state to move the menu_editor_mu.php to the mu directory right now doesnt have the mu at the end 🙂
thank you
The instructions are correct; what you should’ve moved is the “admin-menu-editor-mu.php” file from the “includes” directory.
Still, who cares as long as it works 😉