Giorgos Sarigiannidis

Slash Admin gathers some common functions that you probably need in most of your websites. The plugin lets you change various different options in a WordPress website, keeps them active even if you switch your theme and helps you create a friendlier Admin Panel for you and your editors.
If you are lost with the many options, here’s a presentation of the plugin’s <a href="https://www.gsarigiannidis.gr/slash-admin-best-features/" rel="nofollow ugc">best features</a>.
<h4>Features</h4>
Frontend
<ul>
<li>Option to point to a static splash page.</li>
<li>Option to convert email addresses characters to HTML entities to block spam bots.</li>
<li>Show EU Cookie Law consent message (check screenshots about available options). Since v.3.0 it also supports WPML for different message per language.</li>
<li>Add a “Loading” animation which hides itself when the page is fully loaded</li>
<li>Enqueue your own Google Web Fonts, with option to load it locally for better performance and privacy</li>
<li>Get rid of the word “Category:” in front of the Archive title (usually needed if your theme uses the_archive_title()).</li>
<li>Add excerpt support to pages.</li>
<li>Enable the use of shortcodes in widgets.</li>
<li>Display a warning for users of old versions of Internet Explorer (IE8 or older). Yes, sadly there are still people who use Internet Explorer 8…</li>
</ul>
Administration
<ul>
<li>Insert Google Analytics tracking code (so as you don’t have to remember re-entering it in case you switch themes in the future)</li>
<li>Hide Site Health from everyone except from a selected Admin (<a href="https://www.gsarigiannidis.gr/how-to-hide-wordpress-site-health-from-everyone-but-you/" rel="nofollow ugc">read more</a>)</li>
<li>Hide ACF options from everyone except from the selected Admin</li>
<li>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). <a href="https://www.gsarigiannidis.gr/how-to-hide-wordpress-site-health-from-everyone-but-you/" rel="nofollow ugc">Read more</a></li>
<li>Change the address that receives the Plugin and Theme auto-update email notifications</li>
<li>Make WordPress respect the order of the tags you insert in a post (<a href="https://www.gsarigiannidis.gr/wordpress-post-tags-order" rel="nofollow ugc">read more</a>)</li>
<li>Limit the number of revisions that WordPress keeps for each post (keeps the database cleaner)</li>
<li>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)</li>
<li>Enable Jetpack development mode</li>
<li>Move Jetpack share and like buttons</li>
<li>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.</li>
</ul>
Login screen
<ul>
<li>Add your custom logo at the WordPress log-in screen</li>
<li>Make the login screen logo (custom or default) linking to your website’s homepage instead of wordpress.org</li>
<li>After login, redirect users at the homepage instead of their profile page</li>
<li>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</li>
<li>Add your custom CSS to the login screen to completely change its appearance</li>
</ul>
Non-admins
<ul>
<li>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).</li>
<li>Disable tags and categories</li>
<li>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.</li>
<li>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).</li>
<li>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).</li>
</ul>
White label backend
<ul>
<li>Change the “Howdy” message at the top right corner of the admin (both backend and logged-in frontend)</li>
<li>Change the default footer text at the admin</li>
<li>Replace the WordPress logo at the top left corner of the admin bar with your own (both backend and logged-in frontend)</li>
<li>Replace the default Welcome message at the Dashboard with your own</li>
<li>Add a Dashboard Widget to provide general or commercial information to your clients (for example: your contact info or links to support documentation)</li>
<li>Add your own custom CSS for the Admin area</li>
</ul>
Performance
<ul>
<li>Disable Emojis</li>
<li>Disable wp-embed script from the frontend or load it conditionally</li>
<li>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.</li>
<li>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.</li>
</ul>
Shortcodes
<ul>
<li>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).</li>
<li>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).</li>
<li>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). </li>
</ul>
Development functions
<ul>
<li>Using <code>slash_dump()</code> instead of <code>var_dump()</code> will wrap the output in <code><pre></pre></code> tags, for better readability. <code>slash_admin_dump()</code> 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).</li>
<li>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.</li>
</ul>
Notifications
Slash Admin displays the following notifications:
<ul>
<li>A list with the users who logged in during the past 15 minutes (except from you, obviously)</li>
<li>A warning when debug mode is enabled (you should enable it when developing, but disable it when the site goes live)</li>
<li>A warning when your site is hidden from search engines</li>
</ul>

Slash Admin

Great set of features! Using it on Multisite activated on each domain, and each has its own settings.
Tip for those hard to remove elements:
Find its CSS selector - in browser right-click on it, select Inspect
When you have it, go to Slash Admin "White Label" tab.
Enter the CSS in the "Custom CSS" box, Save.
eg: I want to get rid of wordpress icons in Admin bar menus
div.blavatar { display: none; }
Nice.
Thankyou Giorgo :)



Great set of features!

This is a neat plugin. I wish there was a way to further fine-tune some options but for what it does it does it very well. Easy to use and well thought out!



Dig it!

Dozens of settings aiming at creating a friendlier administration environment for both Administrators and Editors.

Jeremy Felt

Custom Posts Per Page allows you to specify how many posts are displayed per page depending on your current view. Once settings are changed, the Blog pages show at most setting in the Reading menu will be ignored.
Settings are available for:
<ul>
<li>Home (Index) Page
<ul>
<li>As long as view is set to blog posts, not static page.</li>
</ul>
</li>
<li>Category Pages</li>
<li>Tag Pages</li>
<li>Author Pages</li>
<li>Archive Pages</li>
<li>Search Pages</li>
<li>Default Page (Any page not covered above.)</li>
<li>Custom Post Type archive pages
<ul>
<li>All Custom Post Types are detected automatically.</li>
</ul>
</li>
</ul>
Each of the above settings can have a different value for the first page displayed and subsequent paged views.
Custom Posts Per Page makes it easy to manage exactly how your content is displayed to your readers, especially when different views have different layouts, rather than relying on the single setting in the Reading menu or having to hard code options in your custom theme.

Custom Posts Per Page

Thank you so much for making this plugin!



Saved a lot of time and is a great addition

Custom Posts Per Page provides a settings page in your WordPress admin that allows you to specify how many posts are displayed for different views.

Slash Admin vs Custom Posts Per Page