Settings API in Wordpress - Step-by-Step Execution

Concept Flow - Settings API

Start Plugin Initialization

↓

Register Setting

↓

Add Settings Section

↓

Add Settings Fields

↓

Render Settings Page

↓

User Submits Form

↓

Validate & Save Data

↓

Display Updated Settings

↓

End

This flow shows how WordPress Settings API registers settings, adds sections and fields, renders the page, and saves user input.

Execution Sample

Wordpress

<?php
add_action('admin_init', function() {
  register_setting('my_option_group', 'my_option_name');
  add_settings_section('my_section', 'My Section', null, 'my_page');
  add_settings_field('my_field', 'My Field', function() {
    $val = get_option('my_option_name');
    echo "<input type='text' name='my_option_name' value='" . esc_attr($val) . "' />";
  }, 'my_page', 'my_section');
});

Registers a setting, adds a section and a field with an input box on a settings page.

Execution Table

Step	Action	Function Called	Effect	State Change
1	Plugin loads and hooks admin_init	add_action('admin_init', callback)	Callback registered for admin_init	Callback ready
2	admin_init fires	register_setting('my_option_group', 'my_option_name')	Setting registered	Setting 'my_option_name' registered
3	Add settings section	add_settings_section('my_section', 'My Section', null, 'my_page')	Section added to 'my_page'	Section 'my_section' added
4	Add settings field	add_settings_field('my_field', 'My Field', callback, 'my_page', 'my_section')	Field added to section	Field 'my_field' added
5	Render settings page	do_settings_sections('my_page')	Section and field output HTML	Settings page ready
6	User submits form	submit POST data	Data sent to server	Form data received
7	Validate and save	register_setting validation callback (if any)	Data validated and saved	Option 'my_option_name' updated
8	Display updated settings	get_option('my_option_name')	Input field shows saved value	Settings page updated
9	End	-	No further action	Stable state

💡 Process ends after settings page updates with saved data.

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 7	Final
my_option_name	undefined	registered (empty)	registered (empty)	saved user value	saved user value
my_section	undefined	undefined	added	added	added
my_field	undefined	undefined	added	added	added

Key Moments - 3 Insights

Why do we need to register a setting before adding fields?

Registering the setting (see Step 2) tells WordPress to accept and save the option. Without it, the field input won't be saved.

What happens if the validation callback rejects the input?

If validation fails during Step 7, the data is not saved and the old value remains. The user sees an error message.

Why do we add sections and fields separately?

Sections group fields logically on the page (Step 3), and fields belong inside sections (Step 4). This organizes the settings UI.

Visual Quiz - 3 Questions

Look at the execution table, what is the state of 'my_option_name' after Step 4?

A Undefined

B Registered but empty

C Saved user value

D Deleted

💡 Hint

Check the variable_tracker column 'After Step 4' for 'my_option_name'

At which step does the user input get saved?

A Step 7

B Step 5

C Step 3

D Step 2

💡 Hint

Look for 'Validate and save' action in the execution_table

If we skip add_settings_section, what changes in the execution?

A Settings page will not render at all

B Fields will be saved but not shown

C Settings page will have no sections but fields may still appear

D Validation will fail

💡 Hint

Refer to Step 3 and Step 4 in execution_table about sections and fields

Concept Snapshot

Settings API quick steps:
1. register_setting to declare option
2. add_settings_section to group fields
3. add_settings_field to add inputs
4. Render page with do_settings_sections
5. User submits form
6. WordPress validates and saves
Use callbacks for rendering and validation.

Full Transcript

The WordPress Settings API helps developers create settings pages easily. First, you register a setting to tell WordPress to accept and save it. Then, you add sections to organize fields on the page. Next, you add fields inside those sections with callbacks that output input elements. When the settings page renders, WordPress shows these inputs grouped by sections. When a user submits the form, WordPress validates the input and saves it to the database. The saved values then appear in the input fields on reload. This flow ensures settings are managed securely and cleanly.