Why Custom post type arguments in Wordpress? - Purpose & Use Cases

The Big Idea

What if you could create your own content types that fit your site perfectly without messy hacks?

The Scenario

Imagine you want to add a new type of content to your WordPress site, like 'Books' or 'Recipes', but you try to do it by manually creating pages and posts without any structure.

The Problem

Manually managing different content types as regular posts or pages gets messy fast. You lose control over how they appear, how they behave, and it's hard to organize or customize them properly.

The Solution

Custom post type arguments let you define exactly how your new content type works--its labels, visibility, features, and more--making your site organized and easy to manage.

Before vs After

✗ Before

Create a new page for each book and tag it manually.

✓ After

register_post_type('book', ['labels' => ['name' => 'Books'], 'public' => true, 'supports' => ['title', 'editor', 'thumbnail']]);

What It Enables

You can create tailored content types that behave exactly how you want, improving site structure and user experience.

Real Life Example

A cooking blog uses a 'Recipe' custom post type with custom fields for ingredients and cooking time, making recipes easy to add, find, and display.

Key Takeaways

Manual content management is confusing and unorganized.

Custom post type arguments let you customize new content types easily.

This leads to better site structure and easier content management.

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