Alex Prokopenko / JustCoded

Just Custom Fields adds ability to extend your Posts, Pages (and other custom post types) and Taxonomies with additional fields. After installation, you will see a simple settings page, which is self-explanatory to use. 
We use the standard WordPress PostMeta API and TaxonomyMeta API to save fields data, so you can use standard WordPress functions in your themes/plugins to get data.
IMPORTANT We do not recommend update plugins on your existing sites from version 2.* to version 3.0+. 
JCF v3.0+ is not compatible with versions 2.*, so some field settings can be lost (and as a result – wrong values on post edit pages).
Plugin supports such field types:
<ul>
<li>Input text</li>
<li>Select Box</li>
<li>Multiple Select Box</li>
<li>Checkbox (single and multiple)</li>
<li>Textarea (you can use WordPress editor too)</li>
<li>Datepicker</li>
<li>Simple Media (files and images upload)</li>
<li>Table</li>
<li>Fields Collection (repeatable fields groups)</li>
<li>Related Content (to set a relation to another Post/Page or Custom Post Type)</li>
</ul>
You can read full documentation on our site: http://justcustomfields.com.
For quick demo you can watch our presentation video: 
https://www.youtube.com/watch?v=7KJeH2d_v48
Starting from v2.0 we have different options to save plugin configuration:
<ul>
<li>Ability to set Fields Settings global if you have MultiSite. So you can set them once, without copying all settings to every new site.</li>
<li>Ability to save Fields Settings to a file system (inside theme or wp-content folder). We expect this option will be popular among the developers. It will be much easier to move your fields’ settings between site versions (dev/production).</li>
</ul>
Starting from v2.2:
<ul>
<li>Simple Media field is now a single file only (before it was multiple). It uses new media upload box from WordPress and saves post thumbnail ID (before it was just a file url). So now you can use the get_the_post_thumbnail() function to work with attachments.</li>
<li>All fields now have “Shortcodes” and hints how to use them inside the templates for non-professional developers.</li>
</ul>
For easy migrations between different sites, we have Export/Import options.
FEEL FREE TO CONTACT ME IF YOU FIND ANY BUGS/ISSUES!
ISSUES TRACKER 
Plugin code is open source and placed in the GitHub public repository. I listed known bugs and future features there. You can post new bugs or feature requests for me there. 
https://github.com/aprokopenko/justcustomfields/issues

Just Custom Fields

Turn WordPress into more powerful CMS by adding advanced and easy to use custom fields

Mohammad Jangda

Joey Kudish

cvernon

stresslimit

An easy way to add custom fields to your object types (post, pages, custom post types, users) & to generate option pages.
The goal of this plugin is to help you rapidly build familiar, intuitive interfaces for your users in a very WordPress-native way.
The custom field panel is nice, but not quite the easiest thing for users to work with. Adding your own metaboxes and fields involves a lot of time and repetitive code that could be better used elsewhere.
This plugin handles all that heavy-lifting for you behind-the-scenes, so that you can focus on more on building out and connecting your data rather than all the minor details. This single piece of code <code>x_add_metadata_field( 'my-field-name', 'post' );</code> generates a metabox with a text field inside it, with the necessary hooks to save the entered values.
The API is similar to that used for registering custom post types and taxonomies so it should be familiar territory.
NOTE: The plugin now requires WordPress 3.3+ (chiefly for the wysiwyg & datepicker fields)
Like what you see? Want more field types and features added? <a href="mailto:tech@stresslimitdesign.com" rel="nofollow ugc">Get in touch</a> or <a href="https://github.com/jkudish/custom-metadata" rel="nofollow ugc">contribute on github</a>
<blockquote>
See “Other Notes” section for usage information
</blockquote>
<h3>Usage</h3>
<h4>Object Types</h4>
The main idea behind this plugin is to have a single API to work with regardless of the object type. Currently, Custom Metadata Manager works with <code>user</code>, <code>comment</code> and any built-in or custom post types, e.g. <code>post</code>, <code>page</code>, etc.
<h4>Registering your fields</h4>
For the sake of performance (and to avoid potential race conditions), always register your custom fields in the <code>admin_menu</code> hook. This way your front-end doesn’t get bogged down with unnecessary processing and you can be sure that your fields will be registered safely. Here’s a code sample:
<pre><code>add_action( 'admin_menu', 'my_theme_init_custom_fields' );

function my_theme_init_custom_fields() {
 if( function_exists( 'x_add_metadata_field' ) && function_exists( 'x_add_metadata_group' ) ) {
 x_add_metadata_field( 'my_field', array( 'user', 'post' ) );
 }
}
</code></pre>
<h4>Getting the data</h4>
You can get the data as you normally would using the <code>get_metadata</code> function. Custom Metadata manager stores all data using the WordPress metadata APIs using the slug name you provide. That way, even if you decide to deactivate this wonderful plugin, your data is safe and accessible. For options, you can use <code>get_option</code>.
Example:
<pre><code>$value = get_metadata( 'post', get_the_ID(), 'featured', true ); // Returns post metadata value for the field 'featured'
</code></pre>
<h4>Adding Metadata Groups</h4>
A group is essentially a metabox that groups together multiple fields. Register the group before any fields
<pre><code>x_add_metadata_group( $slug, $object_types, $args );
</code></pre>
Parameters
<ul>
<li><code>$slug</code> (string) The key under which the metadata will be stored.</li>
<li><code>$object_types</code> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.</li>
</ul>
Options and Overrides
<pre><code>$args = array(
 'label' => $group_slug, // Label for the group
 'context' => 'normal', // (post only)
 'priority' => 'default', // (post only)
 'autosave' => false, // (post only) Should the group be saved in autosave? NOT IMPLEMENTED YET!
 'exclude' => '', // see below for details
 'include' => '', // see below for details
);
</code></pre>
<h4>Adding Metadata Fields</h4>
<pre><code>x_add_metadata_field( $slug, $object_types, $args );
</code></pre>
Parameters
<ul>
<li><code>$slug</code> (string) The key under which the metadata will be stored. For post_types, prefix the slug with an underscore (e.g. <code>_hidden</code>) to hide it from the the Custom Fields box.</li>
<li><code>$object_types</code> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.</li>
</ul>
Options and Overrides
<pre><code>$args = array(
 'group' => '', // The slug of group the field should be added to. This needs to be registered with x_add_metadata_group first.
 'field_type' => 'text', // The type of field; 'text', 'textarea', 'password', 'checkbox', 'radio', 'select', 'upload', 'wysiwyg', 'datepicker', 'taxonomy_select', 'taxonomy_radio'
 'label' => '', // Label for the field
 'description' => '', // Description of the field, displayed below the input
 'values' => array(), // Values for select and radio buttons. Associative array
 'display_callback' => '', // Callback to custom render the field
 'sanitize_callback' => '', // Callback to sanitize data before it's saved
 'display_column' => false, // Add the field to the columns when viewing all posts
 'display_column_callback' => '', // Callback to render output for the custom column
 'required_cap' => '', // The cap required to view and edit the field
 'exclude' => '', // see below for details
 'include' => '', // see below for details
 'multiple' => false, // true or false, can the field be duplicated with a click of a button?
 'readonly' => false, // makes the field be readonly (works with text, textarea, password, upload and datepicker fields)
);
</code></pre>
<h4>Include / Exclude</h4>
You can exclude fields and groups from specific object. For example, with the following, field-1 will show up for all posts except post #123:
<pre><code>$args = array(
 'exclude' => 123
);
x_add_metadata_field( 'field-1', 'post', $args );
</code></pre>
Alternatively, you can limit (“include”) fields and groups to specific objects. The following will ”only” show group-1 to post #456:
<pre><code>$args = array(
 'include' => 123
);
x_add_metadata_group( 'group-1', 'post', $args );
</code></pre>
You can pass in an array of IDs:
<pre><code>$args = array(
 'include' => array( 123, 456, 789 );
);

With multiple object types, you can pass in an associative array:
</code></pre>
$args = array( 
 ‘exclude’ => array( 
 ‘post’ => 123, 
 ‘user’ => array( 123, 456, 789 ) 
 ) 
);
<h4>Examples</h4>
For examples, please see the <a href="https://github.com/jkudish/custom-metadata/blob/master/custom_metadata_examples.php" rel="nofollow ugc">custom_metadata_examples.php</a> file included with the plugin. Add a constant to your wp-config.php called <code>CUSTOM_METADATA_MANAGER_DEBUG</code> with a value of <code>true</code> to see it in action:
<pre><code>define( 'CUSTOM_METADATA_MANAGER_DEBUG', true );
</code></pre>
<h4>TODOs</h4>
Stuff we have planned for the future:
<ul>
<li>Ability to clone (multiple) groups of fields</li>
<li>Ability Pass in attributes for built-in fields (e.g. class, data-*, etc.)</li>
<li>Additional field types (multi-select, multi-checkbox)</li>
<li>Limit or exclude groups and fields using a custom callback</li>
<li>Autosave support for fields on post types</li>
<li>Client- and server-side validation support</li>
<li>Add groups and fields to Quick Edit</li>
</ul>

Custom Metadata Manager

An easy way to add custom fields to your object types (post, pages, custom post types, users)

Just Custom Fields vs Custom Metadata Manager