eZ Platform 15.12.1 Release Notes

The first sub-release of eZ Platform 15.12 is now available for update.<= /p>

For the release notes of the corresponding eZ Studio sub-release, see eZ Studio 15.1= 2.1 Release Notes.

Changes since 15= .12

As already deprecated on requirements page, this release= does not support PHP 5.4 any longer.

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

Distribution

Improved Install doc and Apache/Nginx doc, added script to generate vho= st for automation needs.
PHP Internal web server "works", further fixes in 16.02 to make it test= ed and supported for dev use.
Installers don't write to config anymore, only folders mentioned in dir= ectory permissions are written to.
Info on where to find demo install of eZ Pla= tform added.
Several improvements done on doc.ez.no and specifically d= oc.ez.no/display/TECHDOC.

Kernel

[API] Fix publishing to only update modified time, leaving published ti= me to be time of first publish like in legacy
[Twig] New ez_field function, unlike ez_f= ield_value returns whole Field - find more information here.
EZP-24467 -= [API] When moving an object to an hidden container= , the moved object doesn't have the hidden by superior status=20 Closed
EZP-25366 -= Kernel issue: By doing a subtree copy with subitem= s using ObjectRelation, the Relation is broken on the copy until you republ= ish it.=20 Closed

UI

Improvements to policy & limitation handling, more coming in 16.02<= /li>
Display language names instead of language code
API doc js-rest-client: http://ezsystems.g= ithub.io/javascript-rest-client/
API doc Platform UI: http://ezsystems.g= ithub.io/platformui-javascript-api/
Tutorials for extending UI: https://doc.ez.no/display/TECHDOC/E= xtending+Tutorials

New projects in work for future releases

Contributors

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

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

Upgrading a= 15.12 project

New proposed upgrade process

This section reflects a proposed git based workflow for handling upgrade= s, feedback on how this works in practice and input on how to further impro= ve/simplify it is welcome.

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:

From your master branch

=20

git checkout -b upgrade-1.1.0

=20

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

From the upgrade-1.1.0 branch

=20

git remote add ezplatform http://github.com/ezsystems/ezplatform.g=
it

=20

Then pull the tag into your branch:

From the upgrade-1.1.0 branch

=20

git pull ezplatform v1.1.0

=20

You will get conflicts, and it is perfectly normal. The most common ones= will be on composer.json = ;and composer.lock.

If you get a lot of conflicts (on the doc folder for instance), and eZ Platform was installed from the share.e= z.no tarball, it might be because of incomplete history. You will have = to run git fetch ezplatform --unshallow to load the = full history, and run the merge again.


The latter can be ignored, as it will be regenerated when we execute com=
poser update later. The easiest is to checkout the version from the tag, an=
d add it to the changes:


From the upgrade-1.1.0 branch

=20
git checkout --theirs composer.lock && git add composer.lo=
ck=20


You may also run git remove composer.lock if you do no=
t keep a copy of it in the branch.
Merging compo=
ser.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 ver=
sion, and inspect the changes. It should be readable for most:


From the upgrade-1.1.0 branch

=20
git checkout --theirs composer.json && git diff composer.j=
son=20


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&nbs=
p;ezsystems/ packages. Those should be left untouched. All of =
the other changes should be removals of your project's additions. You can u=
se git checkout -p to selectively cancel those changes:

=20
git checkout -p composer.json=20


Answer no (do not discard) to the requirement cha=
nges of ezsystems dependencies, and yes=
 (discard) to removals of your changes.
Using compose=
r require
You may also checkout your own composer.json, and run the f=
ollowing commands to update the ezsystems packages requir=
ements from v1.0.x to v1.1.0:

=20
git checkout --ours composer.json
composer require --no-update "ezsystems/ezpublish-kernel:~6.1.0"
composer require --no-update "ezsystems/platform-ui-bundle:~1.1.0"
composer require --dev --no-update "ezsystems/behatbundle:~6.1.0"

# PHP requirement is now 5.5+, and 7.0 is now supported for dev use (see to=
p of this page for requirements link)
composer require --no-update "php:~5.5|~7.0"

# As there are some bugs with Symfony 2.8, make sure to pull in Symfony 2.7=
 LTS updates
composer require --no-update "symfony/symfony:~2.7.0" 
 
# This command will remove platform.php: "5.4.4" as php 5.4 is no longer su=
pported
composer config --unset platform.php=20


Fixing=
 other conflicts (if any)
Depending on the local changes you have done, you may get other conflict=
s: configuration files, kernel... 
There shouldn't be many, and you should be able to figure out which valu=
e 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<=
/li>

Updating com=
poser.lock
At this point, you should have a composer.json file with the correct req=
uirements. Run composer update to update the dependencies=
. 

=20
composer update --with-dependencies ezsystems/ezpublish-kernel ezsy=
stems/platform-ui-bundle ezsystems/behatbundle=20





In order to restrict the possibility of unforeseen updates of 3rd party =
packages, we recommend by default that composer update is rest=
ricted to the list of packages we have tested the update for. You may remov=
e this restriction, but be aware that you might get a package combination w=
e have not tested.



On PHP conflict


Because from this release onwards eZ Platform is compatible only with PH=
P 5.5 and higher, the update command above will fail if you use an older PH=
P version. Please update PHP to proceed.


Commit, test a=
nd merge
Once all the conflicts have been resolved, and composer.lock updated, the merge can be committed. Note that you may or may not ke=
ep composer.lock, depending on your version management wo=
rkflow. If you do not wish to keep it, run git reset HEAD <fi=
le> 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 h=
as been approved, go back to master, and merge the upgrade-1.1.0 branch:


=20
git checkout master
git merge upgrade-1.1.0=20

eZ Platform 15.12.1 Release Notes

Changes since 15= .12

Distribution

Kernel

UI

New projects in work for future releases

Contributors

Upgrading a= 15.12 project

Merging compo= ser.json

Manual merging

Using compose= r require

Fixing= other conflicts (if any)

Updating com= poser.lock

Commit, test a= nd merge