Custom post type arguments in Wordpress

Introduction

Custom post type arguments tell WordPress how to create and show your new content type. They control what features it has and how it behaves.

You want to add a new content type like 'Books' or 'Recipes' to your website.

You need to control if your content type appears in menus or search results.

You want to decide what editing features are available for your custom content.

You want to set custom labels and icons for your content type in the admin area.

Syntax

Wordpress

register_post_type('post_type_name', [
  'labels' => [
    'name' => 'Plural Name',
    'singular_name' => 'Singular Name'
  ],
  'public' => true,
  'has_archive' => true,
  'supports' => ['title', 'editor', 'thumbnail'],
  'menu_icon' => 'dashicons-admin-post'
]);

The first argument is the unique name for your post type (lowercase, no spaces).

The second argument is an array of options that control how the post type works and looks.

Examples

Creates a public 'book' post type with archive pages enabled.

Wordpress

register_post_type('book', [
  'labels' => [
    'name' => 'Books',
    'singular_name' => 'Book'
  ],
  'public' => true,
  'has_archive' => true
]);

Creates a 'movie' post type that is not public but visible in the admin area with title and editor support.

Wordpress

register_post_type('movie', [
  'labels' => [
    'name' => 'Movies',
    'singular_name' => 'Movie'
  ],
  'public' => false,
  'show_ui' => true,
  'supports' => ['title', 'editor']
]);

Creates a 'recipe' post type with a carrot icon and supports comments and thumbnails.

Wordpress

register_post_type('recipe', [
  'labels' => [
    'name' => 'Recipes',
    'singular_name' => 'Recipe'
  ],
  'public' => true,
  'menu_icon' => 'dashicons-carrot',
  'supports' => ['title', 'editor', 'thumbnail', 'comments']
]);

Sample Program

This code creates a new post type called 'event' that is public, has archive pages, supports title, editor, and thumbnail, and uses a calendar icon in the admin menu.

Wordpress

<?php
function create_custom_post_type() {
  register_post_type('event', [
    'labels' => [
      'name' => 'Events',
      'singular_name' => 'Event'
    ],
    'public' => true,
    'has_archive' => true,
    'supports' => ['title', 'editor', 'thumbnail'],
    'menu_icon' => 'dashicons-calendar-alt'
  ]);
}
add_action('init', 'create_custom_post_type');

Important Notes

Always hook your custom post type registration to the 'init' action to ensure WordPress is ready.

Use descriptive labels to make the admin area user-friendly.

Setting 'public' to false hides the post type from the front end but can still show it in admin if 'show_ui' is true.

Summary

Custom post type arguments define how your new content type behaves and looks.

Use the 'labels', 'public', 'supports', and 'menu_icon' keys to customize your post type.

Register your post type inside a function hooked to 'init' for proper loading.

Practice

1. Which argument in register_post_type controls whether the custom post type appears in the WordPress admin menu?

easy

A. public

B. menu_position

C. supports

D. rewrite

Solution

1. Step 1: Understand the role of menu_position

   The menu_position argument sets the location of the custom post type in the WordPress admin menu.

2. Step 2: Compare with other arguments

   public controls visibility on front-end, supports defines features, rewrite controls URL structure.

3. Final Answer:

   menu_position -> Option B

4. Quick Check:

   Admin menu location = menu_position [OK]

Hint: Menu location is set by menu_position argument [OK]

Common Mistakes:

• Confusing public with menu visibility
• Thinking supports controls menu
• Assuming rewrite affects admin menu

2. Which of the following is the correct way to set a custom post type to be publicly queryable in register_post_type arguments?

easy

A. "public_queryable" => true

B. "publiclyqueryable" => true

C. "public_queryable" => "true"

D. "publicly_queryable" => true

Solution

1. Step 1: Recall the exact argument name

   The correct argument is publicly_queryable with an 'ly' and underscore.

2. Step 2: Check value type and spelling

   The value must be boolean true, not string, and spelling must be exact.

3. Final Answer:

   "publicly_queryable" => true -> Option D

4. Quick Check:

   Correct spelling and boolean value = publicly_queryable true [OK]

Hint: Remember 'publicly_queryable' with 'ly' and boolean true [OK]

Common Mistakes:

• Misspelling argument name
• Using string "true" instead of boolean true
• Omitting underscore

3. Given this code snippet, what will be the value of $args['has_archive'] after registration?

$args = [
  'public' => true,
  'has_archive' => false,
  'rewrite' => ['slug' => 'books']
];
register_post_type('book', $args);

medium

A. true

B. null

C. false

D. array with slug 'books'

Solution

1. Step 1: Check the has_archive argument value

   It is explicitly set to false in the array.

2. Step 2: Understand effect of rewrite on has_archive

   The rewrite argument does not override has_archive setting.

3. Final Answer:

   false -> Option C

4. Quick Check:

   Explicit has_archive false remains false [OK]

Hint: Explicit has_archive false stays false despite rewrite [OK]

Common Mistakes:

• Assuming rewrite slug enables archive
• Confusing has_archive with rewrite
• Thinking default true overrides false

4. Identify the error in this register_post_type argument array:

$args = [
  'public' => 'yes',
  'supports' => 'title,editor',
  'menu_icon' => 'dashicons-book'
];
register_post_type('book', $args);

medium

A. 'supports' should be an array, not a comma-separated string

B. 'public' should be boolean true, not string 'yes'

C. 'menu_icon' value is invalid, should be a URL

D. No errors, code is correct

Solution

1. Step 1: Check the supports argument type

   supports must be an array of features, not a string.

2. Step 2: Verify other arguments

   public accepts boolean or string 'true'/'false', 'yes' is invalid but PHP may coerce; menu_icon accepts dashicons slug.

3. Final Answer:

   'supports' should be an array, not a comma-separated string -> Option A

4. Quick Check:

   Supports must be array, not string [OK]

Hint: Supports argument must be an array, not a string [OK]

Common Mistakes:

• Passing supports as string instead of array
• Using invalid string for public
• Thinking menu_icon needs URL

5. You want to create a custom post type 'movie' that is public, supports title and editor, has an archive page at '/films', and appears below Posts in the admin menu. Which $args array is correct?

hard

A. {
'public' => true,
'supports' => ['title', 'editor'],
'has_archive' => true,
'rewrite' => ['slug' => 'films'],
'menu_position' => 5
}

B. {
'public' => true,
'supports' => ['title', 'editor'],
'has_archive' => 'films',
'rewrite' => true,
'menu_position' => 20
}

C. {
'public' => true,
'supports' => 'title,editor',
'has_archive' => true,
'rewrite' => ['slug' => 'movies'],
'menu_position' => 5
}

D. {
'public' => false,
'supports' => ['title', 'editor'],
'has_archive' => true,
'rewrite' => ['slug' => 'films'],
'menu_position' => 5
}

Solution

1. Step 1: Check public visibility and supports

   { 'public' => true, 'supports' => ['title', 'editor'], 'has_archive' => true, 'rewrite' => ['slug' => 'films'], 'menu_position' => 5 } sets public to true and supports as an array with 'title' and 'editor', which is correct.

2. Step 2: Verify archive and rewrite slug

   has_archive is true and rewrite slug is 'films' to get archive at '/films'.

3. Step 3: Confirm menu position

   menu_position 5 places it below Posts in admin menu.

4. Final Answer:

   Option A matches all requirements correctly -> Option A

5. Quick Check:

   Public, supports array, archive slug, menu position 5 = { 'public' => true, 'supports' => ['title', 'editor'], 'has_archive' => true, 'rewrite' => ['slug' => 'films'], 'menu_position' => 5 } [OK]

Hint: Use array for supports, boolean for public, correct slug in rewrite [OK]

Common Mistakes:

• Passing supports as string instead of array
• Setting public false when it should be true
• Incorrect has_archive or rewrite values