Janis Elsts

Admin Menu Editor lets you manually edit the Dashboard menu. You can reorder the menus, show/hide specific items, change permissions, and more.
Features
<ul>
<li>Change menu titles, URLs, icons, CSS classes and so on.</li>
<li>Organize menu items via drag & drop.</li>
<li>Change menu permissions by setting the required capability or role.</li>
<li>Move a menu item to a different submenu. </li>
<li>Create custom menus that point to any part of the Dashboard or an external URL.</li>
<li>Hide/show any menu or menu item. A hidden menu is invisible to all users, including administrators.</li>
</ul>
The <a href="http://w-shadow.com/AdminMenuEditor/" rel="nofollow ugc">Pro version</a> lets you set per-role menu permissions, hide a menu from everyone except a specific user, export your admin menu, drag items between menu levels, make menus open in a new window and more. <a href="http://amedemo.com/wpdemo/demo.php" rel="nofollow ugc">Try online demo</a>.
Additional Features
Despite the name, this plugin is not limited to just editing the admin menu. You can also:
<ul>
<li>Create login redirects and logout redirects.</li>
<li>Allow/deny access to specific posts based on user roles.</li>
<li>Hide plugins on the Plugins -> Installed Plugins page from other users.</li>
<li>Edit the display name, description, and other plugin details shown on the Plugins -> Installed Plugins page (e.g. for white-labelling).</li>
</ul>
Shortcodes
The plugin provides a few utility shortcodes. These are mainly intended to help with creating login/logout redirects, but you can also use them in posts and pages.
<ul>
<li><code>[ame-wp-admin]</code> – URL of the WordPress dashboard (with a trailing slash).</li>
<li><code>[ame-home-url]</code> – Site URL. Usually, this is the same as the URL in the “Site Address” field in Settings -> General.</li>
<li><code>[ame-user-info field="..."]</code> – Information about the logged-in user. Parameters:
<ul>
<li><code>field</code> – The part of user profile to display. Supported fields include: <code>ID</code>, <code>user_login</code>, <code>display_name</code>, <code>locale</code>, <code>user_nicename</code>, <code>user_url</code>, and so on.</li>
<li><code>placeholder</code> – Optional. Text that will be shown if the visitor is not logged in.</li>
<li><code>encoding</code> – Optional. How to encode or escape the output. This is useful if you want to use the shortcode in your own HTML or JS code. Supported values: <code>auto</code> (default), <code>html</code>, <code>attr</code>, <code>js</code>, <code>none</code>.</li>
</ul>
</li>
</ul>
Notes
<ul>
<li>If you delete any of the default menus they will reappear after saving. This is by design. To get rid of a menu for good, either hide it or change it’s access permissions.</li>
<li>In the free version, it’s not possible to give a role access to a menu item that it couldn’t see before. You can only restrict menu access further.</li>
<li>In case of emergency, you can reset the menu configuration back to the default by going to http://example.com/wp-admin/?reset_admin_menu=1 (replace example.com with your site URL). You must be logged in as an Administrator to do this.</li>
</ul>

Admin Menu Editor

Does just what it says it does. Instantly.

Perfect

I've been a user of Admin Menu Editor and the Pro version for a while now. WordPress backend can get a little messy very easily, so this plugin comes to the rescue, and it does it well.

I wish all the features were free, but the devs need to pay the bills as well :-)

Best option


It allows you to move existing items on the left side menu around and change their icons.


Not Bad, simple to use


Essential for taming the admin menu, due to all the stupid ideas other developers have for their menus!


Essential

Lets you edit the WordPress admin menu. You can re-order, hide or rename menus, add custom menus and more.

Ipstenu (Mika Epstein)

We’ve all had this problem: a group of spammers from <code>mail.ru</code> are registering to your blog, but you want to keep registration open. How do you kill the spammers without bothering your clientele? While you could edit your theme’s <code>functions.php</code> and block the domain, once you get past a few bad eggs, you have to escalate.
Ban Hammer helps you do that by preventing unwanted users from registering.
On a single install of WordPress, instead of using its own database table, Ban Hammer pulls from your list of prohibited emails from the Disallowed Comment Keys feature, native to WordPress. Since emails never equal IP addresses, it simply skips over and ignores them.
On a network instance, there’s a network wide setting for banned emails and domains. This means you only have one place to update and maintain your blocked list. When a listed user attempts to register, they get a customizable message that they cannot register.
For advanced documentation, including how to use on WooCommerce, please visit <a href="https://github.com/Ipstenu/ban-hammer/wiki" rel="nofollow ugc">the Ban Hammer Wiki</a>.
<ul>
<li><a href="https://github.com/Ipstenu/ban-hammer/" rel="nofollow ugc">Development</a></li>
<li><a href="https://github.com/Ipstenu/ban-hammer/wiki" rel="nofollow ugc">Wiki</a></li>
<li><a href="https://ko-fi.com/A236CEN/" rel="nofollow ugc">Donate</a></li>
</ul>
<h4>Privacy Policy</h4>
This plugin does not track data outside of what WordPress already collects. It utilizes the submitted email address to validate the domain and compares it to the list of prohibited domains and emails. No additional data is processed.
<h4>Credits</h4>
Ban Hammer is a very weird fork of <a href="http://www.joeswebtools.com/wordpress-plugins/no-disposable-email/" rel="nofollow ugc">Philippe Paquet’s No Disposable Email plugin</a>. The original plugin was a straight forward .dat file that listed all the bad emails (generally ones like mailinator that are disposable) and while Ban Hammer doesn’t do that, this would not have been possible without that which was done before.
Many thanks are due to WP-Deadbolt, for making me think about SQL and TTC for StopForumSpam integration. MASSIVE credit to Travis Hamera for the StopForumSpam/cURL fix! And then props to Helen Hou-Sandí for not using curl at all. Protip? Use <a href="http://planetozh.com/blog/2009/08/how-to-make-http-requests-with-wordpress/" rel="nofollow ugc">WP_http</a> instead!

Ban Hammer

Prevent people from registering via your disallowed comment keys.

Admin Menu Editor vs Ban Hammer