How to Create a WordPress Plugin Administration Section

29 July 2013

Brisbane: In this article, I would like to show you how to put in administrative features to the back end of WordPress so that your plugin can be dealt with using the standard user interface.

During the file structure setup portion you need to include a folder labeled “admin” and a file named “super-plugin-admin.php”:

+ super-plugin

           + admin

           - super-plugin-admin.php

           + img

           - icon.png

           + js

           - super-plugin.js

- super-plugin.php

- readme.txt

You can put in any added support files that you need for your plugins administration under the admin folder, including things like images, css, and javascript. While it’s not essential to put your administration files under a separate directory, I find it much more planned to go that route than to just stuff everything into the root of your plugin directory.

Initialize your Admin features

Just like with the client side portion of the plugin, the admin features can be initialized within your main super-plugin.php file. You can do this either by introducing the necessary code directly inside of this file, or by creating a new file to hold your administrative settings and simply reference the file from within the main super-plugin.php script.

For simplicities sake, we will do our administrative work in the same super-plugin.php file.

The first thing to do is to give some way for the user to get to your settings page. We can do this by listing a menu item in the administration section of WordPress.

To do this we will:

  1. Create a function to register the menu
  2. Create an action hook to trigger the registration
  3. Create a function to build the HTML for the page


function super_plugin_menu(){

          add_options_page(Super Plugin Options', 'Super Plugin', 'manage_options', 'super-plugin-menu', 'super_plugin_options');





function super_plugin_options(){



Step 1 probably needs a little explanation. The add_options_page function is a WordPress function which takes the following parameters:

  • Page Title (a string for the title tag)
  • Menu Title (a string for the menu label)       
  • Capability (a string for the permissions required to access this menu)
  • Unique Identifier (a unique string for the menu slug)
  • Callback Function (the function to call when the menu is clicked)

So as you can see, when you click on the menu item we’ve just created, the function super_plugin_options() will be called. All that function does is pull in the admin file we created in admin/super-plugin-admin.php.

Build your Admin interface and Actions

To put up your administrative interface, start by populating the super-plugin-admin.php file with HTML. A fairly standard way to begin this file is with the following HTML:

<div class="wrap">

<h2>Super Plugin</h2>

<h3>Super Plugin Options</h3>


After the H3 tag you can begin filling the accessible options for your plugin. A simple scenario is the case where you have to to store a few option values for your plugin. You can do this by using WordPress’s built in option management framework.

First we need to register our settings for the admin section. Back in the super-plugin.php file, add to the super_plugin_menu() function another action hook and the actual settings function:

function super_plugin_menu(){

add_options_page(Super Plugin Options', 'Super Plugin', 'manage_options', 'super-plugin-menu', 'super_plugin_options');

//call register settings function

add_action( 'admin_init', 'register_mysettings' );


function register_mysettings() {

//register our settings

register_setting( 'super-settings-group', 'new_option_name' );

register_setting( 'super-settings-group', 'some_other_option' );

register_setting( 'super-settings-group', 'option_etc' );


Currently, in your super-plugin-admin.php file you can take benefit of the WordPress settings API to do the heavy lifting for you. By create an HTML form which posts to the options.php page, you can promptly create the settings page for your plugin:

<div class="wrap">

<h2>Super Plugin</h2>

<h3>Super Plugin Options</h3>

<form method="post" action="options.php">

<?php settings_fields( 'super-settings-group' ); ?>

<?php do_settings( 'super-settings-group' ); ?>

<table class="form-table">

<tr valign="top">

<th scope="row">New Option Name</th>

<td><input type="text" name="new_option_name" value="<?php echo get_option('new_option_name'); ?>" /></td>


<tr valign="top">

<th scope="row">Some Other Option</th>

<td><input type="text" name="some_other_option" value="<?php echo get_option('some_other_option'); ?>" /></td>


<tr valign="top">

<th scope="row">Options, Etc.</th>

<td><input type="text" name="option_etc" value="<?php echo get_option('option_etc'); ?>" /></td>



<?php submit_button(); ?>




We’ve now created a WordPress plugin which can be administered using a custom menu in the back end of WordPress and can even create and save custom settings for the plugin as well. While this instance plugin doesn’t do much, it’s all hooked up to start carrying out any task you may need.

Read more: WordPress Plugin Development

Why Fortune Innovations?

  • Cost-saving for your projects, up to 40%
  • Hire web development and web designing specialists
  • Project management based out in Brisbane
  • 50 plus strong off shore development team based in Bangalore, India
  • Expert teams well verse with Web 2.0 standards
  • Quality-driven delivery model
  • Detailed time sheets, daily reporting and regular status updates
  • WordPress Development in Brisbane
  • Drupal Development in Brisbane
  • Joomla Development in Brisbane
  • eCommerce Magento Brisbane
  • Web Development Brisbane
  • Web Design Brisbane
  • jQuery development Brisbane
  • Zend framework development Brisbane
  • Airline IBE GDS Integration Navitaire Brisbane
  • Airline IBE GDS Integration Aamadeus Brisbane