Wordpress The Complete Guide To Custom Post Types

Advertisement

WordPress has been gaining a foothold in the general content management system (CMS) game for a few years now, but the real breakthrough was the custom post type mechanism which allows for the creation of a wide variety of content. Let’s take a look at how this came to be and all the options that this great functionality offers.

Some of the custom post types you can create in WordPress.1
Some of the custom post types you can create in WordPress.

What It Used To Be Like

In practice, custom post types have been around for a long time, more specifically since February 17, 2005, when WordPress 1.5 added support for static pages, creating the post_type database field.

The wp_insert_post() function has been around since WordPress 1.0, so when the post_type field was implemented in 1.5, you could simply set the post_type value when inserting a post. Of course, creating and managing custom post types required much more than that, but the amount of coding needed became less and less as WordPress functions became more and more flexible.

By version 2.8, the register_post_type() function and some other helpful things were added to the nightly builds, and when 2.9 came out, the functions became available to everyone. At this point, extensive coding and hacks were not needed to make WordPress a full blown CMS; you could use plenty of great built-in functions to make WordPress do your bidding.

What WordPress Can Do For You Now

A custom post type is nothing more than a regular post with a different post_type value in the database. The post type of regular posts is post, pages use page, attachments use attachment and so on. You can now create your own to indicate the type of content created. You could create custom post types for books, movies, reviews, products and so on.

If created correctly, you can achieve the following with a few lines of code:

  • The custom post type will show up in the back end as a separate menu item with its own post list and “add new” page
  • Navigating to http://mysite.com/customposttype/ will take you to the archive page for the post type. This is akin to visiting the front page for latest posts from the “post” post type.
  • Categories and tags can be made available to the custom post type, or you can create custom taxonomies.

Apart from these, you can modify countless options, such as where the custom post type should be placed in the menu, should it be searchable, which user level can access it, should it be hierarchical, custom rewrite rules, etc.

Different types of content have different data requirements. For regular posts, you’ll want to specify the author, category, date and so on. For a “book” custom post type, ideally you’d like to have the option to specify the book’s author, the page count, genre, publisher and other book-specific data. Using custom meta boxes, this is easily achieved and managed as well.

Custom meta boxes enable you to add additional boxes to the edit screen of a post. They usually use custom fields, so you could just use custom fields as well, but by separating out some custom fields as meta boxes, you can create a much smoother and usable admin.

Working With Custom Post Types

To effectively create and use custom post types, you’ll need to be familiar with the following:

  • Creating custom post types,
  • Creating custom taxonomies,
  • Creating custom meta boxes.

Creating Custom Post Types

First on our agenda is creating the post type itself. Ideally you should create a plugin2 when working with custom post types, but if you don’t know how, or just need a quick test, you can use the functions.php file in your theme.

function my_custom_post_product() {
  $args = array();
  register_post_type( 'product', $args ); 
}
add_action( 'init', 'my_custom_post_product' );

In its simplest form, it will create a post type which has almost no customization. It won’t be public, it won’t show up in the admin, interaction messages will be the same as posts (“post saved,” “post updated,” etc.) and so on. To tailor our new post type to our needs, I’ll go through some of the more frequently-used options and add them to the previously empty $args array.

function my_custom_post_product() {
  $labels = array(
    'name'               => _x( 'Products', 'post type general name' ),
    'singular_name'      => _x( 'Product', 'post type singular name' ),
    'add_new'            => _x( 'Add New', 'book' ),
    'add_new_item'       => __( 'Add New Product' ),
    'edit_item'          => __( 'Edit Product' ),
    'new_item'           => __( 'New Product' ),
    'all_items'          => __( 'All Products' ),
    'view_item'          => __( 'View Product' ),
    'search_items'       => __( 'Search Products' ),
    'not_found'          => __( 'No products found' ),
    'not_found_in_trash' => __( 'No products found in the Trash' ), 
    'parent_item_colon'  => '',
    'menu_name'          => 'Products'
  );
  $args = array(
    'labels'        => $labels,
    'description'   => 'Holds our products and product specific data',
    'public'        => true,
    'menu_position' => 5,
    'supports'      => array( 'title', 'editor', 'thumbnail', 'excerpt', 'comments' ),
    'has_archive'   => true,
  );
  register_post_type( 'product', $args ); 
}
add_action( 'init', 'my_custom_post_product' );
  • labels
    The labels option should be an array defining the different labels that a custom post type can have. I have separated this out above just to make the arguments for registering a post type clearer.
  • description
    A short explanation of our custom post type; what it does and why we’re using it.
  • public
    This option controls a bunch of things in one go. Setting this to true will set a bunch of other options (all to do with visibility) to true. For example, it is possible to have the custom post type visible but not queryable. More on this later.
  • menu_position
    Defines the position of the custom post type menu in the back end. Setting it to “5” places it below the “posts” menu; the higher you set it, the lower the menu will be placed.
  • supports
    This option sets up the default WordPress controls that are available in the edit screen for the custom post type. By default, only the title field and editor are shown. If you want to add support for comments, revisions, post formats and such you will need to specify them here. For a full list take a look at the arguments section3 in the Codex.
  • has_archive
    If set to true, rewrite rules will be created for you, enabling a post type archive at http://mysite.com/posttype/ (by default)

A custom post type in the menu.
A custom post type in the menu.

After setting this up, you should see the menu entry for the custom post type. You should be able to add posts, view the post list in the admin and also visit the published posts on the website.

As I mentioned there are a lot of things you can modify when creating a post type. I suggest looking at the arguments list in the Codex for a full description of each option and the possible values.

Custom Interaction Messages

WordPress generates a number of messages triggered by user actions. Updating, publishing, searching, etc., in the back end all lead to messages which — by default — are tailored to regular posts. You can change the text of these messages easily by using the post_updated_messages hook.

function my_updated_messages( $messages ) {
  global $post, $post_ID;
  $messages['product'] = array(
    0 => '', 
    1 => sprintf( __('Product updated. <a href="%s">View product</a>'), esc_url( get_permalink($post_ID) ) ),
    2 => __('Custom field updated.'),
    3 => __('Custom field deleted.'),
    4 => __('Product updated.'),
    5 => isset($_GET['revision']) ? sprintf( __('Product restored to revision from %s'), wp_post_revision_title( (int) $_GET['revision'], false ) ) : false,
    6 => sprintf( __('Product published. <a href="%s">View product</a>'), esc_url( get_permalink($post_ID) ) ),
    7 => __('Product saved.'),
    8 => sprintf( __('Product submitted. <a target="_blank" href="%s">Preview product</a>'), esc_url( add_query_arg( 'preview', 'true', get_permalink($post_ID) ) ) ),
    9 => sprintf( __('Product scheduled for: <strong>%1$s</strong>. <a target="_blank" href="%2$s">Preview product</a>'), date_i18n( __( 'M j, Y @ G:i' ), strtotime( $post->post_date ) ), esc_url( get_permalink($post_ID) ) ),
    10 => sprintf( __('Product draft updated. <a target="_blank" href="%s">Preview product</a>'), esc_url( add_query_arg( 'preview', 'true', get_permalink($post_ID) ) ) ),
  );
  return $messages;
}
add_filter( 'post_updated_messages', 'my_updated_messages' );

A custom message after saving a product.4
A custom message after saving a product.

As you can see, this is not the most user-friendly method of managing messages. An associative array would be far better; we could see what each message is for without having to read the actual message.

Notice that you can change the messages for all custom post types using this single function. The $messages array holds the messages for all post types, so you can modify them all here. I personally create a function for each post type just so I can group the post type creation and the custom messages together easily.

Contextual Help

A feature I rarely see implemented is the customized contextual help. As a user, I’ve never actually used this feature myself, but I’m sure that many people do; in any case, it’s nice to provide some hand-holding for less experienced users.

The contextual help feature is a descending tab which can be seen in the top right of pages where available. Let’s take a look at how the contents can be changed.

function my_contextual_help( $contextual_help, $screen_id, $screen ) { 
  if ( 'product' == $screen->id ) {

    $contextual_help = '<h2>Products</h2>
    <p>Products show the details of the items that we sell on the website. You can see a list of them on this page in reverse chronological order - the latest one we added is first.</p> 
    <p>You can view/edit the details of each product by clicking on its name, or you can perform bulk actions using the dropdown menu and selecting multiple items.</p>';

  } elseif ( 'edit-product' == $screen->id ) {

    $contextual_help = '<h2>Editing products</h2>
    <p>This page allows you to view/modify product details. Please make sure to fill out the available boxes with the appropriate details (product image, price, brand) and <strong>not</strong> add these details to the product description.</p>';

  }
  return $contextual_help;
}
add_action( 'contextual_help', 'my_contextual_help', 10, 3 );

This is also a bit difficult because you have to know the ID of the screen you are on. If you print out the contents of the $screen variable, you should be able to determine the ID easily. This is also a function you can use to modify the contextual help of all custom post types at once, but I personally recommend grouping this together with the previous two blocks and only using it for one custom post type at a time.

Overview

To quickly recap, we used three functions to create a “complete” custom post type. We used register_post_type() to create the post type itself and two hooks — contextual_help and post_updated_messages — to create helpful guidance and relevant messages respectively.

Custom Taxonomies

Your regular blog posts use categories and tags to create an organization structure. However, the same organization doesn’t necessarily make sense for custom post types. Your blog posts could be about your “Life,” your “Thoughts” or your “Dreams.” These are obviously not appropriate for products.

This is the problem that drove developers to create custom taxonomies. You can create a separate taxonomy named “Product Categories” to house categories you only use for products. Kevin Leary wrote a great article about custom taxonomies in WordPress5 which I highly recommend, so I will only go into minor detail here.

function my_taxonomies_product() {
  $args = array();
  register_taxonomy( 'product_category', 'product' $args );
}

add_action( 'init', 'my_taxonomies_product', 0 );

Similarly to custom post types, you can create a taxonomy very easily, but you need to work at it a bit to tailor it to your needs. Custom taxonomies behave a bit better out of the box as they are public by default, so the above is actually enough to tie this taxonomy to the product posts. Let’s look at a customized example.

function my_taxonomies_product() {
  $labels = array(
    'name'              => _x( 'Product Categories', 'taxonomy general name' ),
    'singular_name'     => _x( 'Product Category', 'taxonomy singular name' ),
    'search_items'      => __( 'Search Product Categories' ),
    'all_items'         => __( 'All Product Categories' ),
    'parent_item'       => __( 'Parent Product Category' ),
    'parent_item_colon' => __( 'Parent Product Category:' ),
    'edit_item'         => __( 'Edit Product Category' ), 
    'update_item'       => __( 'Update Product Category' ),
    'add_new_item'      => __( 'Add New Product Category' ),
    'new_item_name'     => __( 'New Product Category' ),
    'menu_name'         => __( 'Product Categories' ),
  );
  $args = array(
    'labels' => $labels,
    'hierarchical' => true,
  );
  register_taxonomy( 'product_category', 'product', $args );
}
add_action( 'init', 'my_taxonomies_product', 0 );

As you can see, not much has changed. We added some labels and set the hierarchical option to true. This enables “category style” taxonomies. When set to false (this is the default), your taxonomy will be like the default tags.

There are a few other power options available which you can read about in Leary’s article, or you can go to the Codex entry on register_taxonomy()6.

The Product Categories custom taxonomy.7
The Product Categories custom taxonomy.

Post Meta Boxes

Meta boxes are the draggable boxes you see in the WordPress edit screen for a post. There are numerous built-in meta boxes like the publishing controls, the taxonomies, the author box, etc., but you can create some for yourself.

Meta boxes tend to be used to manage custom field data in a much more user-friendly way than the built-in custom fields box does. Since you put the controls in place, you can add client-side error checking and many other fancy things.

Justin Tadlock wrote the all-encompassing custom meta box article8 here on Smashing Magazine, which is a great in-depth article on the subject. I recommend reading it for the full picture, but I’ll get you started here.

Creating a meta box requires three steps:

  • Define the box itself,
  • Define the content of the meta box,
  • Define how the data from the box is handled.

Defining the Meta Box

add_action( 'add_meta_boxes', 'product_price_box' );
function product_price_box() {
    add_meta_box( 
        'product_price_box',
        __( 'Product Price', 'myplugin_textdomain' ),
        'product_price_box_content',
        'product',
        'side',
        'high'
    );
}

The code above creates the meta box with the following parameters (in the order given):

  • The unique identifier for the meta box (it does not have to match the function name),
  • The title of the meta box (visible to users),
  • The function which will display the contents of the box,
  • The post type the meta box belongs to,
  • The placement of the meta box,
  • The priority of the meta box (determines “how high” it is placed).

Defining the Content of the Meta Box

function product_price_box_content( $post ) {
  wp_nonce_field( plugin_basename( __FILE__ ), 'product_price_box_content_nonce' );
  echo '<label for="product_price"></label>';
  echo '<input type="text" id="product_price" name="product_price" placeholder="enter a price" />';
}

This is a simple box which only contains the price, so we have created a label and an input to manage it. A nonce9 field is also present, which adds security to the data submission.

Handling Submitted Data

In most cases, you will want to save the data as a custom field, but you are by no means restricted to this method. You could use the input to make a third party API call, to generate an XML file or whatever you like. The most common use is saving custom post data, so let’s take a look at how that is done.

add_action( 'save_post', 'product_price_box_save' );
function product_price_box_save( $post_id ) {

  if ( defined( 'DOING_AUTOSAVE' ) && DOING_AUTOSAVE ) 
  return;

  if ( !wp_verify_nonce( $_POST['product_price_box_content_nonce'], plugin_basename( __FILE__ ) ) )
  return;

  if ( 'page' == $_POST['post_type'] ) {
    if ( !current_user_can( 'edit_page', $post_id ) )
    return;
  } else {
    if ( !current_user_can( 'edit_post', $post_id ) )
    return;
  }
  $product_price = $_POST['product_price'];
  update_post_meta( $post_id, 'product_price', $product_price );
}

The biggest part of this function is all about safety. First of all, if an autosave is being performed, nothing happens because the user hasn’t actually submitted the form. Then the nonce is checked, followed by permission checking. If these are all passed, we take our data and add it to the post using the update_post_meta() function.

An example of a meta box for an apartment post type.
An example of a meta box for an apartment post type.

Displaying Your Content

While there a plenty of nuances to all of the above, you should be familiar with the basics. All that is left is to actually use the data we now have and show things to the user. This involves showing posts — perhaps from various custom post types and taxonomies — and using our post metadata.

Displaying Posts

If you’ve created a post type with the has_archive parameter set to “true,” WordPress will list your posts on the post type’s archive page. If your post type is called “books,” you can simply go to http://mysite.com/books/ and you’ll see your post list.

This page uses archive-[post_type].php for the display if it exists (archive-books.php in our case). If it doesn’t exist, it will use archive.php and if that doesn’t exist it will use index.php.

Another way to display custom post type content is to use a custom query with the WP_Query class. To display posts from a certain post type and custom taxonomy, you could do something like this:

<?php
    $args = array(
      'post_type' => 'product',
      'tax_query' => array(
        array(
          'taxonomy' => 'product_category',
          'field' => 'slug',
          'terms' => 'boardgames'
        )
      )
    );
    $products = new WP_Query( $args );
    if( $products->have_posts() ) {
      while( $products->have_posts() ) {
        $products->the_post();
        ?>
          <h1><?php the_title() ?></h1>
          <div class='content'>
            <?php the_content() ?>
          </div>
        <?php
      }
    }
    else {
      echo 'Oh ohm no products!';
    }
  ?>

Displaying Metadata

Metadata can be retrieved easily using the get_post_meta() function. In our example above, we saved a post meta field named product_price. We can retrieve the value of this field for a given post using the following code:

<?php
  // If we are in a loop we can get the post ID easily
  $price = get_post_meta( get_the_ID(), 'product_price', true );

  // To get the price of a random product we will need to know the ID
  $price = get_post_meta( $product_id, 'product_price', true );
?>

Final Words

As you can see, creating a CMS is pretty easy due to the modular nature of WordPress controls and functions. The methods outlined here can be used extremely well to create customized admins for nearly anything you can think of.

Since defining the content of meta boxes is completely up to you, you have the power to create additional features for your controls, making you or your clients very happy.

You can take this one step further with custom admin pages and completely custom content, but that’s a story for another day.

Image source10 of picture on front page.

(cp)

Footnotes

  1. 1 http://www.smashingmagazine.com/wp-content/uploads/2012/10/customposttypes.jpg
  2. 2 'http://www.smashingmagazine.com/2011/09/30/how-to-create-a-wordpress-plugin/'
  3. 3 http://codex.wordpress.org/Function_Reference/register_post_type#Arguments
  4. 4 http://www.smashingmagazine.com/wp-content/uploads/2012/10/custommessage.png
  5. 5 'http://www.smashingmagazine.com/2012/01/04/create-custom-taxonomies-wordpress/'
  6. 6 'http://codex.wordpress.org/Function_Reference/register_taxonomy'
  7. 7 http://www.smashingmagazine.com/wp-content/uploads/2012/10/productcategories.jpg
  8. 8 'http://www.smashingmagazine.com/2011/10/04/create-custom-post-meta-boxes-wordpress/'
  9. 9 'http://codex.wordpress.org/WordPress_Nonces'
  10. 10 http://alittlecode.com/wordpress-custom-post-types-and-custom-taxonomies-a-roundup/

↑ Back to top Tweet itShare on Facebook

Hallo, my name is Daniel :) I build plugins, themes and apps - then proceed to write or talk about them. I'm the editor for the WordPress section here on Smashing Magazine and I contribute to various other online sites. When not coding or writing you'll find me playing board games or running with my dog. Drop me a line on Twitter or visit my personal website.

Advertisement
  1. 1

    Thanks for the article, great help.

    However, as is I was having issues editing custom post type posts. Any time you edit, the custom meta-content boxes are empty. Then on submission all values are cleared (assigned the empty values).

    We can clear this up by loading any existing values using get_post_meta().

    Add this to the last line of the ‘product_price_box_content’ function:
    … placeholder=”enter a price” value=”‘ . (get_post_meta($post->ID, ‘part_id’, true) ?:”) . ‘”/>';

    This way you’ll get any existing values loaded into the content meta-boxes on edit.

    (Sorry to write it that way but if I place the entire line of code it triggers the spam bot.)

    3
  2. 52

    Developers using this code will have an issue with custom meta boxes not saving content on submit or update. In fact, the content is being saved, but the custom meta box is not displaying the information that is saved to it. The issue there is that if a user goes in to the post and edits it without re-entering the custom meta content; the box will stay empty and save a null value over the previously entered content. This requires the user to re-enter the same content each time they edit the post.

    The solution is similar to what Tim wrote above me, but written out a little more to understand what’s going on easier (also Tim’s solution did not work for me.) First, in the “product_price_box_content” function, create a $meta_value variable that stores the meta data like so: $meta_values = get_post_meta($post->ID, ‘product_price’, true);

    Then after the label for the product price, write an if statement. If ($meta_values != ”) { echo the input with value=”‘ . $meta_values . ‘” (or whatever you’ve chosen to name your meta value variable) }

    else { echo the input with no value }

    This conditional asks “Is $meta_values a non-null value?” meaning has there been content saved to this meta box before? If yes, then echo the input box with the content that has been entered before as the default value of the box. This verifies that your content has been saved, and makes it unnecessary to re-enter the same content each time you edit your post.

    If the answer is no – meaning either this is the creation of the current post, or the post is being edited and a value was not entered for this meta box before, then echo the input with no default value.

    If anyone on the smashing magazine team is reading this I would highly recommend either adding this solution to the blog post or addressing the problem in some kind of way. I am using this to write some custom post types and know numerous people who have used this post before. Thank you for this fantastic article and I hope my solution can help in some way.

    Here is a pastebin of my solution http://pastebin.com/nu2EknxW

    6
    • 103

      Hey Bobby,

      Thanks for this answer. I was pulling my hair out wondering why the custom meta box was not saving my input. Again, many thanks and I really appreciate it.

      Zam

      2
    • 205

      Thank you thank you thank you Bobby! I have been going nuts over this and i’ve done a couple of other tutorials about custom meta boxes and have come across this problem. It seems simple for someone that is knowledgeable on it already but for people just learning it is a massive brick wall to run into. This is why having comments on web dev blogs is helpful

      0
    • 307

      I have received a few messages thanking me for this solution. I was more than happy to help. For the sake of keeping this result findable, I have uploaded my solution to Gist as well here:

      https://gist.github.com/BobbyAdamson/0063b35bcd070d8ea38f

      0
  3. 358

    Thanks for the tutorial. Do you know a godo way to get the urls to be like
    /%custom-caxonomy%/%post-name%/

    instead of

    post-type/%post-name%

    it sounds like a simple thing to do but notihing seems to work without conflicting with something else.

    0
  4. 409

    Aleksandar Misin

    April 11, 2014 12:37 pm

    Thank you very much!!
    I did searched almost the entire universe to find the answer. And answer was I did only need to add custom taxonomy :)

    Thanks very much!

    1
  5. 460

    Hi Daniel,

    Just like to say thanks for your article. I found it very useful indeed, and it has helped me gain a better understanding of how WordPress functions from the inside.

    Cheers

    Barry

    0
  6. 511

    Hello
    Thanks for this post, very very good
    I need show multiple post type in home page
    for example i create post type for team, product, price table and… so show all post in this post type (team, product, price table…) in home page
    Please help…
    Thanks

    2
  7. 562

    I have been having issues with the WP_QUERY not return the correct results. I found that it was a problem with the underscore in the taxonomy. So i changed this:

    register_taxonomy( ‘product_category’, ‘product’, $args );

    to this:

    register_taxonomy( ‘productcategory’, ‘product’, $args );

    and everything is now working nicely.

    Just thought i would share, just incase someone else has the same problem.

    Thanks

    0
  8. 613

    Does anyone know how to add a duplicate button to the custom post type?

    2
  9. 664

    Great article.

    I’ve just got back into WordPress after hand coding all the projects I’ve worked on for the last few years.

    This is exactly what I needed to figure out as I’ve got a client that need to separate there venues and supply location / contact / description / images ……

    My question now is – Is it possible to make a search framework that will tie into all these extra meta data?

    For example search for a venue by region / county / town / activities

    -1
  10. 715

    Hello,

    Please let me know if it’s posible to export the custom type with all the custom fileds that i will creat ?

    I need for example to create one type post with the name “travel listing” with more custom fields: name, price, transport, etc…

    Then i want to export into a .xml file the listing from “travel listing” type post?
    The format of the must be something like that:

    Listing type
    – name of the listing
    – Price
    – include price
    – ect….

    Please let me know uf that it’s posible?

    many regards

    0
  11. 766

    Awesome tutorial. Thank you very much.

    0
  12. 817

    hallo,
    nice article , really helped me make a post for affiliate products. Can I get the code to display the affiliate link in the meta boxes

    0
  13. 868

    hey,
    thank you very much for this nice tutorial. it helped me alot. i just found a little mistake: it must be “get_the_ID()” instead of “get_post_ID()” in the “Displaying Metadata” section.

    0
  14. 970

    Fantastic post. It took me a little while to see the value in using custom post types but once I got my head around why they are useful I can’t stop using them. Every site I now work on I use custom post types, they make orgainsing different content so much easier and when combined with custom fields they make creating content simpler too.

    I’ve just recorded a video showing how I use custom post types on one of my websites, which some people new to the subject may find useful.

    Cheers, Neil
    Link to the video: http://www.neilcurtis.me/guides/what-are-custom-post-types/

    0
  15. 1021

    very useful tutorial. thanks dear. I am new to wp.
    I have create the texanomy area and add different categories/texonomies in that but now I have tried different ways that how to fetch the custom post data based on that particular texonomy.

    here is my code

    $query = new WP_Query( array(‘post_type’ => ‘books-shelves’, ‘books_category’ => 7, ‘posts_per_page’ => 8) );
    while ( $query->have_posts() ) : $query->the_post();

    will anybody please tell me the correct syntax. thanks in advance.

    0
  16. 1072

    Thank you Daniel, this tutorial really helped me!

    0
  17. 1123

    Hey Daniel,

    Thanks for the post. I came back to it a number of times to get things right. It helped me creating a humble plugin that uses this setup and has a decent user base (no link, not here to drive clicks :).
    Having said that, once this plugin is active, I noticed everytime I create a regular post, my database gets cluttered with additional metaboxes (with no value).

    Where should I look at to limit the scope of my metaboxes to my custom post type ?

    Keep up the good work !
    Greg

    0
  18. 1174

    Hello Sir, Thank you for your detailed tutorial. But I encountered an error after I added this function below:

    function my_taxonomies_product() {
    $labels = array(
    ‘name’ => _x( ‘Product Categories’, ‘taxonomy general name’ ),
    ‘singular_name’ => _x( ‘Product Category’, ‘taxonomy singular name’ ),
    ‘search_items’ => __( ‘Search Product Categories’ ),
    ‘all_items’ => __( ‘All Product Categories’ ),
    ‘parent_item’ => __( ‘Parent Product Category’ ),
    ‘parent_item_colon’ => __( ‘Parent Product Category:’ ),
    ‘edit_item’ => __( ‘Edit Product Category’ ),
    ‘update_item’ => __( ‘Update Product Category’ ),
    ‘add_new_item’ => __( ‘Add New Product Category’ ),
    ‘new_item_name’ => __( ‘New Product Category’ ),
    ‘menu_name’ => __( ‘Product Categories’ ),
    );
    $args = array(
    ‘labels’ => $labels,
    ‘hierarchical’ => true,
    );
    register_taxonomy( ‘product_category’, ‘product’, $args );
    }
    add_action( ‘init’, ‘my_taxonomies_product’, 0 );

    And I try to submit new category I the error are occurred below.

    Fatal error: Call to undefined function auth_redirect() in D:\xampp\htdocs\wp\dev_plugins\basic_plugins\wp-admin\admin.php on line 80

    Which I could not continue to save the category. Please advise. Thank you.

    0
  19. 1225

    Nice article Daniel. I would like to share a free and useful WordPress plugin “WP Show Stats” here. This plugin can show how many inbuilt and how many custom post types used in WordPress site. It will be very helpful for admin to keep track on how custom post types used and how many records are the for each custom post types. It also provides other various statics about usage of blog posts, categories, tags, users, comments, etc..
    https://wordpress.org/plugins/wp-show-stats
    I hope it will be useful for other readers of this post as well.

    0
  20. 1276

    Thanx sir this code is very useful for me :) Could you also please write the code how to add multiple images of post and multiple meta box? Thanks in advance.

    1
  21. 1327

    Thanks for the great article..it really helps a noob like me!

    Everything works great except for the archive page, it comes up with no results. So I setup an archive-[post_type].php with code provided above but in vain…
    Could anyone guide me to where I could look to get this working? thanks in advance…

    …and if you are feeling generous please also maybe point me to somewhere I can learn how to build a custom search form to include the custom meta box data and list the results?

    1

Leave a Comment

Yay! You've decided to leave a comment. That's fantastic! Please keep in mind that comments are moderated and rel="nofollow" is in use. So, please do not use a spammy keyword or a domain as your name, or else it will be deleted. Let's have a personal and meaningful conversation instead. Thanks for dropping by!

↑ Back to top