Verified option record · updated 2026-08-25

default_category

Configuration

default_category is owned by WordPress Core in the tested WordPress 7.0–7.1 ConfigOps contract. The local category assigned when a post has no category; its term ID belongs to this website.

Tested owner
WordPress CoreTested ConfigOps adapter assignment
Version contract
WordPress 7.0–7.1Adapter schema 1
Stored shape
Scalar option value1 mapped field
ConfigOps recovery
Conditional UndoCurrent-state check required

Who writes default_category?

WordPress Core is the tested owner for default_category under the WordPress 7.0–7.1 ConfigOps adapter contract. This is a source-backed adapter claim, not a guess based on naming.

Component type
WordPress
Component entry point
wp-includes/version.php
Adapter ID
wordpress-core
Adapter schema
1
Visible setting
Settings → Writing
Classification
Configuration

Scalar option value.

Mapped paths1
Secret paths0
Field kinds1
Exact fields mapped by ConfigOps adapter schema 1
PathVisible meaningKindWhy it matters
/Default post categoryPublishing defaultsenvironmentThe local category assigned when a post has no category; its term ID belongs to this website.

What belongs beside the setting—but not inside the decision?

Core caches, update state, rewrite rules, cron, locks, and migration markers are treated as generated or technical state rather than user intent.

No option-specific neighboring value is asserted.

The adapter-wide technical boundary still applies; absence here is not proof that a save has no runtime side effects.

Known secret paths

No secret field is declared inside this exact option schema. ConfigOps still applies its conservative global secret detector.

Adapter-backed, not Smart Undo.

ConfigOps adapterYes · wordpress-core

Schema 1; tested against WordPress 7.0–7.1.

Adapter-aware UndoConditionally supported

Supported values can use adapter-aware, conflict-checked Undo when evidence is complete and the current value still matches.

Smart Undo eligibilityNo

No. Smart Undo is only for ordinary associative options that no adapter claims. This option is adapter-owned.

History boundary: ConfigOps records only saves it observes while active. It cannot tell you what changed this row before installation.

Inspect without writing.

Run these on the intended environment. The commands read current state; they do not reconstruct history.

Read the current value
wp option get default_category
Inspect matching storage and autoload metadata
wp option list --search=default_category --fields=option_name,autoload --format=table

No option-specific autopsy published yet.

Contract coverage is not a save autopsy.

The owner and field map are verified by the adapter source, but this Atlas record does not claim an option-specific browser or integration save trace.

Questions developers ask mid-incident.

What plugin writes default_category?

WordPress Core is the tested owner in the ConfigOps WordPress 7.0–7.1 adapter contract. The assignment is verified, not inferred from the option prefix.

What is stored in the default_category WordPress option?

Scalar option value. default_category contains 1 mapped field in this adapter schema.

Can ConfigOps track and undo changes to default_category?

ConfigOps can attribute and record supported Options API writes while active. Supported values can use adapter-aware, conflict-checked Undo when evidence is complete and the current value still matches. No. Smart Undo is only for ordinary associative options that no adapter claims. This option is adapter-owned.

Does WordPress keep a history of default_category?

WordPress normally exposes the current option value, not a universal before-and-after history. ConfigOps must observe the original save to create local evidence; it cannot reconstruct older changes retroactively.

Why this page exists.

This record was generated from pinned ConfigOps source commit e319f502ff677bd76e53b7034650f9ee2afead72. The exact option name passed the publication allowlist; arbitrary searches do not.