Custom meta boxes in Wordpress - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a custom meta box in WordPress.

Wordpress

add_action('add_meta_boxes', '[1]');

function my_custom_meta_box() {
    add_meta_box(
        'my_meta_box_id',
        'My Meta Box',
        'my_meta_box_callback',
        'post'
    );
}

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

Aregister_meta_box

Bmy_custom_meta_box

Cadd_my_meta_box

Dcreate_meta_box

Attempts:

3 left

💡 Hint

Common Mistakes

Using a function name that does not exist.

Confusing the hook name with the callback function.

The 'add_meta_boxes' action hook requires a callback function name that adds the meta box. Here, 'my_custom_meta_box' is the correct function.

2fill in blank

medium

Complete the code to save the custom meta box data when the post is saved.

Wordpress

add_action('save_post', '[1]');

function save_my_meta_box_data($post_id) {
    if (!isset($_POST['my_meta_box_nonce'])) {
        return;
    }
    // Additional saving logic here
}

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

Aupdate_meta_box_data

Bsave_custom_meta

Csave_my_meta_box_data

Dstore_meta_box

Attempts:

3 left

💡 Hint

Common Mistakes

Using a function name that does not exist.

Not hooking the save function properly.

The 'save_post' hook requires a callback function that handles saving. The function 'save_my_meta_box_data' matches the saving logic.

3fill in blank

hard

Fix the error in the code to correctly display the meta box field value.

Wordpress

function my_meta_box_callback($post) {
    $value = get_post_meta($post->ID, '[1]', true);
    echo '<label for="my_field">Description:</label>';
    echo '<input type="text" id="my_field" name="my_field" value="' . esc_attr($value) . '" />';
}

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

Amy_field

Bmy_field_value

Cfield_value

Dcustom_field

Attempts:

3 left

💡 Hint

Common Mistakes

Using a meta key that does not match the saved data.

Mismatching input name and meta key.

The meta key used in get_post_meta must match the name used to save the field. 'my_field' is the correct meta key here.

4fill in blank

hard

Fill both blanks to correctly verify the nonce and check user permissions before saving meta box data.

Wordpress

function save_my_meta_box_data($post_id) {
    if (!isset($_POST['[1]']) || !wp_verify_nonce($_POST['[1]'], '[2]')) {
        return;
    }
    if (!current_user_can('edit_post', $post_id)) {
        return;
    }
    // Save meta box data here
}

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

Amy_meta_box_nonce

Bsave_nonce

Cmy_meta_box_action

Dnonce_check

Attempts:

3 left

💡 Hint

Common Mistakes

Using different strings for nonce name and action.

Not verifying nonce before saving.

The nonce field name and the nonce action string must match. Here, both are 'my_meta_box_nonce' to verify correctly.

5fill in blank

hard

Fill all three blanks to correctly register a meta box, display its field, and save the data securely.

Wordpress

add_action('add_meta_boxes', '[1]');
add_action('save_post', '[2]');

function [1]() {
    add_meta_box('custom_box', 'Custom Box', '[3]', 'post');
}

function [3]($post) {
    wp_nonce_field('custom_box_nonce_action', 'custom_box_nonce');
    $value = get_post_meta($post->ID, 'custom_field', true);
    echo '<input type="text" name="custom_field" value="' . esc_attr($value) . '" />';
}

function [2]($post_id) {
    if (!isset($_POST['custom_box_nonce']) || !wp_verify_nonce($_POST['custom_box_nonce'], 'custom_box_nonce_action')) {
        return;
    }
    if (!current_user_can('edit_post', $post_id)) {
        return;
    }
    if (isset($_POST['custom_field'])) {
        update_post_meta($post_id, 'custom_field', sanitize_text_field($_POST['custom_field']));
    }
}

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

Aregister_custom_meta_box

Bsave_custom_meta_box_data

Cdisplay_custom_meta_box

Dcustom_meta_box_callback

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up function names between hooks and callbacks.

Not matching callback names in add_meta_box.

The add_meta_boxes hook calls 'register_custom_meta_box', the save_post hook calls 'save_custom_meta_box_data', and the meta box callback is 'custom_meta_box_callback'.

Practice

1. What is the main purpose of adding a custom meta box in WordPress?

easy

A. To change the theme colors automatically

B. To create new user roles

C. To add extra input fields on the post edit screen

D. To optimize the website speed

Solution

1. Step 1: Understand what meta boxes do

   Meta boxes provide extra areas on the post edit screen for input.

2. Step 2: Identify the purpose of custom meta boxes

   They allow adding custom fields to collect extra data for posts or pages.

3. Final Answer:

   To add extra input fields on the post edit screen -> Option C

4. Quick Check:

   Custom meta boxes = extra input fields [OK]

Hint: Meta boxes add fields on edit screens [OK]

Common Mistakes:

• Confusing meta boxes with theme or user settings
• Thinking meta boxes change site speed
• Assuming meta boxes create user roles

2. Which function is used to add a custom meta box in WordPress?

easy

A. add_meta_box()

B. register_meta_box()

C. add_custom_box()

D. create_meta_box()

Solution

1. Step 1: Recall WordPress function for meta boxes

   The official function to add meta boxes is add_meta_box().

2. Step 2: Verify other options

   Other options are not valid WordPress functions for meta boxes.

3. Final Answer:

   add_meta_box() -> Option A

4. Quick Check:

   Use add_meta_box() to add meta boxes [OK]

Hint: Remember exact function name: add_meta_box() [OK]

Common Mistakes:

• Using incorrect function names like add_custom_box()
• Confusing with register_meta_box() which doesn't exist
• Trying to create meta boxes without this function

3. Given this code snippet, what will be the output on the post edit screen?

add_action('add_meta_boxes', function() {
  add_meta_box('my_box', 'My Box', function() {
    echo '<input type="text" name="my_field" value="Hello" />';
  }, 'post');
});

medium

A. A checkbox labeled 'My Box' with 'Hello' inside

B. A text input box labeled 'My Box' with 'Hello' inside

C. No meta box will appear because 'post' is invalid

D. An error because the callback function is missing parameters

Solution

1. Step 1: Analyze add_meta_box parameters

   The ID is 'my_box', title is 'My Box', callback outputs a text input with value 'Hello', and screen is 'post'.

2. Step 2: Understand the callback output

   The callback prints an input box of type text with name 'my_field' and value 'Hello'.

3. Final Answer:

   A text input box labeled 'My Box' with 'Hello' inside -> Option B

4. Quick Check:

   Callback outputs text input with value 'Hello' [OK]

Hint: Callback echoes input field HTML inside meta box [OK]

Common Mistakes:

• Thinking callback needs parameters to work
• Assuming 'post' is invalid screen
• Confusing input types (text vs checkbox)

4. What is wrong with this code snippet for saving meta box data?

add_action('save_post', function($post_id) {
  update_post_meta($post_id, 'my_field', $_POST['my_field']);
});

medium

A. It should echo the data instead of updating

B. It uses the wrong hook; should be 'add_meta_box'

C. It updates meta with wrong function; should use add_post_meta

D. It lacks a nonce check for security

Solution

1. Step 1: Check security best practices

   Saving meta box data requires verifying a nonce to prevent unauthorized saves.

2. Step 2: Identify missing nonce check

   The code updates post meta directly without checking nonce or user permissions.

3. Final Answer:

   It lacks a nonce check for security -> Option D

4. Quick Check:

   Always verify nonce before saving meta data [OK]

Hint: Always check nonce before saving meta data [OK]

Common Mistakes:

• Skipping nonce verification
• Using wrong hook for saving data
• Confusing update_post_meta with add_post_meta

5. You want to add a custom meta box that only appears on pages (not posts) and saves a checkbox value safely. Which steps are correct to implement this?

hard

A. Use add_meta_box with 'page' screen, output checkbox in callback, save with save_post hook including nonce and permission checks

B. Use add_meta_box with 'post' screen, output checkbox, save without nonce check

C. Use add_meta_box with 'page' screen, output text input, save with save_post hook but no permission check

D. Use add_meta_box with 'post' screen, output checkbox, save with add_post_meta function

Solution

1. Step 1: Choose correct screen and output

   To show on pages only, use 'page' as screen in add_meta_box and output a checkbox input in the callback.

2. Step 2: Save data securely

   Use the 'save_post' hook to save data, but include nonce verification and user permission checks to ensure security.

3. Final Answer:

   Use add_meta_box with 'page' screen, output checkbox in callback, save with save_post hook including nonce and permission checks -> Option A

4. Quick Check:

   Screen='page', checkbox output, secure save with nonce [OK]

Hint: Match screen type and add nonce checks when saving [OK]

Common Mistakes:

• Using wrong screen type ('post' instead of 'page')
• Skipping nonce or permission checks
• Saving checkbox as text input