Template parts in Wordpress - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to include a template part named 'header'.

Wordpress

<?php get_[1]('header'); ?>

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

Atemplate_part_include

Btemplate_part_load

Ctemplate_part

Dtemplate_part_get

Attempts:

3 left

💡 Hint

Common Mistakes

Using functions that do not exist like get_template_part_include.

Confusing with functions that load full templates.

The correct function to include a template part in WordPress is get_template_part().

2fill in blank

medium

Complete the code to include a template part named 'content' with a slug 'single'.

Wordpress

<?php get_template_part('content', [1]); ?>

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

A'single'

B'page'

C'archive'

D'footer'

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong slug name that does not match the file.

Omitting quotes around the slug string.

The second argument in get_template_part() is the slug, here 'single' to load content-single.php.

3fill in blank

hard

Fix the error in the code to correctly include the sidebar template part.

Wordpress

<?php get_template_part([1]); ?>

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

A"sidebar"

B'sidebar'

Csidebar

Dsidebar.php

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the template part name without quotes causing syntax errors.

Including the '.php' extension which is not needed.

The template part name must be a quoted string without the file extension.

4fill in blank

hard

Fill both blanks to include a template part named 'footer' with a slug 'custom'.

Wordpress

<?php get_template_part([1], [2]); ?>

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

A'footer'

B'header'

C'custom'

D'sidebar'

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the order of arguments.

Using incorrect names that do not match template files.

The first argument is the template part name 'footer', the second is the slug 'custom'.

5fill in blank

hard

Fill all three blanks to include a template part named 'content' with slug 'page' and pass an array of variables.

Wordpress

<?php get_template_part([1], [2], [3]); ?>

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

A'content'

B'page'

Carray('title' => 'Welcome')

Darray('footer' => true)

Attempts:

3 left

💡 Hint

Common Mistakes

Passing variables as a string instead of an array.

Omitting the third argument when variables are needed.

The first two arguments specify the template part and slug; the third passes variables as an array.

Practice

1. What is the main purpose of using get_template_part() in WordPress themes?

easy

A. To create database tables

B. To register new custom post types

C. To include reusable template parts and keep code organized

D. To enqueue styles and scripts

Solution

1. Step 1: Understand the function role

   get_template_part() is designed to include reusable parts of a theme, like headers or footers.

2. Step 2: Compare with other options

   Registering post types, enqueuing scripts, and creating tables are unrelated to template parts.

3. Final Answer:

   To include reusable template parts and keep code organized -> Option C

4. Quick Check:

   Template parts = reusable code pieces [OK]

Hint: Remember: template parts reuse code pieces [OK]

Common Mistakes:

• Confusing template parts with post type registration
• Thinking it manages scripts or styles
• Assuming it handles database operations

2. Which of the following is the correct syntax to include a template part named 'content' with a specific variation 'single'?

easy

A. get_template_part('content', 'single');

B. get_template_part('single', 'content');

C. get_template_part('content-single');

D. get_template_part('content', single);

Solution

1. Step 1: Recall function parameters

   get_template_part() takes two string arguments: slug and optional name.

2. Step 2: Match correct order and syntax

   The correct call is get_template_part('content', 'single'); with both parameters as strings.

3. Final Answer:

   get_template_part('content', 'single'); -> Option A

4. Quick Check:

   Slug then name as strings [OK]

Hint: Use two strings: slug first, then name [OK]

Common Mistakes:

• Passing combined slug and name as one string
• Swapping slug and name order
• Forgetting quotes around name

3. Given the code snippet:

get_template_part('header');

What file will WordPress try to load first?

medium

A. header.php

B. header-header.php

C. header-single.php

D. header-template.php

Solution

1. Step 1: Understand default file naming

   When only slug is given, WordPress looks for {slug}.php file.

2. Step 2: Apply to example

   Slug is 'header', so WordPress loads header.php.

3. Final Answer:

   header.php -> Option A

4. Quick Check:

   Slug only loads slug.php [OK]

Hint: Slug alone loads slug.php file [OK]

Common Mistakes:

• Expecting a suffix like '-header' automatically
• Confusing with named template parts
• Assuming different file extensions

4. What is wrong with this code snippet?

get_template_part('footer', single);

medium

A. No issues, code works fine

B. Wrong function name, should be get_template_parts

C. Footer template parts cannot have a name

D. Missing quotes around 'single' causing a syntax error

Solution

1. Step 1: Check parameter types

   Both slug and name must be strings, so 'single' needs quotes.

2. Step 2: Identify error cause

   Without quotes, single is treated as a constant or variable, causing syntax error.

3. Final Answer:

   Missing quotes around 'single' causing a syntax error -> Option D

4. Quick Check:

   Strings need quotes [OK]

Hint: Always quote slug and name strings [OK]

Common Mistakes:

• Omitting quotes around name parameter
• Using wrong function name
• Thinking named parts are not allowed

5. You want to create a reusable sidebar template part with two variations: 'left' and 'right'. Which folder structure and code usage is correct to achieve this?

hard

A. Files: sidebar-left.php, sidebar-right.php inside /parts/ folder; Code: get_template_part('sidebar', 'left');

B. Files: sidebar-left.php, sidebar-right.php in theme root; Code: get_template_part('sidebar', 'left');

C. Files: sidebar.php only; Code: get_template_part('sidebar-left');

D. Files: sidebar-left.php, sidebar-right.php in theme root; Code: get_template_part('sidebar-left');

Solution

1. Step 1: Understand file naming for variations

   Named template parts use {slug}-{name}.php in theme root.

2. Step 2: Match code to file structure

   Calling get_template_part('sidebar', 'left'); loads sidebar-left.php.

3. Step 3: Evaluate other options

   B places files in subfolder without adjusting slug to include path; C uses only one file; D uses combined slug-name as one string incorrectly.

4. Final Answer:

   Files: sidebar-left.php, sidebar-right.php in theme root; Code: get_template_part('sidebar', 'left'); -> Option B

5. Quick Check:

   Slug-name files in root with two-string call [OK]

Hint: Use slug-name.php files in root, call with two strings [OK]

Common Mistakes:

• Placing files in subfolders without adjusting code
• Passing combined slug-name as one string
• Using only one file for multiple variations