Doctrine Migration Rollback vs Content Versioning: Reverting a Sulu Content Type Schema Change

Question

In Sulu, changing a content type definition modifies both the persistent database schema and the content model, yet the platform provides two separate recovery mechanisms that operate at different layers. A Doctrine migration down-step can revert the physical schema, while Sulu's content staging feature restores prior content element states without altering table structures. The unresolved decision is which mechanism offers a safer rollback when a content type change has already been deployed and existing content references are present.
The core trade-off is that a Doctrine migration rollback may fail if foreign-key constraints or dependent content records prevent the down-step, whereas restoring a content version preserves the data but leaves the database schema potentially out of sync with the original content type definition. Neither approach automatically coordinates both the structural and content-model reversion.
Which documented rollback path minimizes the risk of data loss or schema inconsistency when reverting a content type change in a Sulu application? Does the content staging feature track schema-level metadata in a way that makes it suitable for structural rollback, or is it strictly limited to content state restoration? What verification is required to confirm that the database schema and content model are aligned after choosing either rollback strategy?

Tasadduq Burney · Answer

Answer at a glance
For a content‑type change that has already hit production, the Doctrine migration rollback followed by content staging is the safest documented path. Doctrine handles the physical schema, while content staging restores the element data. Neither feature alone guarantees full consistency, but together they cover both layers.
Why Doctrine migration is the first step

It rewrites the database tables to match the original schema.
It does not touch the content‑type definition stored in the registry.
Without it, the registry would describe a type that no longer exists in the database, leading to validation errors.

Why content staging alone is insufficient

It only reverts the state of content elements.
It never records or changes table structures.
After a schema rollback, any new fields that were added will still be present in the registry, causing mismatches when rendering pages.

Recommended two‑step rollback procedure

Rollback the migration

Run the down‑step that was generated when the schema change was first applied.
Verify that the migration table no longer lists the added columns.
Check for foreign‑key or data‑constraint failures; if any exist, resolve them manually before proceeding.

Revert content to a pre‑change snapshot

Use the Sulu admin UI or the sulu:content:restore command to bring each affected page back to a version created before the schema change.
Ensure that the restored content does not reference any fields that were removed.

Validate alignment

php bin/console doctrine:schema:validate – confirms that tables and columns match the current content‑type definitions.
php bin/console sulu:content:validate – ensures the registry and database are in sync.
Inspect a sample page in the admin UI to verify that all expected fields are present and correctly typed.

What verification steps are required?

Check the doctrine_migration_versions table to confirm the down migration has been applied.
Run php bin/console doctrine:schema:validate and look for any MissingColumn or MissingTable errors.
Execute php bin/console sulu:content:validate and resolve any registry‑schema mismatches.
Open the affected content in the admin UI and confirm that the UI fields match the restored data.

Missing diagnostic detail that could change the recommendation
Do you have any foreign‑key constraints or orphaned records that might block the down migration? If so, a manual data cleanup may be required before the rollback can succeed.
Key takeaway
Use the Doctrine migration rollback to restore the physical schema, then use content staging to revert the data. Validate both layers after each step to ensure the database and content‑type registry remain consistent.

Doctrine Migration Rollback vs Content Versioning: Reverting a Sulu Content Type Schema Change

1 answer

Answer at a glance

Why Doctrine migration is the first step

Why content staging alone is insufficient

Recommended two‑step rollback procedure

What verification steps are required?

Missing diagnostic detail that could change the recommendation

Key takeaway

Your perspective belongs here.

0 question comments