Reading and writing settings in Wordpress - Step-by-Step Execution

Concept Flow - Reading and writing settings

Start

↓

Call get_option('setting_name')

↓

Retrieve value from DB

↓

Use value in code

↓

Call update_option('setting_name', new_value)

↓

Save new_value to DB

↓

Confirm save success

↓

End

This flow shows how WordPress reads a setting from the database using get_option, uses it, then writes a new value back with update_option.

Execution Sample

Wordpress

<?php
$value = get_option('my_setting');
if ($value === false) {
  update_option('my_setting', 'default');
}
?>

This code reads a setting 'my_setting', and if it doesn't exist, writes a default value.

Execution Table

Step	Function Called	Input	Action	Output/Result
1	get_option	'my_setting'	Look for 'my_setting' in DB	Returns false (not found)
2	Condition	if ($value === false)	Check if value exists	True, value missing
3	update_option	'my_setting', 'default'	Save 'default' to DB under 'my_setting'	Returns TRUE (success)
4	End	-	Setting now saved	-

💡 Setting 'my_setting' was missing, so default value was saved and process ends.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
$value	undefined	false	false	false	false

Key Moments - 2 Insights

Why does get_option return false sometimes?

Because the setting does not exist yet in the database, as shown in execution_table step 1.

What happens if update_option is called with a new setting?

It creates the setting in the database with the given value, as shown in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of $value after step 1?

A TRUE

B false

C 'default'

D Undefined

💡 Hint

Check the 'Output/Result' column in step 1 of the execution_table.

At which step does the setting get saved to the database?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look for update_option calls in the execution_table.

If get_option returned a value instead of false, what would happen?

A The condition would be false and update_option would not run

B update_option would still run

C The code would error out

D The value would be deleted

💡 Hint

Check the condition check in step 2 of the execution_table.

Concept Snapshot

Reading and writing settings in WordPress:
- Use get_option('name') to read a setting.
- Returns false if setting missing.
- Use update_option('name', value) to save or update.
- update_option creates setting if missing.
- Always check get_option result before update.

Full Transcript

This visual execution shows how WordPress reads and writes settings using get_option and update_option. First, get_option tries to find the setting in the database. If it returns false, it means the setting does not exist yet. Then, update_option is called to save a default value. This creates the setting in the database. The variable $value starts undefined, becomes false after get_option, and remains false since update_option does not change it directly. Understanding this flow helps beginners manage WordPress settings safely.