Below you will find cleanup commands from the EzPublishMigrationBundle for the most common issues that can occur after migration to eZ Platform.
Enabling EzPublishMigrationBundle bundle
To enable EzPublishMigrationBundle add the following to your
dev environment bundles in
Remember about proper backup before running any of the commands below.
Regenerating URL aliases¶
To regenerate URL aliases, use the
See Regenerating URL aliases for more information.
This command keeps history and replaces the old
legacy_storage_url_aliases is now deprecated.
Unknown relation type 0¶
"Unknown relation type 0." error occurs only when using REST API. The issue does not occur the first time article is published (upon creation). It only happens after the article is edited and published.
If this error occurs use the console command below. It will clean up redundant relations rows:
- list / dry-run - prints table with all corrupted relations that will be deleted (to be executed first)
- fix - executes clean up
You can read more about this issue here: EZP-27254
Always available flag set on all Fields¶
Always available flag is set on all Fields, instead of only on Fields in the main language. This problem occurs when eZ Platform is used to create Content that is both always available and has multiple translations. The cleanup script will correctly set always available flag for prioritized language filtering in Legacy Search Engine.
Only affected Fields will be processed by the cleanup command.
You can read more about this issue here: EZP-24882
Trouble listing sub content¶
It is possible that after upgrade
sort_key_string is left empty. This may cause problems
in searches throughout the API. The cleanup script will check if Fields of given Field
Type have correct sort key, and update it if needed.
Execute the following command from the installation root directory:
You can read more about this issue here: EZP-23924