by
Giorgos Sarigiannidis
5 (9 reviews)
Slash Admin
Dozens of settings aiming at creating a friendlier administration environment for both Administrators and Editors.
Slash Admin ranks #8,920 among WordPress.org plugins with 500+ active installations, is #242 of 1,807 in the Analytics category, a 5/5 rating from 9 reviews, and was last updated Mar 1, 2024. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 6.4 (Current: 7.0.2)
v3.8.3
Current Version v3.8.3
Updated 2 years ago
Last Update on 01 Mar, 2024
Refreshed 10 hours ago
Last Refreshed on
#242 of 1,807 in Analytics
Top 25% by installs
No update in over a year
Rank
#8,920
+3 this week
Active Installs
500+
—
No change
KW Avg Position
191
—
No change
Downloads
27.7K
+1 today
Support Resolved
0%
—
No change
Rating
100%
Review 5 out of 5
5
(9 reviews)
Next Milestone 600
500+
600+
255
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 26 more installs to reach 600+
Rank Changes
Current
#8,920
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
9 reviews
Overall
100%
5
9
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 1 of 1| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| administration | 191 | — | Tag | 12 hours ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Security History
Source: WPVulnerability1 known vulnerability on record · 0 in the last 24 months · checked 20 hours ago
-
Slash Admin [slash-admin] < 3.8.2
CVE-2024-32958 · Fixed in v3.8.2
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 3.8.3
- Last Updated
- Mar 01, 2024
- Requires WP
- 5.0+
- Tested Up To
- 6.4
- PHP Version
- 7.0 or higher
- Author
- Giorgos Sarigiannidis
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 9
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
7K+ installs
#2,721
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#991
Site Kit by Google - Analytics, Search Console, AdSense, Speed
5M+ installs
#8
MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)
2M+ installs
#24
ManageWP Worker
1M+ installs
#53
GTM4WP - A Google Tag Manager (GTM) plugin for WordPress
700K+ installs
#82
Header Footer Code Manager
600K+ installs
#104
WP Statistics – Simple, privacy-friendly Google Analytics alternative
600K+ installs
#113
GA Google Analytics – Connect Google Analytics to WordPress
400K+ installs
#147
WP Activity Log
300K+ installs
#180
TL;DR
AI summary of the plugin's readmeSlash Admin is for WordPress site administrators managing sites for both themselves and less-technical editors. It solves the problem of scattered, theme-dependent admin tweaks by centralizing dozens of settings for frontend behavior, admin permissions, login screen customization, white labeling, and performance.
- Static splash page option
- EU Cookie Law consent message
- Loading animation on page load
- Google Analytics tracking code
- Hide Site Health from users
- Maintenance mode for non-admins
- Custom logo on login screen
- Disable Emojis for performance
Frequently Asked Questions
Common questions about Slash Admin
You can enable the following shortcodes: [slash_mail address="yourmail@mail.com"] - disguises the email address to make it unreadable from mail harvesters and displays it as plain text. [slash_mailto address="yourmail@mail.com"] - does the exact same thing, but it also transforms the text to a "mailto" link as well. [slash_mail] and [slash_mailto] (same as above but with no parameters given) automatically retrieve the email address of the author of a post/page. All the above shortcodes use the WordPress' antispambot() function. [slash_phone number="PHONE_NUMBER" prefix="COUNTRY_PREFIX" text="ANCHOR_TEXT"] - Shows 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). The "number" parameter is the only one that is absolutelly required. Here are some usage examples: [slash_phone number="999999"] would output a link "999999" which would make a phone call to 999999. [slash_phone number="999999" prefix="+30"] would output a link "999999" which would make a phone call to +30999999. [slash_phone number="999999" prefix="+30" text="Call us"] would output a link "Call us" which would make a phone call to +30999999. [slash_home] - retrieves the home URI for the current site. It is the equivalent of echoing the home_url(). [slash_theme] - retrieves the template directory URI for the current theme. It is the equivalent of echoing the get_template_directory_uri(). [slash_child] - retrieves the stylesheet directory URI for the current theme/child theme. It is the equivalent of echoing the get_stylesheet_directory_uri().
Slash Admin includes the following functions which you can use in your code: slash_dump() - You can use it instead of var_dump() to wrap the output in <pre></pre> tags, for better readability.
It is up to you to decide whether you will use your theme's options or those provided by this plugin. It is recommended, though, that you keep those settings separated from your theme and the reason is simple: If at some point you decide to switch themes, those options will be lost and you have to remember to re-enter them. Keeping them in a plugin maintains the options between themes.
Generally speaking, no. WordPress' default behaviour is probably the best, that's why the specific option is disabled by default. In some cases, though, users might get confused with those notifications or think that something is wrong with the website. In cases like that, you might want to keep the update notifications visible only for those who can apply them - namely the administrators. Keep in mind that, technically, selecting this option won't remove the notifications for the non-admins - it will just hide them with CSS.
Sometimes you only use certain features of WordPress. For example, your website might have comments disabled or not using the Links feature. Also, for better usability you might want to show your users only the options that concern them. Hiding those options won't remove them. You, as an administrator, will always see the full list of all the available options. An editor, though, won't see the hidden options, which helps him focus to only those that concern him.
You can allow editors access to one or more of the following sub-sections of the "Appearance" section: Customize Widgets Menus Background Technically, by selecting even one of the above options you give editors access to the Appearance section. To prevent them from accessing unwanted subsections (e.g. you want them to see the Menus but not the Widgets) the plugin hides their links via CSS/JavaScript from both the backend and the frontend. If an editor knew the link for the Widgets subsection he/she could access it. By default the plugin respects the WordPress' default behavior, keeping those options disabled (users have no access at all to the Appearance section). Old browser warning behaves strangely with W3TC plugin This is a known issue. When Page Caching is activated in the W3 Total Cache plugin, the old browser warning becomes unpredictable and it may appear not only in Internet Explorer 8 but in newer IE versions as well as in Chrome. To deal with the problem you need to disable either the old IE warning or the W3TC Page Cache option.
