netbiel

The plugin has its own admin options page (settings page) where you can:
<ul>
<li>add user-friendly horizontal menu and dashboard metaboxes</li>
<li>completely remove blogging plarform widgets</li>
<li>change logo and link of the login page</li>
<li>customize admin bar menu</li>
<li>add custom content to the admin footer</li>
<li>hide notices (core update notice, plugin update notice and theme update notice)</li>
<li>hide screen options and help tag</li>
<li>change basic site settings e.g. hide site generator and feed links</li>
</ul>
It gives your clients a better experience of their new website.
Support for translation!
<ul>
<li>Polish translation</li>
<li>Dutch translation by Jos Wolbers</li>
</ul>
Plugin is ready for WordPress 3.6

CMS admin area

Useful and easy way to customize your WordPress admin area and the login page.

Phan Chuong

There is a dozen WordPress metaboxes out there, but this one is the unique one, the simplest one, and the most flexible one. Imagine you have a post that need to display multiple of item, and each item have a bundle of fields, you’d need IP Metaboxes’s help.
<h4>**WHAT’S NEW on 2.1 ?**</h4>
<ol>
<li>New API function to get single metabox value.</li>
<li>Add new ability to upload feature to allow you to upload MP3 audio files together with pictures.</li>
<li>Fix compatibility with WordPress 3.8.1.</li>
</ol>
<h4>**HIGHLIGHTED FEATURES**</h4>
<ol>
<li>It has ability to add multiple items for each metabox. </li>
<li>You can change the order of each items according to your expectation.</li>
<li>All the settings and customizations are placed under only one page, and it’s super easy to add more and more metaboxes for any post, even custom post types. </li>
</ol>
<h4>How to use</h4>
<ol>
<li>After install, there is a custom menu that created at the bottom of admin page, it’s named “IP Metaboxes”. By opening that page, you’re accessing to the main setting page of IP Metaboxes.</li>
<li>Let’s start to define a metabox:
<ul>
<li>Metabox Name: The name of metabox. There is no limitation of this name, you can define any easy-to-remember name for this. Changing this name would take no impact to your data.</li>
<li>Post Types: The post type that you would like to apply metabox to. You can select multiple types, and of course you can select custom post type.</li>
<li>Context: The location of metabox (left/right). Usually, normal and advanced would make your metabox stay on the left side (content section), and side would make it stay on the right side (publish section).</li>
<li>Priority: The place of metabox (top, bottom). Usually, high would make your metabox go up and higher than the others.</li>
<li>Post IDs: The special post IDs that you want to strict your metabox to display. You can enter multiple ID, separate by comma, e.g.: <code>102, 582</code>.</li>
</ul>
</li>
<li>Now, let’s add some fields for your metabox:
<ul>
<li>Name: The name of field. You can enter any name you want here, but please remember that, CHANGING THE FIELD NAME WOULD MAKE YOUR OLD DATA LOST.</li>
<li>Type: The type of field. </li>
<li>Options: Each field type have some sort of options:
<ul>
<li>Text, editor: no special options.</li>
<li>Multiselect, select, checkbox, radio: each item is separated by comma, e.g.: <code>item 1, item 2, item 3</code>.</li>
<li>Upload: width and height are separated by comma, e.g.: <code>100, 200</code>.</li>
<li>Date: your expected format, default one is <code>dd/MM/yyyy</code>.</li>
</ul>
</li>
<li>Description: The field’s description. Just use it to describe a little information about the field to end-user.</li>
<li>ID: The field’s ID. This ID is auto-generated based on your field name, you might need it in order to get a specific data as you want.</li>
</ul>
</li>
<li>Finally, just save them all and you will see a sample code that show how to display the metaboxes you just added. Copy them to the template and well done.</li>
</ol>
<h4>Public API</h4>
Currently IP Metaboxes only public 3 methods:
<ol>
<li><code>ipmb_get_metabox_values($metabox_id, $post_id)</code>
<ul>
<li><code>$metabox_id</code>: you can found it under metaboxes table of IP Metaboxes setting page</li>
<li><code>$post_id</code>: by default it would be the current post. But in order to get metaboxes of some special post you can pass it’s ID here.</li>
</ul>
</li>
<li><code>ipmb_get_metabox_value($metabox_id, $post_id, $field_name)</code>
<ul>
<li><code>$metabox_id</code>: you can found it under metaboxes table of IP Metaboxes setting page.</li>
<li><code>$post_id</code>: by default it would be the current post. But in order to get metaboxes of some special post you can pass it’s ID here.</li>
<li><code>$field_name</code>: the specific field that you want to get value, can be found at metabox details table of IP Metaboxes setting page</li>
</ul>
</li>
<li><code>ipmb_get_metabox_images($url, $size)</code>
<ul>
<li><code>$url</code>: the url of image, you should have this from method <code>ipmb_get_metabox_values</code> with upload field</li>
<li><code>$size</code> : the thumbnail size, by default it’s ‘thumbnail’ but you can change to any size you want, even the array of width and height as you usually defined.</li>
</ul>
</li>
</ol>
<h4>Known Issues</h4>
<ol>
<li>When add an ‘editor’ with context ‘side’, it would automatically change to normal textarea, this happens because there is not much space for an editor when it’s displaying at sidebar.</li>
<li>When you try to move items around or add new item, and if the item contain editor(s), it will be disabled and you cannot edit it’s content. This is one of limitation of WordPress editor. So just save your post and you will be able to enter text.</li>
<li>There is no link for ‘Expand All’ and ‘Collapse All’ if the context is ‘side’ due to the title space is too small.</li>
</ol>
Please <a href="mailto:pltchuong@gmail.com" rel="nofollow ugc">let me know</a> if there is any bugs happens, or any feature that you’d like to have, I will do my best to complete it if I can 🙂

IP Metaboxes

A new metaboxes plugin, the unique one, the simplest one, and the most flexible one.

CMS admin area vs IP Metaboxes