janekniefeldt

Use this plugin to create your own widgets, duplicate existing widgets and arrange them in a sidebar or anywhere else. 
Thanks to filter definitions you can decide whether the widget should be displayed or not for specific pages or page-types.
This plugin does not work with WordPress 2.7.1 and below. 
If you are using WordPress 2.2 – 2.7.x please use Release 1.9.1 of this plugin.
The following features have been implemented:
<ul>
<li>define own widgets with php and/or html code </li>
<li>decide where your widget should be displayed (e.g. archive-page only)</li>
<li>define your own filters through plugin configuration</li>
<li>widget-titles that fit into your theme can be defined and changed comfortable as well</li>
<li>Debug-mode for code review</li>
<li>apply_filter-functionality can be activated within CustomWidgets </li>
<li>widgets are also available through custom tags such as <!–MyWidget–> 
and can be used outside of the sidebar as well</li>
<li>duplicate/copy existing widgets (beta feature)</li>
<li>deinstallation routine to remove all option entries created by the plugin </li>
<li>Backup routine for widget- and plugin-configuration</li>
</ul>

My Custom Widgets

Plugin to create your own custom widgets.

nosurs

Intuitively harmonize meta box positions and screen column layout for all backend users of your WordPress installation.
<h4>Quick Overview</h4>
<ul>
<li>Install and activate the plugin</li>
<li>Switch to a post, a page, a custom post type, or the dashboard</li>
<li>Change the order and position of a meta box (or all of them)</li>
<li>Change the column layout</li>
<li>Switch to a different user (maybe with the help of the <a href="https://wordpress.org/plugins/user-switching/" rel="ugc">User Switching</a> plugin)</li>
<li>See your changes applied </li>
</ul>
<h4>Installation</h4>
Download and unpack, then move the folder ‘global-meta-box-order’ into your ‘plugins’ folder. Head over to your WordPress installation and activate the plugin in the admin area.
<h4>Rollback</h4>
The plugin doesn’t write anything to the database, it just reads. So it never touches any user settings, but instead filters them on a per request basis. Though all applied changes appear to be permanent from a user’s perspective, they are not. Just deactivate the plugin and see all changes disappear. Activate it again, and they will all be reapplied.
<h4>How It Works</h4>
The plugin operates on a blueprint user whose screen settings for meta boxes (visibility, position and ordering), and column layout are cloned for all other backend users on the fly.
By default, this blueprint user is the first admin user found, so you’ll need to be logged in as that user to globally change screen settings. For how to change the default blueprint user as well as other settings, please refer to the Configuration section below.
<h4>Where It Works</h4>
By default, the plugin kicks in when a user:
<ul>
<li>edits a post</li>
<li>edits a page</li>
<li>edits a custom post type</li>
<li>hits the dashboard</li>
</ul>
<h4>What It Changes</h4>
It will always change
<ul>
<li>the meta boxes visibility, ordering, and column positions</li>
<li>the column layout</li>
</ul>
When told so, it will also
<ul>
<li>remove the screen options box</li>
<li>immobilize all boxes, so they can’t be moved around by your users anymore</li>
</ul>
<h4>Usage</h4>
Log in as your blueprint user. By default, the is the first admin user found in your system.
Select an editing screen (post, page, custom post type) or the dashboard, move the meta boxes around, change their screen settings and the screen’s column layout. Switch to some user to review your settings, switch back to adjust them.
When done, you might want to lock your views down by removing the screen options box and by locking the boxes’ sort order. Your blueprint user, of course, wil not be affected by this.
<h4>Configuration</h4>
The backend integration is kept to a minimum. No navigation entry, no options page, no entry in the database. Instead, the place to go to configure the plugin is your theme’s functions.php.
By the way: You don’t need to configure the plugin. As long as it finds an admin user, it will work just fine.
Preparation
Fire up an editor, load your functions.php, and copy and paste the following code into it. The idea is to have some sort of container to do the configuration in, but do it any way you like.
For brevity, we’ll assume the plugin is loaded and active, so we won’t check for that (see this nice <a href="http://queryloop.com/how-to-detect-if-a-wordpress-plugin-is-active/" rel="nofollow ugc">write-up</a> on QueryLoop on some ways to do it, though).
<pre><code>if (is_admin()) {

 // The path to the configuation is rather long, so let's
 // make us a shorthand.
 class_alias('\GlobalMetaBoxOrder\Config', 'MetaBoxConfig');

 // Add MetaBoxConfig below this line
 ...
}
</code></pre>
Now we are ready to add some of the configuration settings below to adjust the plugin’s default behaviour. You might also want to have a look at the example configuration near the end of this document.
Please keep in mind that you need to be logged in as any user but your blueprint user to see a setting applied. Again, the <a href="https://wordpress.org/plugins/user-switching/" rel="ugc">User Switching</a> plugin might come in handy.
Screens To Operate On
By default, the plugin operates on the post, page, and custom post type editing screens, and the dashboard.
You can change this as follows:
<pre><code>// Operate on post and page screens only, leave the dashboard alone.
// This will still include custom post types.
MetaBoxConfig::$filter = array('post', 'page');

// Exclude custom post types
MetaBoxConfig::$include_cpts = false; 

// Allow custom post types...
MetaBoxConfig::$include_cpts = true; 

// ...but not all of them
MetaBoxConfig::$exclude = array('acme_product');
</code></pre>
MetaBoxConfig in the example above is assumed to be an alias to \GlobalMetaBoxOrder\Config as shown in the preparation section above.
Changing the Blueprint User
Register a function that returns a user id, like so:
<pre><code>MetaBoxConfig::$getBlueprintUserId = function () { return 1; };
</code></pre>
Or, more involved:
<pre><code>MetaBoxConfig::$getBlueprintUserId = function () { 

 $user = get_user_by('slug', 'jane');
 return $user ? $user->ID : false; 
};
</code></pre>
MetaBoxConfig in the example above is assumed to be an alias to \GlobalMetaBoxOrder\Config as shown in the preparation section above.
Locking Views
By default, all users will be able to interact with the screen options box, and to move around the meta boxes themselves. There is a rationale behind it, but to cut things short, this is how you might want to change it:
<pre><code>// No screen options 
MetaBoxConfig::$remove_screen_options = true;

// Meta boxes can't be moved anymore 
MetaBoxConfig::$lock_meta_box_order = true; 
</code></pre>
MetaBoxConfig in the example above is assumed to be an alias to \GlobalMetaBoxOrder\Config as shown in the preparation section above.
Example Configuration
<pre><code>if (is_admin()) {

 // Make sure plugin is active
 if (class_exists('\GlobalMetaBoxOrder\Config')) {

 // Make a long name short. 
 class_alias('\GlobalMetaBoxOrder\Config', 'MetaBoxConfig');

 // Settings

 MetaBoxConfig::$filter = array('post', 'page', 'dashboard'); // default
 MetaBoxConfig::$include_cpts = true; // default
 MetaBoxConfig::$getBlueprintUserId = function () { return 1; };
 MetaBoxConfig::$exclude = array('acme_product');
 MetaBoxConfig::$remove_screen_options = true;
 MetaBoxConfig::$lock_meta_box_order = true; 
 }
}
</code></pre>
<h4>On Moving the WYSIWYG Editor</h4>
The position of WordPress’ WYSIWYG editor is fixed, and can’t be changed out of the box (mostly because it lacks a box around it). There are reasons for this, but if you want to have a positionable editor anyway, you might want to have a look at our very own <a href="https://github.com/pontycode/wordpress-movable-editor" rel="nofollow ugc">Movable Editor</a> plugin.
If, on the other hand, if you want to place one specific box above the editor, you might want to check out <a href="http://wordpress.stackexchange.com/a/88103" rel="nofollow ugc">this answer</a> on stackexchange.

Global Meta Box Order

Got it working in no time. Locked meta boxes and hid the screen options button. Hopefully I've just made the client's life 10x easier by arranging meta boxes in a logical order.
Why WordPress doesn't let you set the default layout out of the box is beyond me.



Excellent

Harmonize meta box positions for all backend users.

My Custom Widgets vs Global Meta Box Order