Kite

<p>Due to security/privacy concerns, JSON REST API (WP API) only allows post meta data (custom field value) for authenticated users.<br />
This plugin is an easy way to make post meta available when unauthenticated.</p>
<p>After activate the plugin, go to WP API Customizer option page.<br />
Click the plus icon to add rows.<br />
Set JSON attributes and custom field names in your posts that you want to use when unauthenticated.<br />
The JSON REST API will provide the data as “post_meta” like the following:</p>
<pre><code>"post_meta":{"your_attribute_a":"Custom Field A value","your_attribute_b":"Custom Field B value"}
</code></pre>


WP API Customizer

Make post meta data (custom field values) available for JSON REST API (WP API) when unauthenticated.

Matthew Boynes

Union Street Media

<h4>UPGRADE NOTICE</h4>
<p>SuperCPT now uses Font Awesome instead of Glyphicons. Some icon names will carry over, but not all. If this is a considerable inconvenience for you for a project, simply do not update it. It’s not a security release, so updating isn’t necessary.</p>
<h4>Overview</h4>
<p>SuperCPT is an object wrapper for Custom Post Types, Custom Taxonomies, and Custom Post Meta “for coders, by coders.” Simply put, SuperCPT:</p>
<ul>
<li>DRYs up the Custom Post Type and Custom Taxonomy process (e.g. automatically adds the name to all the labels),</li>
<li>allows you to set default options for all your Custom Post Types and Taxonomies,</li>
<li>significantly simplifies the process of creating, saving, and displaying Custom Post Meta,</li>
<li>is sexy! Your custom fields are styled to look great and SuperCPT comes with 361 awesome icons courtesy of <a href="http://fontawesome.io/" rel="nofollow ugc">Font Awesome</a>.</li>
</ul>
<h4>Demo Video</h4>
<div class="embed-vimeo" style="text-align: center;"><iframe loading="lazy" src="https://player.vimeo.com/video/59368054" width="750" height="422" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div>
<h4>TextMate/Sublime Text 2 Bundle</h4>
<p>If you use TextMate, Sublime Text 2, or another editor which supports TextMate bundles, check out <a href="https://github.com/mboynes/super-cpt-bundle" rel="nofollow ugc">this set of snippets</a> to turbo-charge your development.</p>
<h4>And more…</h4>
<p>See the <a href="https://wordpress.org/extend/plugins/super-cpt/other_notes/" rel="ugc">Other Notes tab</a> for instructions and demo code. Find more demos and a full reference <a href="https://github.com/mboynes/super-cpt/wiki" rel="nofollow ugc">at GitHub</a>.</p>
<p>Since you’re a hard-core coder, <a href="https://github.com/mboynes/super-cpt" rel="nofollow ugc">check this out on GitHub</a> if you want to contribute!</p>
<h3>Instructions</h3>
<p>Depending on when and where you’re declaring your Custom Post Types and Taxonomies, you have different options for which action to hook onto. <code>after_setup_theme</code> is the safest bet, but if you’re referencing this in another plugin, <code>plugins_loaded</code> is a good choice. To avoid a fatal error if something goes awry, you should check to see if the class <code>Super_Custom_Post_Type</code> exists before referencing it. Don’t worry about keeping up, reference code is below.</p>
<h4>Custom Post Types</h4>
<p>To define a new Custom Post Type, instantiate the <code>Super_Custom_Post_Type</code> class with a string for the post type. For example,</p>
<pre><code>$movies = new Super_Custom_Post_Type( 'movie' );
</code></pre>
<p>It works very much like <a href="https://codex.wordpress.org/Function_Reference/register_post_type" rel="nofollow ugc"><code>register_post_type</code></a>. The first thing you gained by using this is that the labels all got setup with either ‘Movie’ or ‘Movies’. If our post type were ‘indie-film’, the labels would have “Indie Film” and “Indie Films” as appropriate. Of course, you do have the ability to set the plural word in cases such as goose/geese. You also gained the ability to define your own custom post type defaults through a filter. Lastly, you gained access to <code>Super_Custom_Post_Type</code>‘s parent class, <code>Super_Custom_Post_Meta</code>, for fast, clean, intuitive custom post meta, which we’ll go into shortly.</p>
<p>Lastly, if you’ve built a lot of custom post types, you’re probably sick and tired of the pushpin icon. SuperCPT comes with 350 gorgeous icons courtesy of <a href="http://fontawesome.io/" rel="nofollow ugc">Font Awesome</a> that are extremely easy to implement. Here’s what it looks like:</p>
<pre><code>$movies->set_icon( 'film' );
</code></pre>
<h4>Custom Taxonomies</h4>
<p>To define a new Custom Taxonomy, much like with Custom Post Types, you instantiate <code>Super_Custom_Taxonomy</code> with a string for the term name. For example:</p>
<pre><code>$actors = new Super_Custom_Taxonomy( 'actor' );
</code></pre>
<p>Again, we got free labels for doing this, using either ‘Actor’ or ‘Actors’ as appropriate, without needing to specify the 16 labels individually.</p>
<h4>Custom Post Meta</h4>
<p>Custom Post Meta is where SuperCPT shines the brightest, because this process is typically the most time-consuming. <code>Super_Custom_Post_Meta</code> is a free-standing class that can be added to any post type, even built-in post types (posts and pages). This class has a method <code>add_meta_box</code> which does the bulk of the work, and somewhat mimics the WordPress function. Here’s an example:</p>
<pre><code>$movies->add_meta_box( array(
    'id' => 'features',
    'fields' => array(
        'tagline' => array( 'type' => 'text' )
    )
) );
</code></pre>
<p>The method <code>add_meta_box</code> takes an array of parameters (unlike the core function which takes normal ordered arguments). <code>id</code> is the only required attribute, and that becomes the ID of the meta box as well as the title (this will get converted into “words” for the title, e.g. <code>"movie_details"</code> would become “Movie Details”). <code>fields</code> is an array of all the fields in the meta box. It’s an associative array, where the keys in the array are the field names and the values are another associative array of attributes for the field. The keys closely reflect the HTML attributes in the resulting field, and any key not known by the plugin will in fact become an HTML attribute (e.g. passing <code>'data-src' => 'foo'</code> would become the HTML attribute <code>data-src="foo"</code> in the field). See the reference for the full gamut of options, both for the <code>add_meta_box</code> argument array and the fields array.</p>
<p>Long story short, using this class means you don’t have to do any additional work to store data, retrieve data, style the boxes, and so on.</p>
<h4>Helper Functions</h4>
<p>SuperCPT has a couple of helper functions for displaying your post meta. <code>get_scpt_formatted_meta</code> and <code>the_scpt_formatted_meta</code></p>
<h3>Demo Code</h3>
<p>Here is the full demo code:</p>
<pre><code>function scpt_demo() {
    if ( ! class_exists( 'Super_Custom_Post_Type' ) )
        return;

    $demo_posts = new Super_Custom_Post_Type( 'demo-post' );

    # Test Icon. Should be a square grid.
    $demo_posts->set_icon( 'th-large' );

    # Taxonomy test, should be like tags
    $tax_tags = new Super_Custom_Taxonomy( 'tax-tag' );

    # Taxonomy test, should be like categories
    $tax_cats = new Super_Custom_Taxonomy( 'tax-cat', 'Tax Cat', 'Tax Cats', 'category' );

    # Connect both of the above taxonomies with the post type
    connect_types_and_taxes( $demo_posts, array( $tax_tags, $tax_cats ) );

    # Add a meta box with every field type
    $demo_posts->add_meta_box( array(
        'id' => 'demo-fields',
        'context' => 'normal',
        'fields' => array(
            'textbox-demo' => array(),
            'textarea-demo' => array( 'type' => 'textarea' ),
            'wysiwyg-demo' => array( 'type' => 'wysiwyg' ),
            'boolean-demo' => array( 'type' => 'boolean' ),
            'checkboxes-demo' => array( 'type' => 'checkbox', 'options' => array( 'one', 'two', 'three' ) ),
            'radio-buttons-demo' => array( 'type' => 'radio', 'options' => array( 'one', 'two', 'three' ) ),
            'select-demo' => array( 'type' => 'select', 'options' => array( 1 => 'one', 2 => 'two', 3 => 'three' ) ),
            'multi-select-demo' => array( 'type' => 'select', 'options' => array( 'one', 'two', 'three' ), 'multiple' => 'multiple' ),
            'date-demo' => array( 'type' => 'date' ),
            'label-override-demo' => array( 'label' => 'Label Demo' )
        )
    ) );

    # Add another CPT to test one-to-one (it could just as easily be one-to-many or many-to-many)
    $linked_posts = new Super_Custom_Post_Type( 'linked-post', 'Other Post', 'Other Posts' );
    $linked_posts->add_meta_box( array(
        'id' => 'one-to-one',
        'title' => 'Testing One-to-One relationship',
        'context' => 'side',
        'fields' => array(
            'demo-posts' => array( 'type' => 'select', 'data' => 'demo-post' ),
            'side-wysiwyg' => array( 'type' => 'wysiwyg' )
        )
    ) );
    $linked_posts->set_icon( 'cogs' );

}
add_action( 'after_setup_theme', 'scpt_demo' );<h3>To-Do</h3>
</code></pre>
<p>1. Add better support for multiple fields for one meta key<br />
2. Add easy RSS feeds, e.g. in fields array, a parameter might be <code>'rss' => 'PubDate'</code> to prefer that field’s data over the post’s publication date.</p>


SuperCPT

Insanely easy and attractive custom post types, custom post meta, and custom taxonomies

WP API Customizer vs SuperCPT