Message-ID: <74143593.3428.1485853108789.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3427_1411630662.1485853108789" ------=_Part_3427_1411630662.1485853108789 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Upgrading: As this is a alpha release, there is no upgrade= instructions yet, this is planned for Beta.
Download: See share.ez= .no/downloads, or see Install for how to install via= composer.
July 6th 2015
The third alpha release of eZ Platform,15.05 builds u= pon the 15.03 March release adding additional support for editing- and b= rowsing-capabilities. It also contains several underlying improvements and = fixes that will be part of the 5.3.6 and 5.4.3 maintenance versions that will be rele= ased soon.
Besides lots of smaller improvements and fixes found bellow, and mention= ed above for the 5.x sub release, the main changes are:
Symfony 2.7 LTS is now fully supported, and no deprecation errors sh= ould be thrown anymore. This should also ensure compatibility with the 2.8 = and 3.0 releases planned for november this year.
Dynamic settings have been refactored to use the Expression Language instea= d of fake services.
More info: Symfony 2.7/3.0 epic, Symfony 2.7 announcement blog post
Content types can now be created o= r edited from PlatformUI, inside the Admin panel. The feature isn't visuall= y integrated yet, but already covers most FieldTypes. Progress can be follo= wed on the Epic above.
Forms themselves use the Symf= ony Forms component. The implementation has been done in a distinct pac= kage, dedicated to providing Forms for the eZ Repository domain: Repository Forms.
More info: Content type management epic, repository-forms on Github, repository-forms on Packagist.
Image variations generated by Imagine can now be purged using the = application console. It can either clear all variations, or variations of a= particular alias:
# Clear all variations of the large and gallery aliases/filters php ezpublish/console liip:imagine:cache:remove --filters=3Dlarge --filters= =3Dgallery -v=20
Note that this change comes with a modification of the variations storag=
e path. This change will be transparent from a user's perspective, but you =
may want to purge the existing variations. To do this, you need to switch to the legacy hand=
ler by redeclaring the ezpublish.image_alias.variation_purge=
r
service to ezpublish.image_alias.variation_purger.legac=
y_storage_image_file
.
More info: Technical specifications, Implementation story.
A new controller and route have been added, and the Image and Binary= File content field templates have been updated. Permissions are transparent= ly checked during download, and HTTP resume is supported. The Route Re= ference API, provides facilities to generate the right path from templa= tes, and a valid URI is exposed over REST.
More info: D= ocumentation, Specificaftions, Implementation story, Content view module e= pic.
Thanks to the addition of the Universal Discovery Widget in 2015.03, tho= se functions have been added to PlatformUI.
More info: Content CRUD UI epic
Notifications will now be displayed upon certain events in the backoffic= e.
Each notification is either an information (content was published, locat= ion was removed...), or an error. A reusable javascript API makes it easy t= o re-use the system for your own needs, if any, on PlatformUI. A PHP API ha= s also been added in order to send notifications from the Symfony controlle= rs used to implement some parts of the backoffice.
More info: UI notifications epic
A prototype of the WYSWIGYG editor for the RichText FieldType has been a= dded. It is based on Alloy Editor, itself based on CKEditor.
To see it in action, you need to create a new Content Type with a RichTe= xt Field. A perfect opportunity to test the Content Type admin UI.
More info: Alloy Editor, RichText editing = epic, prototype screencast
The ezsystems/privacy-cook= ie-bundle package, introduced in the 15.03 release, has been made much = more flexible. It now comes with a Factory interface and a Banner value obj= ect, so that it is easy to pick the banner's content in different ways.
The built-in implementation uses a configuration file based Factory, all= owing you to configure the cookie banner using simple yaml files.
More info: github repository = ;
<= /p>
Changes (Stories, Improvements and bug fixes) can be found= in our issue tracker: = 51 issues (some are still pe= nding additional documentation changes)
List of issues specifically affecting this release: 35 issues
General "Known issues" in Platform stack compared to<= em> Legacy: 8 issues
Epics tentatively* planned for first stable release: 7 issues
Epics tentatively* planned for first LTS release: 0 issue
'* Some of these fea= tures will not be in the stable releases, the once we first and foremost wi= ll aim for having in the release are those mentioned on the Roadmap.