WordPress 3.1 will probably be launched in the upcoming weeks; also it brings with it a couple of major changes. If you daily use WordPress, you may well not instantly notice several updates; but if you’re a WordPress Multi Site subscriber, the alterations will in all probability appear somewhat revolutionary.

The main modification for WordPress Multi Site is the separation of the Network Administration region. Super Admin set is vanishing and being substituted with a latest admin dashboard for Super Admin users. Developers those primarily generated their plugins companionable with WordPress Multi Site or WordPress MU will have to make some slight changes to make their plugins suitable for WordPress 3.1.

Rather than utilizing the add_submenu_page () function to adjoin your alternatives page to the ms-options.php page, you will have to include your alternatives page to the settings.php page. The key variation, though, is the fact that you’ll need to hook to the network_admin_menu action as opposed to the admin_menu action. Consequently, the brand new code to set up an alternatives page would look like:

add_action( 'network_admin_menu', 'pluginname_setup_admin' );
function pluginname_setup_admin()

{
/* Add the new options page to the Super Admin menu */
add_submenu_page
(
/*$parent_slug = */'settings.php',
/*$page_title = */'Plugin Settings',
/*$menu_title = */'Plugin Name',
/*$capability = */'delete_users',
/*$menu_slug = */basename(__FILE__),
/*$function = */'pluginname_display_admin_page'
);
}

Another major alternation in WordPress - and many backend users will most likely notice this - may be the addition of the admin bar. If you have used BuddyPress in the past, you are most likely employed to the admin bar turning up towards the apex of the screen. Basically, it’s a set menu bar that provides you access to some of the actions you utilize most usually using the WordPress admin area.

Other changes happen to be made to the code within WordPress to optimize definite actions and usually make things happen more swiftly and simply within the backend.