Custom post type arguments in Wordpress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the effect of 'public' => false in a custom post type?

Consider this custom post type registration snippet:

register_post_type( 'book', array( 'public' => false, 'show_ui' => true ) );

What will be the visible behavior in the WordPress admin dashboard?

Wordpress

register_post_type( 'book', array( 'public' => false, 'show_ui' => true ) );

A The post type is hidden both in admin UI and front-end.

B The post type is visible on the front-end but hidden in admin UI.

C The post type is visible both in admin UI and front-end.

D The post type is visible in admin UI but not accessible on the front-end.

💡 Hint

Think about what 'public' controls versus 'show_ui'.

The 'public' argument controls front-end visibility and queryability. Setting it to false hides the post type from front-end queries. However, 'show_ui' controls admin dashboard visibility. Since 'show_ui' is true, the post type appears in admin but not on the front-end.

📝 Syntax

intermediate

Which argument correctly enables REST API support for a custom post type?

You want your custom post type to be accessible via the WordPress REST API. Which argument must be set to true in register_post_type?

Wordpress

register_post_type( 'movie', array( /* arguments here */ ) );

A 'show_in_rest' => true

B 'rest_support' => true

C 'enable_rest' => true

D 'rest_api' => true

💡 Hint

Look for the exact argument name used in WordPress documentation.

The correct argument to enable REST API support is 'show_in_rest'. Setting it to true makes the post type available in the REST API endpoints.

❓ state_output

advanced

What is the slug used in URLs for this custom post type?

Given this registration code:

register_post_type( 'album', array( 'rewrite' => array( 'slug' => 'music' ), 'public' => true ) );

What will be the base URL slug for single 'album' posts?

Wordpress

register_post_type( 'album', array( 'rewrite' => array( 'slug' => 'music' ), 'public' => true ) );

A /music/{post-name}/

B /album/{post-name}/

C /albums/{post-name}/

D /post/{post-name}/

💡 Hint

The 'rewrite' argument controls the URL slug.

The 'rewrite' argument with 'slug' set to 'music' means single posts of this type will have URLs starting with '/music/'.

🔧 Debug

advanced

Why does this custom post type not appear in the admin menu?

This code registers a custom post type but it does not show in the WordPress admin menu:

register_post_type( 'event', array( 'public' => true, 'show_ui' => false ) );

What is the cause?

Wordpress

register_post_type( 'event', array( 'public' => true, 'show_ui' => false ) );

A 'show_in_menu' must be true to appear in admin menu.

B 'show_ui' is false, so admin menu is hidden.

C Missing 'menu_position' argument causes it to be hidden.

D 'public' must be false to show in admin menu.

💡 Hint

Check the meaning of 'show_ui' argument.

The 'show_ui' argument controls whether the post type appears in the admin dashboard menu. Setting it to false hides it from the menu even if 'public' is true.

🧠 Conceptual

expert

Which argument controls whether a custom post type supports hierarchical parent-child relationships?

You want your custom post type to behave like pages, allowing parent and child posts. Which argument enables this?

A 'supports' => ['parent']

B 'parentable' => true

C 'hierarchical' => true

D 'nested' => true

💡 Hint

Think about the argument that controls post relationships.

The 'hierarchical' argument set to true allows the post type to have parent and child posts, similar to pages.