A blank title column in the WordPress 7.2 Site Editor does not by itself prove page titles were erased. The editor needs both content and field definitions to render a view. Check the underlying page title and the entity-field response before renaming pages, restoring a database or running a content migration.
This is a staging diagnostic for WordPress 7.2 beta, checked October 28, 2026. Beta 2 is available for testing. Record the precise build because the entity APIs are still receiving fixes.
Establish whether the data still exists
Pick one synthetic page with a distinctive title and record its ID. Compare the title in the affected Site Editor list, a separate authorized editing view and the normal content response your integration already uses. Do not treat the public theme's heading as the only source of truth; a template can replace it.
If the stored title is missing too, investigate the save or import operation. If the title exists outside the new view, focus on field registration and rendering. This distinction prevents a presentation problem from becoming a destructive data repair.
The entity-fields ticket records a real development-stage case where core field registration was missing and the Site Editor's page-title column appeared blank. Later changes register the core fields and address preload and module edge cases. An older alpha symptom should not automatically be attributed to the current beta.
Inspect the request your editor actually makes
Open the browser's Network panel while loading the affected view. Locate its entity-fields request or preloaded response. Use the route and parameters observed in your build; do not copy an early proposal's endpoint from an old discussion.
Record status, content type, entity identity and whether the title field definition is present. A 200 response with an empty field collection differs from an authorization failure or HTML returned in place of JSON.
| Evidence |
Investigate next |
| Content title present, field missing |
Server registration and filtering |
| Field present, module fails |
Script delivery and module registration |
| HTML instead of expected JSON |
Authentication redirect, WAF or route handling |
| Only custom entity affected |
Its supports and custom field registration |
| Stored title also missing |
Save/import history, not just rendering |
Trace content, field definitions and rendering separately before treating a blank column as data loss.
Compare a core page with the custom entity
Use a standard page as a control, then the custom post type or entity that fails. If the control works, document the registration differences rather than disabling every editor feature. Check the field ID, entity identity and any plugin filtering field definitions.
Inspect the console for the first module-loading error. A failed dependency can produce several later rendering errors. Check the failed asset's HTTP response and type before changing field definitions. A missing script served as an HTML fallback will not become executable by clearing a local preference.
If the failure began with a custom preload filter, verify its returned value and context expectations. Preserve a minimal reproduction. Do not invoke private core preload helpers directly in a production workaround; their implementation can change.
Retest with a controlled plugin comparison
On an isolated copy, compare the exact beta with and without the plugin that registers or filters the affected fields. Keep content and user identity fixed. Record whether the response changes and whether the displayed cell follows it.
For a problem confined to a grouped form's summary or validation, use the DataForm combined-fields guide. That is a narrower layout contract than a missing server field collection.
Preserve proof that content was not changed
Save before-and-after content values, field IDs, request status and the module error, with personal information removed. Acceptance means the title renders correctly and the stored title remains unchanged. It does not require a mass content rewrite.
Repeat after the next approved build and include the precise version in the handoff. For a custom entity whose field definitions never reach the editor, request a focused WordPress editor repair with the control page and minimal registration example.
Sources checked October 28, 2026. Synthetic fixtures and diagrams illustrate the proposed checks; they are not claims of customer testing.
For an action menu that renders but does not execute, trace the separate action-module contract: WordPress 7.2 Entity Actions: A Menu Item Appears but Does Nothing.