eZ Platform beta 8 is now available for testing. This releases focuses on cleanup, stabilization and the online editor.
The ezsystems/ezplatform
package has been completely cleaned from any reference to the demo and DemoBundle. In addition, we have moved closer from the symfony-standard distribution:
ezpublish
folder now contains an empty Resources/views
directory. This is where the templates used in the app should go. They can be referenced from templates or yaml files as "path/to/file"
, relative to the views
directoryezpublish.yml
has been renamed to ezplatform.yml
, and greatly simplified. It is now imported from config.yml
instead of being force-loaded by the kernelThis change should make it much easier to get started on a project. It also enforces a better separation, on our side, of demo related and application related changes.
AncestorOf
criterion, and should perform much better (EZP-24871)Embed elements can now be added to RichText fields. The editor will be shown the Universal Discovery Widget to browse for the embedded content (EZP-24894).
Images handing is under active development, and will be part of the next release.
In addition, bugs were fixed on the Online Editor:
Policies (EZP-24713), roles (EZP-24700) and languages (EZP-22658) management have been implemented. Role assignment with limitations is being finished, and should be part of the next release.
In addition, the following improvements have been made
The XmlText FieldType has been moved to its own package (EZP-24925). It can be installed by requiring ezsystems/ezplatform-xmltext-fieldtype
.
Default templates were added for most views (EZP-25121). This means that any content will be shown on the site, even if no custom view rule was created for it yet. It will work for content view, with the full
, line
and embed
view types. The default templates can be overridden using container parameters, and customized per siteaccess by means of siteaccess aware settings.
Changes (Stories, Improvements and bug fixes) can be found in our issue tracker: (some are still pending additional documentation changes)
List of issues specifically affecting this release:
General "Known issues" in Platform stack compared to Legacy:
Epics tentatively* planned for first stable release:
Epics tentatively* planned for first LTS release:
'* Some of these features will not be in the stable releases, the once we first and foremost will aim for having in the release are those mentioned on the Roadmap.