Registering custom post types in Wordpress - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to register a custom post type named 'book'.

Wordpress

<?php
function create_book_post_type() {
    register_post_type('book', [1]);
}
add_action('init', 'create_book_post_type');

Drag options to blanks, or click blank then click option'

Aarray('public' => true)

Barray('label' => 'Books')

Ctrue

D'public'

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a string instead of an array as the second argument.

Forgetting to set the 'public' key to true.

The register_post_type function requires an array of arguments as the second parameter to define the post type's behavior. Using array('public' => true) makes the post type publicly accessible.

2fill in blank

medium

Complete the code to add a label 'Books' to the custom post type.

Wordpress

<?php
function create_book_post_type() {
    register_post_type('book', array(
        'public' => true,
        'labels' => array(
            'name' => [1]
        )
    ));
}
add_action('init', 'create_book_post_type');

Drag options to blanks, or click blank then click option'

A'Book'

B'Books'

C'books'

D'BOOKS'

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular form 'Book' instead of plural.

Using lowercase or all uppercase which is less readable.

The 'name' label should be the plural form of the post type, so 'Books' is correct.

3fill in blank

hard

Fix the error in the code to make the custom post type support the editor feature.

Wordpress

<?php
function create_book_post_type() {
    register_post_type('book', array(
        'public' => true,
        'supports' => [1]
    ));
}
add_action('init', 'create_book_post_type');

Drag options to blanks, or click blank then click option'

A'editor'

Barray('edit')

Carray('editor')

D'supports'

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a string instead of an array to 'supports'.

Using incorrect feature names like 'edit'.

The 'supports' argument expects an array of features. To enable the editor, use array('editor').

4fill in blank

hard

Fill both blanks to register a custom post type 'movie' with public visibility and archive support.

Wordpress

<?php
function create_movie_post_type() {
    register_post_type('movie', array(
        'public' => [1],
        'has_archive' => [2]
    ));
}
add_action('init', 'create_movie_post_type');

Drag options to blanks, or click blank then click option'

Atrue

Bfalse

C'true'

D'false'

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings 'true' or 'false' instead of booleans.

Setting 'has_archive' to false when archive is needed.

Both 'public' and 'has_archive' should be set to the boolean true (without quotes) to enable public visibility and archive pages.

5fill in blank

hard

Fill all three blanks to register a custom post type 'album' with label 'Albums', public visibility, and support for title and thumbnail.

Wordpress

<?php
function create_album_post_type() {
    register_post_type('album', array(
        'labels' => array('name' => [1]),
        'public' => [2],
        'supports' => [3]
    ));
}
add_action('init', 'create_album_post_type');

Drag options to blanks, or click blank then click option'

A'Albums'

Btrue

Carray('title', 'thumbnail')

D'Album'

Attempts:

3 left

💡 Hint

Common Mistakes

Using singular label instead of plural.

Passing 'supports' as a string instead of an array.

Using string 'true' instead of boolean true.

Use 'Albums' as the plural label, set 'public' to boolean true, and 'supports' to an array with 'title' and 'thumbnail' to enable those features.

Practice

1. What is the main purpose of registering a custom post type in WordPress?

easy

A. To create a new type of content different from posts and pages

B. To change the WordPress theme

C. To add a new user role

D. To install a plugin automatically

Solution

1. Step 1: Understand WordPress content types

   WordPress has default content types like posts and pages, but custom post types allow adding new content types.

2. Step 2: Purpose of custom post types

   Registering a custom post type lets you organize and display content that doesn't fit posts or pages.

3. Final Answer:

   To create a new type of content different from posts and pages -> Option A

4. Quick Check:

   Custom post types = new content types [OK]

Hint: Custom post types add new content types beyond posts/pages [OK]

Common Mistakes:

• Confusing custom post types with themes or plugins
• Thinking it changes user roles
• Assuming it installs plugins automatically

2. Which of the following is the correct way to hook the register_post_type function in WordPress?

easy

A. add_action('init', 'register_post_type')

B. add_action('wp_head', 'register_post_type')

C. add_filter('init', 'register_post_type')

D. add_action('admin_menu', 'register_post_type')

Solution

1. Step 1: Identify the correct hook for registering post types

   The init hook is the standard place to register custom post types in WordPress.

2. Step 2: Use add_action with 'init'

   Using add_action('init', 'register_post_type') correctly hooks the function to run at initialization.

3. Final Answer:

   add_action('init', 'register_post_type') -> Option A

4. Quick Check:

   Hook register_post_type on init [OK]

Hint: Use 'init' hook with add_action for registering post types [OK]

Common Mistakes:

• Using add_filter instead of add_action
• Hooking into 'wp_head' or 'admin_menu' incorrectly
• Calling register_post_type directly without a hook

3. What will be the effect of this code snippet?

add_action('init', function() {
  register_post_type('book', [
    'label' => 'Books',
    'public' => true,
    'supports' => ['title', 'editor']
  ]);
});

medium

A. Causes a syntax error due to missing semicolons

B. Creates a private post type called 'book' without editor support

C. Creates a new public post type called 'book' with title and editor support

D. Registers a taxonomy instead of a post type

Solution

1. Step 1: Analyze the register_post_type parameters

   The code registers a post type named 'book' with label 'Books', public visibility, and supports title and editor features.

2. Step 2: Understand the effect of 'public' and 'supports'

   Setting 'public' to true makes it visible on the site, and 'supports' enables editing title and content.

3. Final Answer:

   Creates a new public post type called 'book' with title and editor support -> Option C

4. Quick Check:

   register_post_type with public true and supports = A [OK]

Hint: Check 'public' and 'supports' keys for post type behavior [OK]

Common Mistakes:

• Confusing post type with taxonomy
• Assuming missing semicolons cause errors in PHP arrays
• Thinking 'public' false means visible

4. Identify the error in this custom post type registration code:

function create_movie_post_type() {
  register_post_type('movie', [
    'label' => 'Movies',
    'public' => true,
    'supports' => 'title,editor'
  ]);
}
add_action('init', 'create_movie_post_type');

medium

A. The hook 'init' is incorrect for registering post types

B. Missing a closing parenthesis in register_post_type

C. The function name cannot contain underscores

D. 'supports' should be an array, not a string

Solution

1. Step 1: Check the 'supports' argument type

   The 'supports' argument must be an array of features, but here it is a string with comma-separated values.

2. Step 2: Correct the 'supports' argument

   It should be ['title', 'editor'] instead of 'title,editor' to work properly.

3. Final Answer:

   'supports' should be an array, not a string -> Option D

4. Quick Check:

   'supports' requires array format [OK]

Hint: Use array for 'supports', not comma string [OK]

Common Mistakes:

• Passing 'supports' as a string instead of array
• Using wrong hook instead of 'init'
• Incorrect function naming conventions

5. You want to register a custom post type 'event' that is public, supports title, editor, and custom fields, and has a custom menu icon. Which code snippet correctly achieves this?

hard

A. register_post_type('event', ['public' => false, 'supports' => ['title', 'editor'], 'menu_icon' => 'calendar']);

B. register_post_type('event', ['public' => true, 'supports' => ['title', 'editor', 'custom-fields'], 'menu_icon' => 'dashicons-calendar']);

C. register_post_type('event', ['public' => true, 'supports' => 'title,editor,custom-fields', 'menu_icon' => 'dashicons-calendar']);

D. register_post_type('event', ['public' => true, 'supports' => ['title', 'editor'], 'menu_icon' => 'dashicons-event']);

Solution

1. Step 1: Check 'public' and 'supports' keys

   The post type must be public and support title, editor, and custom fields, so 'public' => true and 'supports' => ['title', 'editor', 'custom-fields'] are correct.

2. Step 2: Verify 'menu_icon' value

   The icon must be a valid Dashicons class like 'dashicons-calendar'. register_post_type('event', ['public' => true, 'supports' => ['title', 'editor', 'custom-fields'], 'menu_icon' => 'dashicons-calendar']); uses this correctly.

3. Step 3: Identify errors in other options

   register_post_type('event', ['public' => false, 'supports' => ['title', 'editor'], 'menu_icon' => 'calendar']); sets 'public' false and wrong icon string; register_post_type('event', ['public' => true, 'supports' => 'title,editor,custom-fields', 'menu_icon' => 'dashicons-calendar']); uses string for 'supports'; register_post_type('event', ['public' => true, 'supports' => ['title', 'editor'], 'menu_icon' => 'dashicons-event']); misses 'custom-fields' support.

4. Final Answer:

   register_post_type('event', ['public' => true, 'supports' => ['title', 'editor', 'custom-fields'], 'menu_icon' => 'dashicons-calendar']); -> Option B

5. Quick Check:

   Correct keys and values for event post type [OK]

Hint: Use array for supports and valid dashicons for menu_icon [OK]

Common Mistakes:

• Using string instead of array for 'supports'
• Setting 'public' to false by mistake
• Using invalid icon names