Admin Menu Editor
Admin Menu Editor lets you manually edit the Dashboard menu. You can reorder the menus, show/hide specific items, change permissions, and more. Features Change menu titles, URLs, icons, CSS classes and so on. Organize menu items via drag & drop. Change menu permissions by setting the required capability or role. Move a menu item to a different submenu. Create custom menus that point to any part of the Dashboard or an external URL. Hide/show any menu or menu item. A hidden menu is invisible to all users, including administrators. The Pro version 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. Try online demo. Additional Features Despite the name, this plugin is not limited to just editing the admin menu. You can also: Create login redirects and logout redirects. Allow/deny access to specific posts based on user roles. Hide plugins on the Plugins -> Installed Plugins page from other users. Edit the display name, description, and other plugin details shown on the Plugins -> Installed Plugins page (e.g. for white-labelling). 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. [ame-wp-admin] – URL of the WordPress dashboard (with a trailing slash). [ame-home-url] – Site URL. Usually, this is the same as the URL in the “Site Address” field in Settings -> General. [ame-user-info field="..."] – Information about the logged-in user. Parameters: field – The part of user profile to display. Supported fields include: ID, user_login, display_name, locale, user_nicename, user_url, and so on. placeholder – Optional. Text that will be shown if the visitor is not logged in. encoding – 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: auto (default), html, attr, js, none. Notes 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. 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. 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.
AJAX Thumbnail Rebuild
AJAX Thumbnail Rebuild recreates the resized copies WordPress makes of every image in your media library. It does them one image at a time, so a library of any size gets through without running into the script timeout that stops the plugins which rebuild everything in a single request. You need this whenever the sizes change: a new theme with different dimensions, a plugin that registers a size of its own, or a size you have edited yourself. WordPress applies those to images uploaded afterwards and leaves everything already in the library at its old dimensions. Rebuilding fills the gap. On its screen under Tools you can: Pick which of the registered sizes to rebuild, so a single changed size does not mean redoing all of them. Rebuild only the images used as a featured image – which covers WooCommerce product images and product galleries – or only the file names matching a pattern, e.g. banner-*.jpg. Watch it run: a progress bar, the image being worked on, a Stop button, and a list of anything it had to skip. See every image size registered on the site with its dimensions and crop setting. Clean up the resized files left behind by sizes that no longer exist. You can also work on one image at a time without leaving the media library: a row action rebuilds or optimises a single image, a bulk action hands a selection to the plugin’s screen, and the attachment details panel – wherever it opens – rebuilds, optimises, or replaces the file. A replaced image keeps its id, title and address, so every post and product already pointing at it shows the new picture. Beyond rebuilding, each of these is off until you turn it on: Uploads. How hard WordPress compresses the copies it writes, and how large an image may stay before it is scaled down. Optimising. Makes files smaller without resizing them, using the optimisers installed on the server – jpegoptim, optipng, gifsicle, and pngquant where lossy PNG is allowed. Where a host has none, TinyPNG or ShortPixel can do the same job over their API. A file is replaced only when the new one is genuinely smaller. AVIF and WebP copies. Written next to every image WordPress generates and served through a picture element, AVIF first, WebP after it, the original as the fallback – which works behind a page cache. Background processing. Optimising and the copies are the slow half of an upload. Queue them instead, and the upload finishes as soon as the sizes are written – on Action Scheduler where the site has it, on WP-Cron where it does not. Image proxy. Front end image URLs can be served through wsrv.nl, which resizes and re-encodes on the fly and serves the result from a CDN. Your own files are never touched. Sizes on demand. An upload keeps only its own file, and each size is cut the first time something asks for it. This plugin requires JavaScript to be enabled. Contributions are welcome at Github
