Message-ID: <1115352344.2792.1485850813827.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2791_1977154831.1485850813826" ------=_Part_2791_1977154831.1485850813826 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Migrating legacy Page field (ezflow) to Landing Page (Enterprise= )

Migrating legacy Page field (ezflow) to Landing Page (Enterprise)
=20
=20
=20
=20

To move your legacy Page field / eZ Flow configuration to eZ Platform En= terprise Edition you can use a script that will aid in the migration proces= s.

The script will automatically migrate only data =E2=80=93 to move c= ustom views, layouts, blocks etc., you will have to provide their business = logic again.

The migration script will operate on your current database.

Make sure to back up your database in case of an unexpe= cted error.

 

To use the script, do the following:

Make a note of the paths to .ini files which define your legacy blocks. You= will need these paths later.

1. Add ezflow-migration-toolkit to c= omposer.json in your clean Platform installation.

composer.json
=20
"ezsystems/ezflow-migration-toolkit": "^1.0.0"
=20

2. Add ezflow-migration-toolkit to A= ppKernel.php.

AppKernel.php
=20
new EzSystems\EzFlowMigrationToolkitBundle\EzSystemsEzFlowMigration=
ToolkitBundle()
=20

3. Clear cache.

=20
app/console cache:clear
=20

4. Run the script with the following parameters:

  • absolute path of your legacy application
  • list of .ini files which define your legacy blocks
Script command
=20
app/console ezflow:migrate <legacy path> =E2=80=94ini=3D<b=
lock definitions> [=E2=80=94ini=3D<another block definition> ...]<=
/pre>=20
Example of the migration script command
=20
app/console ezflow:migrate /var/www/legacy.application.com/ =E2=80=
=94ini=3Dextension/myapplication/settings/block.ini.append.php
=20

5. You will be warned about the need to create a backup= of your database. Proceed only if you are sure you have done it.

A MigrationBundle will be generated in the src/ folder.

You will see a report summarizing the results of the migration.

6. Add MigrationBundle to AppKernel.= php.

AppKernel.php
=20
new MigrationBundle\MigrationBundle()
=20

7. Clear cache again.

 

At this point you can already view the initial effects of the migration,= but they will still be missing some of your custom content.

The MigrationBundle generates placeholders for layouts in t= he form of frames with a data dump.

For blocks that could not be mapped to existing Landing Page blocks, it = will also generate PHP file templates that you need to fill with your own b= usiness logic.

 

=20
=20
=20
=20

 

=20
=20
=20
------=_Part_2791_1977154831.1485850813826--