This page explains how to update eZ Platform to a new version.

In the instructions below, replace <version> with the version of eZ Platform you are updating to (for example: v1.7.0). If you are testing a release candidate, use the latest rc tag (for example: v1.7.1-rc1).

Version-specific steps

Update procedure

1. Check out a version

1.1. From the project's root, create a new branch from the project's master, or from the branch you're updating on:

git checkout -b <branch_name>

This creates a new project branch for the update based on your current project branch, typically master. An example <branch_name> would be update-1.4.

1.2. If it's not there, add ezsystems/ezplatform (or ezsystems/ezstudio, when updating an Enterprise installation) as an upstream remote:

git remote add ezplatform http://github.com/ezsystems/ezplatform.git
or
git remote add ezstudio http://github.com/ezsystems/ezstudio.git

1.3. Then pull the tag into your branch.

git pull ezplatform <version>
or
git pull ezstudio <version>

At this stage you may get conflicts, which are a normal part of the procedure and no reason to worry. The most common ones will be on composer.json and composer.lock.

The latter can be ignored, as it will be regenerated when we execute composer update later. The easiest is to checkout the version from the tag and add it to the changes:

git checkout --theirs composer.lock && git add composer.lock

If you do not keep a copy in the branch, you may also run:

git rm composer.lock

2. Merge composer.json

Manual merging

Conflicts in composer.json need to be fixed manually. If you're not familiar with the diff output, you may checkout the tag's version and inspect the changes. It should be readable for most:

git checkout --theirs composer.json && git diff HEAD composer.json

You should see what was changed, as compared to your own version, in the diff output. The update changes the requirements for all of the ezsystems/ packages. Those changes should be left untouched. All of the other changes will be removals of what you added for your own project. Use git checkout -p to selectively cancel those changes:

git checkout -p composer.json

Answer no (do not discard) to the requirement changes of ezsystems dependencies. Answer yes (discard) to removals of your changes.

Once you are done, inspect the file, either using an editor or by running git diff composer.json. You may also test the file's sanity with composer validate, and test the dependencies by running composer update --dry-run. (will output what it would do to dependencies, without applying the changes.

Once finished, run git add composer.json and commit.

Fixing other conflicts (if any)

Depending on the local changes you have done, you may get other conflicts on configuration files, kernel, etc.

There shouldn't be many, and you should be able to figure out which value is the right one for all of them:

• Edit the file, and identify the conflicting changes. If a setting you have modified has also been changed by us, you should be able to figure out which value is the right one.
• Run git add conflicting-file to add the changes

3. Update the app

At this point, you should have a composer.json file with the correct requirements. Run composer update to update the dependencies. 

composer update

4. Update database

This step is only relevant for some releases:

mysql -p -u <database_user> <database_name> < vendor/ezsystems/ezstudio-form-builder/bundle/Resources/install/form_builder.sql

mysql -p -u <database_user> <database_name> < vendor/ezsystems/date-based-publisher/bundle/Resources/install/datebasedpublisher_scheduled_version.sql

crontab -e

* * * * *   (cd /path/to/your/ezstudio-project && app/console ezpublish:cron:run -e=prod)

* * * * *   (cd /path/to/your/ezstudio-project && app/console ezpublish:cron:run -e=dev)

5. Dump assets

The web assets must be dumped again if you are using the prod environment. In dev this happens automatically:

php app/console assetic:dump -e=prod

If you encounter problems, additionally clear the cache and install assets:

php app/console cache:clear -e=prod
php app/console assets:install --symlink -e=prod
php app/console assetic:dump -e=prod

6. Commit, test and merge

Once all the conflicts have been resolved, and composer.lock updated, the merge can be committed. Note that you may or may not keep composer.lock, depending on your version management workflow. If you do not wish to keep it, run git reset HEAD <file> to remove it from the changes. Run git commit, and adapt the message if necessary. You can now verify the project and once the update has been approved, go back to master, and merge your update branch:

git checkout master
git merge <branch_name>

Your eZ Platform should now be up-to-date with the chosen version!