The first sub-release of eZ Platform 15.12 is now available for update.

Changes since 15.12

For list of issues fixed in 15.12.1 see 13 issues , below is a list of notable bugs/features/enhancements done in the release. 

Distribution

• Improved Install doc and Apache/Nginx doc, added script to generate vhost for automation needs.
• PHP Internal web server "works", further fixes in 16.02 to make it tested and supported for dev use.
• Installers don't write to config anymore, only folders mentioned in directory permissions are written to.
• Info on where to find demo install of eZ Platform added.
• Several improvements done on doc.ez.no and specifically doc.ez.no/display/TECHDOC.

Kernel

• [API] Fix publishing to only update modified time, leaving published time to be time of first publish like in legacy
• [Twig] New ez_field function, unlike ez_field_value returns whole Field
• EZP-24467 - [API] When moving an object to an hidden container, the moved object doesn't have the hidden by superior status Closed
• EZP-25366 - Kernel issue: By doing a subtree copy with subitems using ObjectRelation, the Relation is broken on the copy until you republish it. Closed

UI

• Improvements to policy & limitation handling, more coming in 16.02
• Display language names instead of language code
• API doc js-rest-client: http://ezsystems.github.io/javascript-rest-client/
• API doc Platform UI: http://ezsystems.github.io/platformui-javascript-api/
• Tutorials for extending UI: https://doc.ez.no/display/TECHDOC/Extending+Tutorials

New projects in work for future releases

• https://github.com/ezsystems/docker-php
• https://github.com/ezsystems/ezplatform-demo

Contributors

Several of the mentioned changes above where done by contributors for this release, notable contributions merged from among others:

• @rihards
• @iherak
• @crevillo
• @wizhippo
• @blankse
• @jeromegamez
• @emodric
• @GromNaN

Upgrading a 15.12 project

Existing 15.12 (1.0) projects can also easily be updated using Composer. From the project's root, create a new branch from the project's master, or from the branch you're upgrading on:

If it's not there, add ezsystems/ezplatform as an upstream remote:

Then pull the tag into your branch:

You will get conflicts, and it is perfectly normal. 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:

You may also run git remove composer.lock if you do not keep a copy of it in the branch.

Merging 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:

You should see what was changed, as compared to your own version, in the diff output. The 1.1.0-rc1 tag changes the requirements for all of the ezsystems/ packages. Those should be left untouched. All of the other changes should be removals of your project's additions. You can use git checkout -p to selectively cancel those changes:

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

Using composer require

You may also checkout your own composer.json, and run the following commands to update the ezsystems packages requirements from v1.0.x to v1.1.0:

Fixing other conflicts (if any)

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

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

Updating composer.lock

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

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 test the project, run integration tests... once the upgrade has been approved, go back to master, and merge the upgrade-1.1.0 branch: