CMS architecture overview in Wordpress - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the main WordPress configuration file name.

Wordpress

<?php
// The main configuration file is named [1]

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

Aindex.php

Bfunctions.php

Cwp-config.php

Dstyle.css

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing the configuration file with theme files.

Using 'index.php' as the config file name.

The main configuration file for WordPress is wp-config.php. It contains database settings and other important configurations.

2fill in blank

medium

Complete the code to show how WordPress loads plugins from the {{BLANK_1}} directory.

Wordpress

<?php
$plugin_dir = WP_CONTENT_DIR . '/[1]';
// Plugins are loaded from this directory

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

Acache

Buploads

Cthemes

Dplugins

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'themes' instead of 'plugins'.

Confusing uploads folder with plugins.

WordPress loads plugins from the plugins directory inside the content folder.

3fill in blank

hard

Fix the error in the code to correctly include the WordPress core file.

Wordpress

<?php
require_once(ABSPATH . '[1]');

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

Awp-settings.php

Bwp-config.php

Cindex.php

Dfunctions.php

Attempts:

3 left

💡 Hint

Common Mistakes

Including 'wp-config.php' here causes errors.

Using theme files instead of core files.

The core WordPress settings file to include is wp-settings.php, which sets up the environment.

4fill in blank

hard

Fill both blanks to create a WordPress hook that runs a function on initialization.

Wordpress

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

function my_init_function() {
  // Initialization code here
}

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

Ainit

Bwp_head

Cmy_init_function

Dwp_footer

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing hook names with function names.

Using hooks that run too late or too early.

The init hook runs early in WordPress loading. The function name must match the callback.

5fill in blank

hard

Fill all three blanks to register a custom post type in WordPress.

Wordpress

function register_[1]_post_type() {
  register_post_type('[2]', [
    'labels' => ['name' => '[3]'],
    'public' => true,
  ]);
}
add_action('init', 'register_[1]_post_type');

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

Abook

CBooks

Dmovie

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for function and post type slug.

Incorrect label casing or spelling.

This code registers a custom post type called 'book' with the label 'Books'. The function and post type names must match.

Practice

1. Which part of WordPress is responsible for storing all the website content like posts and pages?

easy

A. The admin dashboard

B. The theme

C. The database

D. The plugin system

Solution

1. Step 1: Understand WordPress content storage

   WordPress stores all posts, pages, and settings in a database to keep data organized and retrievable.

2. Step 2: Identify the correct component

   The database is the part that holds all content, while themes and plugins control appearance and features.

3. Final Answer:

   The database -> Option C

4. Quick Check:

   Content storage = database [OK]

Hint: Content is saved in the database, not themes or plugins [OK]

Common Mistakes:

• Confusing themes with content storage
• Thinking plugins store content
• Assuming admin dashboard holds content

2. Which of the following is the correct way to describe a WordPress theme's role?

easy

A. It manages the website's database

B. It updates WordPress core automatically

C. It handles user authentication

D. It controls the website's appearance and layout

Solution

1. Step 1: Understand the theme's purpose

   The theme defines how the website looks, including colors, fonts, and layout.

2. Step 2: Match the description to the theme

   Only It controls the website's appearance and layout correctly states the theme controls appearance and layout.

3. Final Answer:

   It controls the website's appearance and layout -> Option D

4. Quick Check:

   Themes = appearance/layout [OK]

Hint: Themes change look, not data or security [OK]

Common Mistakes:

• Thinking themes manage database
• Confusing themes with security features
• Believing themes update WordPress core

3. Consider this WordPress setup: The core files, a theme, and a plugin are installed. Which part is responsible for adding new features like contact forms?

medium

A. The plugin

B. The theme

C. The core files

D. The database

Solution

1. Step 1: Identify feature extension in WordPress

   Plugins add new features and functions without changing core files or themes.

2. Step 2: Match feature addition to component

   Contact forms are typical plugin features, so plugins handle this.

3. Final Answer:

   The plugin -> Option A

4. Quick Check:

   New features = plugins [OK]

Hint: Plugins add features; themes change look [OK]

Common Mistakes:

• Assuming core files add features
• Confusing themes with feature plugins
• Thinking database adds features

4. A WordPress site is not showing theme changes after updating the theme files. What is the most likely cause?

medium

A. Browser cache is showing old styles

B. The database is corrupted

C. The plugin is disabling theme updates

D. WordPress core files are missing

Solution

1. Step 1: Analyze why theme changes don't appear

   Often, browsers keep old styles in cache, so updates don't show immediately.

2. Step 2: Eliminate other causes

   Database corruption or missing core files cause bigger errors; plugins rarely block theme updates silently.

3. Final Answer:

   Browser cache is showing old styles -> Option A

4. Quick Check:

   Cache blocks updates visibility [OK]

Hint: Clear browser cache to see theme updates [OK]

Common Mistakes:

• Blaming database for display issues
• Assuming plugins block theme updates
• Thinking core files cause style problems

5. You want to create a WordPress site that can easily switch between different looks without losing content. Which architecture feature supports this best?

hard

A. Editing core WordPress files directly

B. Separating content storage in the database from themes

C. Installing multiple plugins for content editing

D. Using a single theme with hardcoded content

Solution

1. Step 1: Understand content and design separation

   WordPress stores content in the database separately from themes, allowing theme changes without content loss.

2. Step 2: Evaluate options for flexibility

   Installing plugins or editing core files doesn't ensure easy look changes; hardcoded content limits flexibility.

3. Final Answer:

   Separating content storage in the database from themes -> Option B

4. Quick Check:

   Content-theme separation enables easy look changes [OK]

Hint: Content and design are separate in WordPress [OK]

Common Mistakes:

• Editing core files instead of using themes
• Hardcoding content in themes
• Relying only on plugins for design changes