Training mode
Time remaining:
0 / 50 answered
Separate presentation responsibilities from reusable site functionality.
Place the concept in the WordPress request, content, or permission model.
Identify the data-model or security responsibility before choosing the API.
Choose the conventional WordPress lifecycle hook.
It is the same common lifecycle point used for CPT registration.
There is a dedicated filter for the generated class list.
Identify the WordPress API responsibility before considering implementation details.
Consider lifecycle, authorization, failure and long-term maintenance.
Administrators need a recoverable state.
Intent and permission are separate questions.
Think schema and access rules.
The registered post type slug is book.
book
The template hierarchy includes the post type slug.
A child functions.php does not replace its parent counterpart.
Select all generally appropriate safeguards.
Consider request intent, autosaves, and authorization.
Choose the statement that correctly describes the contract expected by WordPress.
Ask yourself whether the received value must continue through the execution chain.
Identify the role of the WordPress function or extension point.
It is an allow-list HTML filter.
The query contains values supplied at runtime.
Do not concatenate untrusted values into the SQL string.
It is late in the request.
The query contains more than one metadata condition.
Think of boolean logic between clauses.
The server must enforce authorization before the main callback.
Registration and flushing are different operations.