Plugin file structure in Wordpress - Step-by-Step Execution

Concept Flow - Plugin file structure

Create plugin folder

↓

Add main plugin file

↓

Add plugin header comment

↓

Add additional files (optional)

↓

Activate plugin in WordPress

↓

Plugin runs and hooks into WordPress

This flow shows how a WordPress plugin is structured starting from folder creation to activation and running inside WordPress.

Execution Sample

Wordpress

<?php
/*
Plugin Name: My Plugin
*/
// Plugin code here

This is the main plugin file with the required header comment that WordPress reads to identify the plugin.

Execution Table

Step	Action	File/Folder Created	Content Summary	WordPress Reaction
1	Create plugin folder	my-plugin/	Empty folder to hold plugin files	Recognizes folder as plugin container
2	Add main plugin file	my-plugin/my-plugin.php	PHP file	Recognizes main plugin file
3	Add plugin header comment	my-plugin/my-plugin.php	Contains Plugin Name and info	Plugin appears in admin plugins list
4	Add additional files	my-plugin/includes/functions.php	Optional PHP files for organization	Files loaded by main plugin file if included
5	Activate plugin	WordPress admin	User activates plugin in dashboard	Plugin code runs and hooks into WordPress
6	Plugin runs	N/A	Hooks and functions execute	Plugin functionality is available on site

💡 Plugin is fully loaded and active after activation step

Variable Tracker

Variable/File	Start	After Step 2	After Step 4	After Activation
Plugin folder	Not created	Created	Exists	Exists
Main plugin file	Not created	Created	Exists with header	Exists and loaded
Additional files	None	None	Added	Loaded if included
Plugin active state	Inactive	Inactive	Inactive	Active

Key Moments - 3 Insights

Why is the plugin header comment important?

WordPress reads the header comment in the main plugin file to identify the plugin and show it in the admin list. Without it, WordPress ignores the plugin folder (see execution_table step 3).

Can a plugin have multiple PHP files?

Yes, additional PHP files can be added for better organization, but the main plugin file must include or require them to run (see execution_table step 4).

What happens if the plugin is not activated?

The plugin files exist but WordPress does not run the plugin code or hooks until the user activates it in the admin dashboard (see execution_table step 5).

Visual Quiz - 3 Questions

Look at the execution table, at which step does WordPress recognize the plugin metadata?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'WordPress Reaction' column for when the plugin appears in the admin list.

According to the variable tracker, when does the plugin become active?

A After Step 2

B After Step 4

C After Activation

D At Start

💡 Hint

Look at the 'Plugin active state' row in the variable tracker.

If you add a new PHP file but do not include it in the main plugin file, what happens?

A The file is ignored and code inside does not run

B WordPress loads it automatically

C Plugin fails to activate

D Plugin header comment is ignored

💡 Hint

Refer to key moment about additional files and execution_table step 4.

Concept Snapshot

WordPress Plugin File Structure:
- Create a plugin folder inside wp-content/plugins
- Add a main PHP file with a plugin header comment
- Optionally add more PHP files for organization
- Activate plugin in WordPress admin
- Plugin code runs and hooks into WordPress
Header comment is required for WordPress to detect the plugin.

Full Transcript

A WordPress plugin starts as a folder inside the plugins directory. Inside this folder, you create a main PHP file that must include a special header comment with the plugin name and info. This header allows WordPress to recognize and list the plugin in the admin dashboard. You can add more PHP files for organizing your code, but these must be included by the main plugin file to run. The plugin remains inactive until you activate it in the WordPress admin. Once activated, WordPress runs the plugin code and hooks, making the plugin's features available on the site.