Why proper configuration matters in Wordpress - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the WordPress site URL correctly.

Wordpress

define('WP_HOME', '[1]');

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

A'index.php'

B'wp-admin'

C'wp-config.php'

D'https://example.com'

Attempts:

3 left

💡 Hint

Common Mistakes

Using file names instead of the site URL.

Leaving the URL empty or incorrect.

Setting WP_HOME defines the main URL of your WordPress site, which is essential for proper site loading.

2fill in blank

medium

Complete the code to set the WordPress database name in the configuration.

Wordpress

define('DB_NAME', '[1]');

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

A'wordpress_db'

B'wp-content'

C'wp-config.php'

D'localhost'

Attempts:

3 left

💡 Hint

Common Mistakes

Using folder names like 'wp-content' instead of the database name.

Using server names like 'localhost' here.

The DB_NAME constant tells WordPress which database to use. It must match your actual database name.

3fill in blank

hard

Fix the error in the code to properly set the WordPress debug mode.

Wordpress

define('WP_DEBUG', [1]);

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

A'false'

B'true'

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Putting quotes around true or false.

Using strings instead of booleans.

The WP_DEBUG constant expects a boolean value without quotes. Using quotes makes it a string, which is incorrect.

4fill in blank

hard

Fill both blanks to correctly set the WordPress database user and password.

Wordpress

define('DB_USER', '[1]');
define('DB_PASSWORD', '[2]');

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

A'admin_user'

B'admin_pass123'

C'root'

D'password'

Attempts:

3 left

💡 Hint

Common Mistakes

Using default or empty passwords.

Mixing up user and password values.

DB_USER and DB_PASSWORD must match your database login credentials for WordPress to connect properly.

5fill in blank

hard

Fill all three blanks to set the WordPress site URL, content directory, and enable debugging.

Wordpress

define('WP_HOME', '[1]');
define('WP_CONTENT_DIR', '[2]');
define('WP_DEBUG', [3]);

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

A'https://mywebsite.com'

B'/var/www/html/wp-content'

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using relative paths for content directory.

Putting quotes around boolean values.

Incorrect site URL format.

These settings define the site URL, the location of the content folder, and enable debugging mode for development.

Practice

1. Why is it important to properly configure the wp-config.php file in WordPress?

easy

A. It manages user comments and spam filtering automatically.

B. It controls the theme colors and fonts for the website.

C. It sets up database connection and security keys essential for site operation.

D. It schedules posts to be published at specific times.

Solution

1. Step 1: Understand the role of wp-config.php

   This file contains important settings like database connection details and security keys that keep the site running and safe.

2. Step 2: Identify what wp-config.php does not control

   Theme colors, fonts, comments, and post scheduling are managed elsewhere, not in this file.

3. Final Answer:

   It sets up database connection and security keys essential for site operation. -> Option C

4. Quick Check:

   wp-config.php = database & security setup [OK]

Hint: Remember: wp-config.php handles core setup, not design [OK]

Common Mistakes:

• Thinking wp-config.php controls site appearance
• Confusing plugin settings with core configuration
• Assuming it manages content scheduling

2. Which of the following is the correct way to define the database name in wp-config.php?

easy

A. set('DB_NAME', 'my_database');

B. config('DB_NAME', 'my_database');

C. db_name = 'my_database';

D. define('DB_NAME', 'my_database');

Solution

1. Step 1: Recall PHP constant definition syntax

   In wp-config.php, constants like DB_NAME are set using the define() function.

2. Step 2: Check each option's syntax

   Only define('DB_NAME', 'my_database'); uses the correct PHP syntax for defining a constant.

3. Final Answer:

   define('DB_NAME', 'my_database'); -> Option D

4. Quick Check:

   Use define() for constants in wp-config.php [OK]

Hint: Use define() to set constants in PHP config files [OK]

Common Mistakes:

• Using assignment (=) instead of define()
• Using non-PHP functions like set() or config()
• Missing quotes around constant name or value

3. Given this snippet in wp-config.php:

define('WP_DEBUG', true);
if (WP_DEBUG) {
  error_reporting(E_ALL);
  ini_set('display_errors', 1);
}

What will happen when you visit the WordPress site?

medium

A. All PHP errors and warnings will be shown on the site.

B. No errors will be shown, site runs silently.

C. Only fatal errors will be logged but not displayed.

D. The site will automatically fix errors.

Solution

1. Step 1: Understand WP_DEBUG setting

   Setting WP_DEBUG to true enables debugging mode in WordPress.

2. Step 2: Analyze error reporting code

   The code sets PHP to report all errors and display them on the site.

3. Final Answer:

   All PHP errors and warnings will be shown on the site. -> Option A

4. Quick Check:

   WP_DEBUG = true shows all errors [OK]

Hint: true WP_DEBUG shows all errors on site [OK]

Common Mistakes:

• Thinking errors are hidden when WP_DEBUG is true
• Assuming errors are fixed automatically
• Confusing error logging with error displaying

4. You added this line to wp-config.php but your site shows a blank page:

define('WP_DEBUG', 'true');

What is the likely problem?

medium

A. WP_DEBUG should be a boolean true, not a string 'true'.

B. The line must be placed after the closing PHP tag.

C. You need to restart the server for changes to apply.

D. WP_DEBUG is not a valid constant in WordPress.

Solution

1. Step 1: Check the data type of WP_DEBUG value

   WP_DEBUG expects a boolean true or false, not a string.

2. Step 2: Understand impact of wrong type

   Using a string can cause PHP to misinterpret the value, leading to errors and blank pages.

3. Final Answer:

   WP_DEBUG should be a boolean true, not a string 'true'. -> Option A

4. Quick Check:

   Use boolean true, not 'true' string for WP_DEBUG [OK]

Hint: Use true without quotes for booleans in config [OK]

Common Mistakes:

• Putting config lines after PHP closing tag
• Thinking server restart is needed for PHP changes
• Believing WP_DEBUG is invalid constant

5. You want to improve your WordPress site's security by adding unique authentication keys in wp-config.php. Which approach is best?

hard

A. Manually write simple words as keys to remember them easily.

B. Use the WordPress.org secret-key service to generate strong keys.

C. Leave keys empty to avoid configuration errors.

D. Copy keys from another site to save time.

Solution

1. Step 1: Understand the purpose of authentication keys

   These keys secure cookies and user sessions, so they must be strong and unique.

2. Step 2: Identify the best way to get strong keys

   WordPress.org provides a secret-key service that generates strong random keys automatically.

3. Step 3: Avoid weak or reused keys

   Simple words, empty keys, or copying keys from other sites weaken security and risk attacks.

4. Final Answer:

   Use the WordPress.org secret-key service to generate strong keys. -> Option B

5. Quick Check:

   Use official key generator for strong unique keys [OK]

Hint: Always use official key generator for security keys [OK]

Common Mistakes:

• Using easy-to-guess words as keys
• Leaving keys empty thinking it's safer
• Reusing keys from other sites