{"id":138641,"date":"2015-03-12T07:00:00","date_gmt":"2015-03-12T11:00:00","guid":{"rendered":"http:\/\/premium.wpmudev.org\/blog\/?p=138641"},"modified":"2016-12-22T23:32:28","modified_gmt":"2016-12-22T23:32:28","slug":"simplify-wordpress-backend","status":"publish","type":"post","link":"https:\/\/wpmudev.com\/blog\/simplify-wordpress-backend\/","title":{"rendered":"Tips for Simplifying WordPress to Make it Client-Friendly"},"content":{"rendered":"

The WordPress backend is great if you’re used to it, but if you’re new to WordPress it definitely\u00a0comes with\u00a0a learning curve.<\/h2>\n

Average users usually spend their time in the posts section so why give them all those unrelated options? Clients could inadvertently switch or edit themes, or even disable plugins needed to run the site.<\/p>\n

Even if your client is well-behaved, perhaps you could do a little something to raise the efficiency of his or her day-to-day workload? Removing menu items, disabling plugin deactivation, modifying the dashboard, adding notices in the backend and so on.<\/p>\n

In this article I’ll show you some techniques to help you\u00a0streamline the WordPress backend for yourself or for your clients. We’ll look at some code-based solutions as well as\u00a0plugins.<\/p>\n

Removing Menu Items<\/h3>\n

Removing all that clutter in the admin menu on\u00a0the left-hand side of the screen is a good step toward WordPress zen. One handy method is to use Editor roles for your clients. This will remove tools, settings and a lot of plugin-specific menu items from view.<\/p>\n

\n
\n
\"Editor\"<\/div>\n<\/div>\n<\/div>\n

This is not a perfect solution, however. You may want to hide W3 Total Cache from your clients, but not Advanced Custom Fields. In this case you’ll need to get your hands dirty with some code.<\/p>\n

One way to remove menus is with remove_menu_page()<\/a><\/code> and remove_submenu_page()<\/a>.<\/code>\u00a0Just add the following snippet to your functions.php file:<\/p>\n

Loading gist 72db8fd0fed3941e4425<\/a>

Please update your cookie preferences<\/a> to enable preference cookies to view this gist.<\/p><\/div><\/div>\n

The functions need to be called from within a function hooked to admin_menu<\/code>. The example above removes the tools and settings menu. I used the current_user_can()<\/code> function to make sure the menus were only removed for non-admins.<\/p>\n

A note about safety: Removing the menu entries does not mean the page is there. With the correct URL you could still get to this page – you’re just taking away easy access.<\/p>\n

Sub-menu elements can also be removed. If you are using the excellent Theme Check<\/a> plugin you may want to hide the entry, but not the whole appearance menu where it resides.<\/p>\n

Loading gist 72db8fd0fed3941e4425<\/a>

Please update your cookie preferences<\/a> to enable preference cookies to view this gist.<\/p><\/div><\/div>\n

To figure out the two arguments I looked at the URL. themes.php<\/code> is the slug of the parent element and themecheck<\/code> is the slug of the sub-menu.<\/p>\n

Disable Theme and Plugin Editing<\/h3>\n

By defining a constant in the wp-config.php<\/code> file you can remove the file editing options in the plugins and appearance section. Most clients don’t need this at all anyway so disabling it could be a step forward.<\/p>\n

Loading gist 72db8fd0fed3941e4425<\/a>

Please update your cookie preferences<\/a> to enable preference cookies to view this gist.<\/p><\/div><\/div>\n

The good news is that this doesn’t just hide the menu entry, it actually disables editing. Even if you know the URL you won’t be able to modify the theme or plugins through the admin.<\/p>\n

Modify the Dashboard<\/h3>\n

Before we use code, don’t forget the screen options tab at the top of the page! It contains checkboxes to enable\/disable content on many screens. On the dashboard it allows you to switch each widget on and off.<\/p>\n

If your client needs occasional access to some widgets it may be best to educate them instead of hiding things from view permanently.<\/p>\n

Removing Widgets<\/h4>\n

Removing widgets is easier than adding them, but it is less logical. WordPress doesn’t have a great system for handling the registration of widgets so we have to resort to complex arrays. The core of it all is the $wp_meta_boxes<\/code> variable which is an array of all registered dashboard widgets.<\/p>\n

$wp_meta_boxes['dashboard']['side']<\/code> holds all the right-hand widgets, $wp_meta_boxes['dashboard']['normal']<\/code> holds all the left side ones. It is easiest to print the array, search for what you need and unset it. To disable the Quick Press section you could use something like this:<\/p>\n

Loading gist 72db8fd0fed3941e4425<\/a>

Please update your cookie preferences<\/a> to enable preference cookies to view this gist.<\/p><\/div><\/div>\n

Adding Widgets<\/h4>\n

Widgets can be added using the wp_add_dashboard_widget()<\/code> function. Once added, a widget can hold any type of content. From instructional videos to orientation messages and complex Javascript powered sales graphs, you can do anything.<\/p>\n

Loading gist 72db8fd0fed3941e4425<\/a>

Please update your cookie preferences<\/a> to enable preference cookies to view this gist.<\/p><\/div><\/div>\n

The code above creates a simple widget with some text. Replace the text with any HTML you need to get the job done.<\/p>\n

Even a simple text-based widget could help a lot! You could add some guidelines and helpful links within a dashboard widget.<\/p>\n

Loading gist 72db8fd0fed3941e4425<\/a>

Please update your cookie preferences<\/a> to enable preference cookies to view this gist.<\/p><\/div><\/div>\n

And here’s what it looks like in action:<\/p>\n

\n
\"Simple<\/div>\n<\/div>\n

Don’t forget that you can add any HTML in there and attach scripts and styles. This allows you to create anything from sales graphs to dynamic slideshows. We have a more in-depth article on Adding Custom Dashboard Widgets<\/a> which shows you how to create a comment trend bar chart like the image below – take a look if you want to learn more.<\/p>\n

\n
\n
\"Comment<\/div>\n<\/div>\n<\/div>\n

Adding Help Text<\/h3>\n

WordPress has a great system for adding help text into the help section at the top of various screens. The tab to open this section is just next to the screen options and contains some basic information.<\/p>\n

\n
\"help-section\"<\/div>\n<\/div>\n

You can add content there yourself and even better – add custom help text for your custom post types and other pages. All you need is the add_help_tab()<\/code> function.<\/p>\n

Loading gist 72db8fd0fed3941e4425<\/a>

Please update your cookie preferences<\/a> to enable preference cookies to view this gist.<\/p><\/div><\/div>\n

The code above adds an additional entry in the post section. You can target other screens by adding a post type or the name of the screen you are on. Print the value of the $screen<\/code> variable to see what the contents are on each page.<\/p>\n

\n
\n
\"Custom<\/div>\n<\/div>\n<\/div>\n

Disable Theme Deactivation<\/h3>\n

You can prevent clients from deactivating specific plugins with a little bit of code. We’ll leverage the plugin_action_links<\/code> hook to modify the display of links next to specific plugins.<\/p>\n

Loading gist 72db8fd0fed3941e4425<\/a>

Please update your cookie preferences<\/a> to enable preference cookies to view this gist.<\/p><\/div><\/div>\n

The $plugins<\/code> array contains the list of plugins you want to prevent from being disabled. If you’re not sure what string to add here simply print the $plugin_file<\/code> variable which is passed to the function and find the plugin you need there.<\/p>\n

Require and Recommend Plugins<\/h3>\n

Another way to manage required plugins \u2013 and also recommend some \u2013 is to use the awesome TGM Plugin Activation<\/a> class. By utilizing this class you can set your requirements and pull them in from the repository or even attach your own plugins to the theme as zip files.<\/p>\n

\n
\n
\"TGM<\/div>\n<\/div>\n<\/div>\n

TGM has excellent documentation, take a look at the link above for all the code you’ll need to make this happen.<\/p>\n

Admin Themes<\/h3>\n

Creating an environment where the user feels good is a big part of a successful project. The WordPress admin interface may be perfectly functional but this may not be enough. Admin themes are not as prevalent as their front-end counterparts and most of the better ones are premium themes but they can be worth their price.<\/p>\n

\n
\n
\"Slate<\/div>\n<\/div>\n<\/div>\n

Admin themes, like Slate<\/a> pictured above are actually plugins. You can find them throughout the plugin repository as well as on marketplaces like CodeCanyon. We have a roundup of admin themes<\/a> if you’re interested in a select few.<\/p>\n

Using Plugins to Simplify the\u00a0Backend<\/h3>\n

A number of plugins have been made to make the WordPress admin interface more user friendly, easier to use, or add missing functionality. The plugins below are just some of the ones you can use to tailor the backend to your client.<\/p>\n