Slash Admin for WordPress

Hide Site Health from everyone except from a selected Admin (read more)

Hide ACF options from everyone except from the selected Admin

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email. By default, it will be sent to the admin email. Slash Admin allows you to override it (you can also add multiple recipients if you like). Read more

Change the address that receives the Plugin and Theme auto-update email notifications

Make WordPress respect the order of the tags you insert in a post (read more)

Limit the number of revisions that WordPress keeps for each post (keeps the database cleaner)

Prevent Post Updates and Deletion After a Set Period. Useful if you have many editors or in cases where an editor’s account is compromised, adding spam code to the posts (by disallowing editing of older posts you limit the damage)

Enable Jetpack development mode

Move Jetpack share and like buttons

Maintenance mode. If checked, non-Admins will not be able to acess the WordPress backend and they will see a customizable message instead. Useful if you want to perform some maintenance work to your website and you don’t want your Editors to add or modify the content before you finish. Admins are not affected and they can always login as usual.

Login screen

Add your custom logo at the WordPress log-in screen

Make the login screen logo (custom or default) linking to your website’s homepage instead of wordpress.org

After login, redirect users at the homepage instead of their profile page

Disable the Admin Bar for all users except Administrators. Applies only to the front-end. It’s useful if you want your site to be visible only to logged-in users (e.g. during developement phase), but you don’t want them to access the dashboard or get confused with the admin bar

Add your custom CSS to the login screen to completely change its appearance

Non-admins

Hide unnecessary options from the Admin menu for non admins (so editors won’t get overwhelmed with options that have no meaning for the current website).

Disable tags and categories

Hide specific pages from non admins. For example, you might not want your editors to have access to the static frontpage, the blog page or pages that you use as page templates.

Allow editors to manage Menus and Widgets and access some other appearance settings previously acessible only to admins (for example, you might want to give your client the option to modify the website’s menu, but you would rather avoid making him/her an administrator).

Hide notices about updating WordPress and other plugins for all users except from Admins (sometimes clients get confused with those notices and think that there is something wrong with the website).

White label backend

Change the “Howdy” message at the top right corner of the admin (both backend and logged-in frontend)

Change the default footer text at the admin

Replace the WordPress logo at the top left corner of the admin bar with your own (both backend and logged-in frontend)

Replace the default Welcome message at the Dashboard with your own

Add a Dashboard Widget to provide general or commercial information to your clients (for example: your contact info or links to support documentation)

Add your own custom CSS for the Admin area

Performance

Disable Emojis

Disable wp-embed script from the frontend or load it conditionally

DNS prefetching notifies the client that there are assets we’ll need later from a specific URL (outside our website’s domain) so the browser can resolve the DNS as quickly as possible.

Link prefetching and prerendering. Link prefetching is a browser mechanism, which utilizes browser idle time to download or prefetch documents that the user might visit in the near future. A web page provides a set of prefetching hints to the browser, and after the browser is finished loading the page, it begins silently prefetching specified documents and stores them in its cache. When the user visits one of the prefetched documents, it can be served up quickly out of the browser’s cache. Prerendering downloads and renders the entire page and hides it from the user until it is requested, therefore, it should be used with caution.

Shortcodes

If you manually include email addresses in your posts, you should consider disguising them in order to “fool” e-mail harvesters (check FAQ for details).

Show a telephone number in a way that it is clickable. When clicked, if you are on a mobile device it opens the phone’s dialer and if you are on a desktop computer it prompts to make a call via a related program (e.g. Skype).

If you develop your site on localhost or on a temporary URL, you might want to avoid absolute URLs inside posts and pages. That way you don’t need to update your links after migrating to your actual domain (check FAQ for details).

Development functions

Using slash_dump() instead of var_dump() will wrap the output in <pre></pre> tags, for better readability. slash_admin_dump() does the same thing, only this time the output is only visible to admins (can be handy if you want to debug a live site).

Show warnings if the site is on air and debug mode is still on and if the site is on localhost and debug mode is off. Also, show warning if the website is on air and you have chosen to hide it from Search Engines.

Notifications

Slash Admin displays the following notifications:

A list with the users who logged in during the past 15 minutes (except from you, obviously)

A warning when debug mode is enabled (you should enable it when developing, but disable it when the site goes live)

A warning when your site is hidden from search engines