Backend | Wbcom News | Wordpress Experts

Register Settings on WordPress Multisite

December 21, 2011 By Frank Leave a Comment

The use of WordPress for several blogs in the network can be useful to simplify several steps and is becoming increasingly popular. Whether you want the classical scenarios of blog hosting service or like to create multilingual websites or other ideas. Therefore, it is also important for plugin developers to use the functions and to expand or develop their own Plugins for it specifically.

Much is the same, but not all, and in this small article I would like to briefly explain how you set settings in the database when you activate a Plugin.

The best case for this is a Function of WordPress, which is triggered when activating a plugin register_activation_hook(). This Function will be called in init or constructor of the Plugin. In the called Function are the functions to store the settings of WordPress in the table options - add_option(). In Multisite there is also a function for it - add_site_option().

Now you have to separate, if the Plugin is activated within the Network, in the management of Multisite installation, or if it is only used in one of the blogs in the network or a single installation. There are currently no functions, but a value that is passed. The following example illustrates it:

register_activation_hook( __FILE__, 'fb_add_config' );
function fb_add_config() {
        $data = array(
                'active' => 0,
                'radio'  => 0,
                'link'   => 1,
                'theme'  => 1,
                'role'   => 'administrator',
                'unit'   => 1,
        );
        // if is active in network of multisite
        if ( is_multisite() && isset($_GET['networkwide']) && 1 == $_GET['networkwide'] ) {
                add_site_option( 'my_settings_id', $data );
        } else {
                add_option( 'my_settings_id', $data );
        }
}

The query of the value in the global GET can be integrated in the long time ago mentioned solution for Multisite and settings.

To solve other queries in a Multisite environment and to remove the setup or integrate menus in the admin area, the function is_plugin_active_for_network() is useful.

if ( is_multisite() && is_plugin_active_for_network( plugin_basename( __FILE__ ) ) )
        $values = get_site_option( 'my_settings_id' );
else
        $values = get_option( 'my_settings_id' );

Filed Under: Wordpress News Tagged With: Advent Calendar, backend, development, PHP, plugin, WordPress, WordPress Plugins, WP

Restrict Mime Types on WordPress Media Upload

December 17, 2011 By Frank Leave a Comment

WordPress has changed the library in version 3.3 - which I think is an improvement. The restrictions in terms of file types remains and you can control them via hook. So you can limit or extend the file-types. Via two hooks, this is done quickly and there is a notification displayed in your backend which lists the allowed file types.

The following small Plugin may extend to different roles or authorization objects, so that you can upload, depending on the role, different types of files in the system - current_user_can().

Anyone interested in the currently allowed types, you can return the array of the first function or look into the function get_allowed_mime_types() in wp-includes/functions.php.

<?php
/**
 * Plugin Name: Restrict mime types
 * Plugin URI:  http://wpengineer.com/?p=2369
 * Description: Restrict list of allowed mime types and file extensions.
 * Version:     1.0.0
 * License:     GPLv3
 * Author:      Frank Bültge
 * Author URI:  http://bueltge.de/
 */
 // This file is not called from WordPress. We don't like that.
! defined( 'ABSPATH' ) and exit;
// If the function exists this file is called as upload_mimes.
// We don't do anything then.
if ( ! function_exists( 'fb_restrict_mime_types' ) ) {
        add_filter( 'upload_mimes', 'fb_restrict_mime_types' );
        /**
         * Retrun allowed mime types
         *
         * @see     function get_allowed_mime_types in wp-includes/functions.php
         * @param   array Array of mime types
         * @return  array Array of mime types keyed by the file extension regex corresponding to those types.
         */
        function fb_restrict_mime_types( $mime_types ) {
                $mime_types = array(
                        'pdf' => 'application/pdf',
                        'doc|docx' => 'application/msword',
                );
                return $mime_types;
        }
}
// If the function exists this file is called as post-upload-ui.
// We don't do anything then.
if ( ! function_exists( 'fb_restrict_mime_types_hint' ) ) {
        // add to wp
        add_action( 'post-upload-ui', 'fb_restrict_mime_types_hint' );
        /**
         * Get an Hint about the allowed mime types
         *
         * @return  void
         */
        function fb_restrict_mime_types_hint() {
                echo '<br />';
                _e( 'Accepted MIME types: PDF, DOC/DOCX' );
        }
}

Filed Under: Wordpress News Tagged With: Advent Calendar, backend, Code, mediathek, PHP, plugin, WordPress, WordPress Plugins, WP

Activate WordPress Plugins Automatically via a Function

December 13, 2011 By Frank Leave a Comment

WordPress stores the active Plugins in the database table options, field activate_plugins, so it is easy to change this value to activate various Plugins by WordPress; either as a Plugin solution after setting up a new installation or because some Plugins need some other Plugins.

I show you as an example a solution. It is important that you don't use the Plugin names, but the string of the file, which is also required in various hooks. Below you will also find a simple solution to get to this string in your backend.

// example on admin init, control about register_activation_hook()
add_action( 'admin_init', 'fb_activate_plugins' );
// the exmple function
function fb_activate_plugins() {
        if ( ! current_user_can('activate_plugins') )
                wp_die(__('You do not have sufficient permissions to activate plugins for this site.'));
        $plugins = FALSE;
        $plugins = get_option('active_plugins'); // get active plugins
        if ( $plugins ) {
                // plugins to active
                $pugins_to_active = array(
                        'hello.php', // Hello Dolly
                        'adminimize/adminimize.php', // Adminimize
                        'akismet/akismet.php' // Akismet
                );
                foreach ( $pugins_to_active as $plugin ) {
                        if ( ! in_array( $plugin, $plugins ) ) {
                                array_push( $plugins, $plugin );
                                update_option( 'active_plugins', $plugins );
                        }
                }
        } // end if $plugins
}

The following function and its hook provides a direct output of the string of the Plugin file on the Plugin page in your backend, so please use it only for a quick finding.

add_filter( 'plugin_row_meta', 'fb_get_plugin_string', 10, 4 );
function fb_get_plugin_string( $plugin_meta, $plugin_file, $plugin_data, $status ) {
        // echo plugin file string
        echo '<code>' . $plugin_file . '</code><br>';
        return $plugin_meta;
}

Filed Under: Wordpress News Tagged With: Advent Calendar, backend, Code, development, PHP, plugin, WordPress, wordpress hacks, WP

Advent Calendar – WordPress, WPCron and the right Time

December 12, 2011 By Frank Leave a Comment

WordPress offers a pseudo-cronjob functionality, which allows the developer to execute scheduled events. For example, the whole Update Notification does it. In these so-called Scheduled Events you can define your own jobs. Thereby you should however pay attention to one important thing: time.

The wp-cron.php works outside the core and loads only the most important things and leaves all settings of WordPress open. In the Settings -> General set time zone is not included. wp-cron.php runs on UTC.

That means: Are we in the time zone of Berlin, the local time is UTC +1. Are we performing a scheduled event, it will always be one hour after the actual time we like to execute. To change this, we use the following function:

function get_offset_to_gmt_in_seconds() {
        $current_timezone_offset = get_option( 'gmt_offset' );
        $offset = $current_timezone_offset * 3600;
        return $offset;
}

Guest Post

This post is written by Thomas Herzog - hughwillfayle.de and is a guest post on WP Engineer about WordPress.
Thank you very much from my part to Thomas. Please see his nice plugins on the official WordPress repository.
If you also like to have your interesting post published on our website, please let us know on our contact page. Of course we will appreciate your contribution!

Filed Under: Wordpress News Tagged With: Advent Calendar, backend, Code, PHP, WordPress, wordpress hacks, WP

Advent Calendar – WordPress Editor: Preserve the scroll position

December 5, 2011 By Frank Leave a Comment

WordPress has a nice editor, with which are several hundreds of articles written daily.

But in my opinion the editor has an usability issue.
Every time you save a post the scroll position of the editor will be on top again. If you want to continue writing the post you have first to find he old position again. This can be time-consuming.

Save editor scroll position on saving

To avoid this behavior I have written a snippet which I want to share now with you.

<?php
/**
 * The class will help you to recover the old scoll position in your Editor.
 * Either HTML or visuel editor.
 */
final class Preserve_Editor_Scroll_Position {
        /**
         * Init
         */
        public static function init() {
                add_filter( 'redirect_post_location', array( __CLASS__, 'add_query_arg' ) );
                add_action( 'edit_form_advanced', array( __CLASS__, 'add_input_field' ) );
                add_action( 'edit_page_form', array( __CLASS__, 'add_input_field' ) );
                add_filter( 'tiny_mce_before_init', array( __CLASS__, 'extend_tiny_mce' ) );
        }
        /**
         * Adds a hidden input field for scrolltop value
         */
        public static function add_input_field() {
                $position = ! empty( $_GET['scrollto'] ) ? $_GET['scrollto'] : 0;
                printf( '<input type="hidden" id="scrollto" name="scrollto" value="%d"/>', esc_attr( $position ) );
                // Print Javascript data
                add_action( 'admin_print_footer_scripts', array( __CLASS__, 'print_js' ), 55 ); // Print after Editor JS.
        }
        /**
         * Extend TinyMCE config with a setup function
         */
        public static function extend_tiny_mce( $init ) {
                if ( 'tinymce' == wp_default_editor() )
                        $init['setup'] = 'rich_scroll';
                return $init;
        }
        /**
         * Returns redirect url with query arg for scroll position
         */
        public static function add_query_arg( $location ) {
                if ( ! empty( $_POST['scrollto'] ) )
                        $location = add_query_arg( 'scrollto', (int) $_POST['scrollto'], $location );
                return $location;
        }
        /**
         * Prints Javascript data
         */
        public static function print_js() {
                ?>
        <script>
        ( function( $ ) {
                $( '#post' ).submit( function() {
                        scrollto =
                                $( '#content' ).is( ':hidden' ) ?
                                $( '#content_ifr' ).contents().find( 'body' ).scrollTop() :
                                $( '#content' ).scrollTop();
                        $( '#scrollto' ).val( scrollto );
                } );
                $( '#content' ).scrollTop( $( '#scrollto' ).val() );
        } )( jQuery );
        function rich_scroll( ed ) {
                ed.onInit.add( function() {
                        jQuery( '#content_ifr' ).contents().find( 'body' ).scrollTop( jQuery( '#scrollto' ).val() );
                } );
        };
        </script>
                <?php
        }
}
add_action( 'plugins_loaded', array( 'Preserve_Editor_Scroll_Position', 'init' ) );

If you want you can create your own plugin with this snippet or you can download the plugin Preserve Editor Scroll Position.

Guest Post

This post is written by Dominik Schilling - wpgrafie.de and is a post in our Advent Calendar on WP Engineer about WordPress. Dominik is Student, Web Developer, WordPress Contributing Developer - ocean90 and he ♥ WordPress.
Thank you very much from my part to Dominik.
If you also like to have your interesting post published on our website, please let us know on our contact page. Of course we will appreciate your contribution!

Filed Under: Wordpress News Tagged With: Advent Calendar, backend, Code, JavaScript, PHP, WordPress, wordpress hacks, WP

Here’s a Thanksgiving surprise I got from Twitter today.

November 25, 2011 By pramod

Konstantin Kovshenin: Here’s a Prayer surprise I ɡοt frοm Twitter today. Seriously, I’ve ɡοt a dozen …

Account Suspended

Here’s a Prayer surprise I ɡοt frοm Twitter today. Seriously, I’ve ɡοt a dozen accounts fοr brands аnԁ experiments I rυn bу thе Twitter API, bυt never οn mу οwn аnԁ аmυѕіnɡ thing, thе surplus аrе hοnеѕt bυt mine’s floating, аnԁ nο single e-e-mail frοm thеm іn mу inbox! Contacting Twitter hеƖр, Ɩеt’s see whаt thеу hаνе tο ѕау.

PƖеаѕеԁ Prayer!

Source: Here’s a Prayer surprise I ɡοt frοm Twitter today. Seriously, I’ve ɡοt a dozen …

Konstantin Kovshenin: Varnish аnԁ Preview Posts іn WordPress

I wrote earlier thаt I ѕtаrtеԁ playing around wіth Varnish here οn mу site аnԁ thаt post hаѕ a small fragment thаt strips аƖƖ incoming аnԁ outgoing cookies (except thе admin οf course.) Today I stumbled οn a conundrum whеrе I hаԁ nο permission tο preview a post I wаѕ drafting іn WordPress аnԁ thеу аƖƖ twisted 404′s whеn I tried tο.I first thουɡht Varnish wаѕ stripping out thе preview query string bυt I wаѕ incorrect, thе conundrum wаѕ thаt WordPress nеw I wаѕ logged іn аnԁ editing thе post whеn I wеrе іn thе admin panel, bυt whеn I tried tο preview іt οn thе front еnԁ Varnish wаѕ stripping out mу login cookies, hence іt didn’t ѕhοw mу draft post.Here’s a fragment fοr vcl_recv аnԁ vcl_fetch thаt ѕhουƖԁ ɡο before thе unset cookies statement whісh passes thе request tο thе web server іf preview=rіɡht іѕ found іn thе request URL.

іf (req.url ~ "preview=rіɡht") {
        return(pass);
}

Regenerate thе Varnish service аnԁ voila! Yουr cookies aren’t stripped out anymore аnԁ уου саn now preview уουr posts аnԁ pages. Dο annotation even іf thаt іf somebody manually types іn thе preview query string іn thе browser, thеу’ll bу-pass Varnish аѕ well.Source: Varnish аnԁ Preview Posts іn WordPress bу Konstantin Kovshenin

WordPress.com Hearsay: Nеw Themes: Shaan аnԁ Adventure Journal

I’m рƖеаѕеԁ tο introduce two nеw сοοƖ аnԁ quaint themes: Adventure Journal Shaan іѕ a charming-discussion theme, quietly delivering a сοοƖ, casual backdrop fοr уουr ɡеt οn tο рƖеаѕеԁ. It’s perfect fοr writers whο Ɩіkе a сοοƖ, сοοƖ down tone tο thеіr blog. If уου υѕе descriptions tο illustrate уουr writing, уου’ll Ɩіkе hοw Shaan displays featured descriptions іn two sizes: small іn archives аnԁ search consequences, аnԁ generous fοr sticky posts οn уουr home page аѕ well аѕ οn single posts аnԁ pages.

Model οf Shaan іn proceedings. Designed bу Specky Bore, Shaan іѕ available today іn уουr WordPress.com dashboard аnԁ directly frοm thе Theme Showcase. Hаνе a well-traveled blog? Adventure Journal іѕ a natural fit fοr highlighting уουr adventures. A theme fοr уουr next trip. Or уουr next blog.

Model οf thе Adventure Journal front page. Featuring a lukewarm wood social class, a slogan persona fοr уουr favorite photo, widget areas styled οn curling paper, аnԁ a crinkled sticky post area fοr persons vital notes—thіѕ theme іѕ satiated οf rustic charm. Customize іt wіth layout options, sidebar аnԁ footer widgets, аnԁ extra. See аƖƖ thе options аnԁ details οn thе Theme Showcase. Designed bу Contexture International, Adventure Journal іѕ available іn уουr dashboard аnԁ directly frοm thе Theme Showcase.

AƖѕο… PƖеаѕеԁ Prayer! Wе hope уου gobble thеѕе themes up.

Justin Tadlock: Mу Life theme testing I’m currently testing out thе Mу Life theme here οn mу blog. If уου’re a member οf Theme Hybrid, уου саn grab a beta copy οf іt frοm theTheme Hybrid forums tο mess аbουt around wіth іt before release. WordPress.com Hearsay: Code іѕ Poetry, CSS іѕ Art Wе want tο aid уουr websites come alive wіth ɡοrɡеουѕ point. Thе WordPress.com theme team hаѕ bееn count nеw themes аt a dazzling rate, bυt ԁіԁ уου know уου саn customize thе style οf аnу οf ουr themes bу thе Custom Point upgrade?

CSS stands fοr Cascading Style Sheets whісh аrе styles thаt define hοw tο ѕhοw HTML elements. Yου саn ԁο anything frοm changing font colors tο styling аn entire site frοm scrape bу CSS.

Nοt single ԁοеѕ thе Custom Point upgrade Ɩеt уου point out frοm 50+ custom fonts іn thе Fonts tab, іt includes a CSS editor whеrе уου саn keep style rules wіth purchasing thе upgrade οr preview changes before export.

Whether уου аrе a point expert οf іnсrеԁіbƖе talent proportions οr уου аrе јυѕt learning thе ways уου саn bend websites tο уουr wіƖƖ, wе rесkοn уου’ll Ɩіkе mаkіnɡ уουr WordPress.com sites even extra ɡοrɡеουѕ wіth custom CSS. Beginners саn initiation wіth thе CSS Basics aid page. AƖƖ іѕ always salutation tο impart approximately CSS Ɩіkе іn theWordPress.com CSS Customization forum whеrе happiness engineers аnԁ amazingly tireless volunteers aid wіth CSS qυеѕtіοnѕ. Tο inspire уου, here аrе a few prominently different Twenty Eleven theme variations currently income аt WordPress.com owing tο bу ουr very οwn Automatticans:

mattnt.com simpledream.net myphotomaton.wordpress.com

If уου аrе a WordPress.org user, never ԁrеаԁ! Yου саn υѕе theWordPress.com CSS plugin tο ɡеt a CSS editor thаt won’t modify theme files, keeping thеm crinkle-free аnԁ simple-tο-update.

Gο tο Advent → Custom Point → CSS іn уουr dashboard аnԁ try out approximately CSS edits!

WP Persuade: Uѕе Constants fοr deactivate thе Editor іn WordPress Backend

WordPress іѕ known fοr, thаt several constants lie dormant іn thе core аnԁ regularly grant qυісk solutions. In thіѕ context I hаνе recently come асrοѕѕ two small strings іn thе core οf thе backend editor οf WordPress аnԁ іn thе core fοr updating thе logic аѕ well. Aѕ far аѕ I know, аƖƖ constants mentioned here аrе іn thе logic ѕіnсе translation 3.0. Thе first constant takes οff thе editors οf thе backend аnԁ ԁοеѕ nοt allow access tο іt. Thіѕ mаkеѕ thе editing οf Theme аnԁ Plugin files οf thе backend wіth ordinary solutions nοt possible.

// fοr enabling/disabling theme/plugin editor define( ‘DISALLOW_FILE_EDIT’, TRUE );

Thе second constant open here prohibits editing, modifying οr changing thе core files, Plugins οr Themes. In thіѕ context thе menu entries іn thе backend аrе nοt visible οr usable. Thus thе update іѕ nοt ѕο simple tο ԁο аnԁ clients аnԁ unauthenticated users аrе blocked quickly. // Disallow anything thаt mаkеѕ, deletes, οr edits core, plugin, οr theme files. // Files іn uploads аrе excepted. define( ‘DISALLOW_FILE_MODS’, TRUE );

In thіѕ context here аrе two constants thаt аrе useful now аnԁ thеn. In innumerable contexts іt іѕ very useful thаt аƖƖ users hаνе thе option οf: tο write unfiltered HTML, іn аƖƖ aspects аnԁ thіѕ саn аƖѕο bе easily implemented via constants:

// Disallow unfiltered_html fοr аƖƖ users, even admins аnԁ super admins DISALLOW_UNFILTERED_HTML

Similar unfilled fοr uploads:

// Allow uploads οf filtered file types tο users wіth administrator role ALLOW_UNFILTERED_UPLOADS

Thе constants belong іn thе wp-config.php οf thе installation.

Filed Under: Wordpress News Tagged With: backend, News, page, Shaan, Themes, WordPress

Use Constants for deactivate the Editor in WordPress Backend

November 23, 2011 By Frank

WordPress is known for, that several constants lie dormant in the core and often provide quick solutions. In this context I have recently come across two little strings in the core of the backend editor of WordPress and in the core for updating the system as well. As far as I know, all constants mentioned here are in the system since version 3.0.

The first constant takes off the editors of the backend and does not allow access to it. This makes the editing of Theme and Plugin files of the backend with standard solutions not possible.

// for enabling/disabling theme/plugin editor
define( 'DISALLOW_FILE_EDIT', TRUE );

The second constant presented here prohibits editing, modifying or changing the core files, Plugins or Themes. In this context the menu entries in the backend are not visible or usable. Thus the update is not so easy to do and clients and unauthenticated users are blocked quickly.

// Disallow anything that creates, deletes, or edits core, plugin, or theme files.
// Files in uploads are excepted.
define( 'DISALLOW_FILE_MODS', TRUE );

In this context there are two constants that are useful now and then.

In various contexts it is very useful that all users have the option of: to write unfiltered HTML, in all aspects and this can also be easily implemented via constants:

// Disallow unfiltered_html for all users, even admins and super admins
DISALLOW_UNFILTERED_HTML

Similar existing for uploads:

// Allow uploads of filtered file types to users with administrator role
ALLOW_UNFILTERED_UPLOADS

The constants belong in the wp-config.php of the installation.

Filed Under: Wordpress News Tagged With: backend, Code, PHP, security, WordPress, wordpress hacks, WP, WP3.0

How to Add and Deactivate the new Feature Pointer in WordPress 3.3

September 21, 2011 By Frank

With WordPress version 3.3 comes with the Feature Pointer a well-known idea from other tools. We know this for example from Gmail or Google Doc where they notice you of new features, in which they point with bubbles to these new features. In WordPress 3.3, the Admin Bar has been redesigned successfully - I think - and this is the first time the feature pointer points to it.

If you are in the environment of customers, it may be that you don't want the feature pointer - different scenarios are possible. But here it also relies on the WordPress hooks so you can intervene in various ways. One idea is to adjust the user settings of the user, as the feature pointer is using Javascript to drop an option in the table, so that the user does not read the instructions again. Alternatively, you can disable it via hook, following solution paste into a small Plugin or the functions.php of your theme (whereas the second solution isn't the best).

<code>
add_filter( 'show_wp_pointer_admin_bar', '__return_false' );
</code>

If you don't have the admin bar not active, then it won't show a feature pointer to it.

Also you can use the hooks to create your own feature pointer. Without adjustment in the design and position is the following simple example conceivable. If the position is changed, it is sufficient to adapt the script section JS-function pointer() in the PHP function get_content_in_wp_pointer(). The function pointer() can be controlled by various parameters (content, position, arrow) .

function get_content_in_wp_pointer() {
        $pointer_content  = '<h3>' . __( 'WP Pointer with version 3.3.', 'my_textdomain' ) . '</h3>';
        $pointer_content .= '<p>' . __( 'Add your own informations to WP Pointer.', 'my_textdomain' ) . '</p>';
?>
<script type="text/javascript">
//<![CDATA[
jQuery(document).ready( function($) {
        $('#wpadminbar').pointer({
                content: '<?php echo $pointer_content; ?>',
                position: {
                        my: 'left top',
                        at: 'center bottom',
                        offset: '-25 0'
                },
                close: function() {
                        setUserSetting( 'p1', '1' );
                }
        }).pointer('open');
});
//]]>
</script>
<?php
}
function fb_enqueue_wp_pointer( $hook_suffix ) {
        $enqueue = FALSE;
        $admin_bar = get_user_setting( 'p1', 0 ); // check settings on user
        // check if admin bar is active and default filter for wp pointer is true
        if ( ! $admin_bar && apply_filters( 'show_wp_pointer_admin_bar', TRUE ) ) {
                $enqueue = TRUE;
                add_action( 'admin_print_footer_scripts', 'get_content_in_wp_pointer' );
        }
        // in true, include the scripts
        if ( $enqueue ) {
                wp_enqueue_style( 'wp-pointer' );
                wp_enqueue_script( 'wp-pointer' );
                wp_enqueue_script( 'utils' ); // for user settings
        }
}
add_action( 'admin_enqueue_scripts', 'fb_enqueue_wp_pointer' );

Please note: The implementation is based on a nightly build of WordPress, not the final Release 3.3 and thus might have some changes or other solutions are possible in a later version. Therefore, please validate according to the version of WordPress the solution. As a tip this should be enough - anything else is creativity and your skills.

Filed Under: Wordpress News Tagged With: backend, Code, development, PHP, WordPress, WP, wp3.3

Remove Menu Item in WordPress Admin Panel

July 12, 2011 By Frank

With WordPress Version 3.1 two new functions were added which makes it easier to remove menu- and submenu-entries in WordPress Admin Panel. These functions removing entries of the menu-tree remove_menu_page or submenus - remove_submenu_page.

/**
 * Remove a top level admin menu
 *
 * @param string $menu_slug The slug of the menu
 * @return array|bool The removed menu on success, False if not found
 */
remove_menu_page( $menu_slug )

/**
 * Remove an admin submenu
 *
 * @param string $menu_slug The slug for the parent menu
 * @param string $submenu_slug The slug of the submenu
 * @return array|bool The removed submenu on success, False if not found
 */
remove_submenu_page( $menu_slug, $submenu_slug ) {

It's easy to remove menu entries and it is not necessary anymore to read the arrays $menu and $submenu. Until now you had to search for them in the array and remove them via unset() from the array. Alternatively you were also able to find the entry on the basis of a key - the above new features make this unnecessary and as a parameter value only the "slug" is passed, which can be found in the link or the URL of the backend. A small example, where we remove the entries to the comments and the submenu-page discussion will show the new possibilities.

function fb_remove_menu_entries () {
        // with WP 3.1 and higher
        if ( function_exists( 'remove_menu_page' ) ) {
                remove_menu_page( 'edit-comments.php' );
                remove_submenu_page( 'options-general.php', 'options-discussion.php' );
        } else {
                // unset comments
                unset( $GLOBALS['menu'][25] );
                // unset menuentry Discussion
                unset( $GLOBALS['submenu']['options-general.php'][25] );
        }
}
add_action( 'admin_menu', 'fb_remove_menu_entries' );

The above code provides a simple solution, removed the two entries and also has a fallback for WordPress, smaller version 3.1. It is also conceivable that the removal is also connected with user rights

if ( function_exists( 'remove_menu_page' ) && ! current_user_can( 'manage_options' ) ) {

so it would be possible to optimize the menu explicitly for a user. Alternatively, the plug Adminimize helps and facilitates the job via admin area.
You can also read about this topic on Justin's post, but my post was an older draft and now was published - the topic is worth it.

Filed Under: Wordpress News, Wordpress Tutorials Tagged With: backend, Code, development, PHP, plugin, WordPress, wp3.1

New Plugin to Style your Plugin on WordPress Admin with Default Styles!

May 31, 2011 By Frank

WordPress is developing fast - this also applies to the design of the backend. So it is important not to use your own styles in the admin area and use tags and classes of WordPress. This is the best way you can simplify your work as a developer and you don't have to test the design with every update. Unfortunately, there are quite extensive opportunities in the backend to implement the requirements. Several different classes and HTML structures are used. To be able to look up something this simple, I have developed a small Plugin, which tinkers in the development environment and quickly represents the necessary elements. Here you see two screenshots with the differences between version 3.1 and 3.2 of WordPress and the current contained elements of the Plugin.

You can find the Plugin in Github and it would be great if you expand it, add new ideas and possibilities to it: - github.com/bueltge/WordPress-Admin-Style

Filed Under: Wordpress News Tagged With: backend, Code, Design, development, PHP, plugin, WordPress, WordPress Plugins

Register Settings on WordPress Multisite

Restrict Mime Types on WordPress Media Upload

Activate WordPress Plugins Automatically via a Function

Advent Calendar – WordPress, WPCron and the right Time

Guest Post

Advent Calendar – WordPress Editor: Preserve the scroll position

Guest Post

Here’s a Thanksgiving surprise I got from Twitter today.

Use Constants for deactivate the Editor in WordPress Backend

How to Add and Deactivate the new Feature Pointer in WordPress 3.3

Remove Menu Item in WordPress Admin Panel

New Plugin to Style your Plugin on WordPress Admin with Default Styles!

Popular Search Terms

Recent Posts

Archives