Plugin file structure in Wordpress - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the main plugin file in a WordPress plugin structure

Given a WordPress plugin folder with these files:

- my-plugin.php
- readme.txt
- includes/functions.php
- assets/style.css

Which file is the main plugin file that WordPress uses to activate the plugin?

A includes/functions.php

B readme.txt

C my-plugin.php

D assets/style.css

💡 Hint

The main plugin file is the one that contains the plugin header comment and is directly inside the plugin folder.

The main plugin file is the PHP file located directly inside the plugin folder that contains the plugin header comment. WordPress uses this file to recognize and activate the plugin.

❓ component_behavior

intermediate

What happens if the main plugin file is missing?

If a WordPress plugin folder does not contain a main PHP file with the plugin header, what will WordPress do when you try to activate it?

A WordPress will not list the plugin in the admin plugins page.

B WordPress will activate the plugin but show a warning.

C WordPress will activate the plugin without any issues.

D WordPress will delete the plugin folder automatically.

💡 Hint

WordPress needs the main plugin file to recognize a plugin.

Without a main plugin file containing the plugin header, WordPress does not recognize the folder as a plugin and will not list it on the plugins page.

📝 Syntax

advanced

Identify the correct plugin header format

Which of the following plugin header comments is correctly formatted for WordPress to recognize the plugin?

A

<?php
/*
Plugin-Name: My Plugin
Description: Does something useful.
Version: 1.0
*/

B

<?php
/*
Plugin Name: My Plugin
Description: Does something useful.
Version: 1.0
*/

C

<?php
// Plugin Name: My Plugin
// Description: Does something useful.
// Version: 1.0

D

<?php
/*
Plugin Name My Plugin
Description: Does something useful.
Version: 1.0
*/

💡 Hint

The plugin header must be inside a block comment with exact field names.

The plugin header must be inside a block comment /* ... */ with exact field names like Plugin Name. Option B follows this format correctly.

🔧 Debug

advanced

Why does the plugin not load the included PHP file?

A plugin has this structure:

- my-plugin.php
- includes/functions.php

Inside my-plugin.php there is this code:

include 'includes/functions.php';

But when activating the plugin, functions from functions.php are not available. What is the likely cause?

A The include path is relative to the current working directory, not the plugin file, so it fails.

B The functions.php file has a syntax error preventing it from loading.

C The include statement should use require_once instead of include.

D The plugin header is missing in functions.php.

💡 Hint

Relative paths in PHP includes depend on the current working directory, not the file location.

PHP includes use paths relative to the current working directory, which may not be the plugin file's folder. Using a relative path without adjusting for this causes the include to fail silently.

❓ state_output

expert

What is the output of the plugin activation hook?

Consider this plugin main file code:

/*
Plugin Name: Test Plugin
*/

register_activation_hook(__FILE__, function() {
  update_option('test_plugin_activated', time());
});

add_action('admin_notices', function() {
  if ($time = get_option('test_plugin_activated')) {
    echo '<div class="notice notice-success">Plugin activated at: ' . date('H:i:s', $time) . '</div>';
    delete_option('test_plugin_activated');
  }
});

What will the admin see immediately after activating this plugin?

A A blank page because the plugin exits after activation.

B No notice because the option is deleted before admin_notices runs.

C An error because update_option cannot be called in activation hook.

D A success notice showing the exact time of activation in H:i:s format.

💡 Hint

The activation hook sets an option with the current time, which is then read and shown in the admin notices.

The activation hook stores the current time in an option. The admin_notices action reads this option and shows a success message with the activation time, then deletes the option so the notice only shows once.