Block attributes and controls in Wordpress - Step-by-Step Execution

Concept Flow - Block attributes and controls

Define block attributes

↓

Render block editor UI

↓

User changes control input

↓

Update attribute value

↓

Re-render block with new attribute

↓

Save block content with attributes

This flow shows how block attributes are defined, controlled by UI inputs, updated on user interaction, and saved with the block.

Execution Sample

Wordpress

registerBlockType('my/block', {
  attributes: { content: { type: 'string' } },
  edit({ attributes, setAttributes }) {
    return <input value={attributes.content} onChange={e => setAttributes({ content: e.target.value })} />;
  },
  save({ attributes }) {
    return <p>{attributes.content}</p>;
  }
});

This code registers a block with a string attribute 'content' controlled by an input field in the editor.

Execution Table

Step	Action	Attribute 'content' Value	UI Control Value	Rendered Output
1	Block loads with default attribute	'' (empty string)	'' (empty input)	<input value=''>
2	User types 'Hello'	'Hello'	'Hello'	<input value='Hello'>
3	Block re-renders with updated attribute	'Hello'	'Hello'	<input value='Hello'>
4	User changes input to 'Hello World'	'Hello World'	'Hello World'	<input value='Hello World'>
5	Block re-renders with new attribute	'Hello World'	'Hello World'	<input value='Hello World'>
6	Block saved with attribute 'Hello World'	'Hello World'	N/A	<p>Hello World</p>

💡 User finishes editing; block saves content attribute as 'Hello World'.

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
attributes.content	''	'Hello'	'Hello World'	'Hello World'
UI input value	''	'Hello'	'Hello World'	N/A (saved)

Key Moments - 2 Insights

Why does the input field show the updated text immediately after typing?

Because the onChange event calls setAttributes to update the attribute, triggering a re-render with the new value as shown in steps 2 and 3 of the execution table.

What happens if you don't update the attribute on input change?

The input would not reflect user typing changes because the attribute value stays the same, so the block won't re-render with new content. See step 1 vs step 2 for contrast.

Visual Quiz - 3 Questions

Look at the execution table, what is the attribute 'content' value after step 4?

A 'Hello World'

B 'Hello'

C '' (empty string)

D N/A

💡 Hint

Check the 'Attribute content Value' column at step 4 in the execution table.

At which step does the block save the content attribute?

A Step 3

B Step 2

C Step 6

D Step 5

💡 Hint

Look for the row mentioning 'Block saved' in the execution table.

If the onChange handler did not call setAttributes, how would the UI control value change after typing?

A It would stay empty

B It would show previous attribute value

C It would update normally

D It would cause an error

💡 Hint

Refer to the key moment about attribute update and UI reflection.

Concept Snapshot

Block attributes hold data for blocks.
Controls let users change attributes.
Changing controls updates attributes.
Attributes update triggers re-render.
Saved content uses attribute values.

Full Transcript

In WordPress block development, blocks have attributes that store data. Controls in the editor let users change these attributes. When a user types in a control like an input box, the onChange event updates the attribute using setAttributes. This triggers the block to re-render with the new attribute value, so the UI stays in sync. Finally, when saving, the block outputs content based on the attribute values. This flow ensures user input is captured and saved correctly.

Practice

1. What is the main purpose of block attributes in WordPress block development?

easy

A. To store data or settings related to the block

B. To style the block with CSS

C. To add animations to the block

D. To create new blocks automatically

Solution

1. Step 1: Understand block attributes role

   Block attributes hold the data or settings that define how a block behaves or looks. Differentiate from styling or automation: Attributes are not for styling or creating blocks automatically but for storing block-specific data.

2. Final Answer:

   To store data or settings related to the block -> Option A

3. Quick Check:

   Block attributes = store data/settings [OK]

Hint: Attributes hold block data/settings, not styles or animations [OK]

Common Mistakes:

• Confusing attributes with CSS styling
• Thinking attributes create blocks automatically
• Assuming attributes control animations directly

2. Which of the following is the correct way to define a block attribute named title of type string in a block's attributes object?

easy

A. "title": { type: String }

B. "title": "string"

C. "title": { value: "string" }

D. "title": { type: "string" }

Solution

1. Step 1: Recall attribute syntax in block.json or registerBlockType

   Attributes are defined as objects with a type property as a lowercase string. Compare options: \"title\": { type: \"string\" } uses { type: \"string\" } which is correct. \"title\": { type: String } uses String (capitalized) which is invalid.

2. Final Answer:

   \"title\": { type: \"string\" } -> Option D

3. Quick Check:

   Attribute type uses lowercase string \"string\" [OK]

Hint: Use { type: \"string\" } with lowercase type name [OK]

Common Mistakes:

• Using capitalized String instead of \"string\"
• Assigning attribute directly to a string
• Using incorrect property like value instead of type

3. Given this block attribute and control code snippet:

const [content, setContent] = useState('Hello');

return (
   setContent(value)}
  />
);

What will happen when the user types "World" into the TextControl?

medium

A. An error occurs because useState is not allowed in blocks

B. The content state updates to "World" and the TextControl shows "World"

C. The content state remains "Hello" and TextControl does not change

D. The TextControl clears and shows an empty string

Solution

1. Step 1: Understand useState and TextControl interaction

   The useState hook holds the current content. The TextControl shows this content and updates it on user input. Follow the onChange handler: When user types \"World\", onChange calls setContent(\"World\"), updating the state and re-rendering the control with new value.

2. Final Answer:

   The content state updates to "World" and the TextControl shows "World" -> Option B

3. Quick Check:

   Typing updates state and control value [OK]

Hint: State updates on change, control reflects new value [OK]

Common Mistakes:

• Thinking state won't update without explicit save
• Believing useState is disallowed in block edit
• Assuming control clears on input

4. Consider this block attribute definition:

attributes: {
  count: { type: 'number', default: 0 }
}

And this control code:

 setAttributes({ count: value })}
/>

What is the likely cause if the control does not update the count attribute correctly when typing?

medium

A. The value prop should be a number, but onChange passes a string

B. The attribute type should be "string" instead of "number"

C. The default value must be set inside setAttributes

D. The control component NumberControl does not exist in WordPress

Solution

1. Step 1: Check data types between attribute and control

   The attribute expects a number, but onChange often passes a string from input controls. Identify mismatch causing update failure: Passing a string instead of a number causes the attribute not to update properly because types differ.

2. Final Answer:

   The value prop should be a number, but onChange passes a string -> Option A

3. Quick Check:

   Type mismatch: onChange passes string to number attribute [OK]

Hint: Ensure onChange passes correct type matching attribute [OK]

Common Mistakes:

• Ignoring type conversion from string to number
• Changing attribute type unnecessarily
• Assuming default value fixes runtime type issues

5. You want to create a block with a toggle control that updates a boolean attribute isActive. Which code snippet correctly defines the attribute and control to toggle this value?

hard

A. attributes: { isActive: { type: 'boolean' } }

setAttributes({ isActive: !attributes.isActive })}
/>

B. attributes: { isActive: { type: 'string', default: 'false' } }

setAttributes({ isActive: value })}
/>

C. attributes: { isActive: { type: 'boolean', default: false } }

setAttributes({ isActive: value })}
/>

D. attributes: { isActive: { type: 'boolean', default: true } }

setAttributes({ isActive: !value })}
/>

Solution

1. Step 1: Define boolean attribute with default false

   attributes: { isActive: { type: 'boolean', default: false } }
   
    setAttributes({ isActive: value })}
   />

   correctly defines isActive as boolean with default false, which is standard for toggles. Use ToggleControl with checked and onChange: The checked prop uses the attribute value, and onChange updates the attribute with the new boolean value passed by the toggle.

2. Final Answer:

   { isActive: { type: 'boolean', default: false } }, ToggleControl checked={attributes.isActive} onChange={(value) => setAttributes({ isActive: value })} -> Option C

3. Quick Check:

   Boolean attribute with checked and direct onChange update [OK]

Hint: Use checked prop and boolean attribute with default false [OK]

Common Mistakes:

• Using string type for boolean attribute
• Using value instead of checked prop
• Inverting value incorrectly in onChange