Quick links
eZ Platform beta 8 is now available for testing. This releases focuses on cleanup, stabilization and the online editor.
Highlights
Platform no longer comes with the demo
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:
- A clean AppBundle is now shipped and enabled by default. Unless you have a specific reason not to do so, this is where your projects should start from
- The
ezpublish
folder now contains an emptyResources/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 theviews
directory - Settings have been cleaned up:
ezpublish.yml
has been renamed toezplatform.yml
, and greatly simplified. It is now imported fromconfig.yml
instead of being force-loaded by the kernel
This 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.
Platform UI performances improvements
- The tree now uses location search instead of content search, leading to fewer HTTP queries (EZP-24873)
- The breadcrumb has been changed to use the new
AncestorOf
criterion, and should perform much better (EZP-24871) - A new "combine" YUI semantic setting has also been introduced. This prepares for the combo loader feature that is being worked on. Once approved this should significantly shorten the loading time of the backoffice.
Online editor embeds
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:
Role, policies and languages management
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
- Items can be excluded from selection in the universal discovery widget (EZP-24989)
This mechanism is based on callbacks, and can be re-used in PlatformUI extensions. - The "save" button will be hidden when editing users (EZP-25016)
- Field definitions position is now calculated automatically (EZP-24569)
- The preview will now use the previewed content's title (EZP-24927)
Bug fixes
- The main location of content can be changed (EZP-24901)
- Proper feedback will be given when an uploaded file exceeds the maximal size (EZP-25037)
- The language will be properly set when creating a new content as a child of freshly created one (EZP-25048)
- Uploading a different file type won't break the file's type anymore (EZP-25039)
- Selection fields are now validated properly (EZP-24716)
- Options can be added to a selection field definition (EZP-25002)
- Visibility is now properly updated in the content details tab (EZP-24945)
- eng-GB is no longer hardcoded in preview (EZP-24929)
- Subitems visibility will be updated when changing a location's visibility (EZP-24964)
- Fixed browser specific issues in Internet Explorer (EZP-24055), Firefox (EZP-24907) and Safari (EZP-24986)
- The first author field will now be automatically filled (EZP-24050)
- The always available flag is correctly set on created content (EZP-24766, EZP-25091)
- Field edit display will no longer break when zooming (EZP-25018)
- Email validation has been improved (EZP-24962, EZP-25051)
- Non-containers can no longer be used as targets for moving or copying content (EZP-24973)
- Image, media and binary field values can now be emptied and changed (EZP-24959, EZP-24922)
- Alternative languages of content with untranslatable fields can now be saved (EZP-24625)
- Role editing will not report an error anymore when editing a role without changing its name (EZP-24939)
- Hitting enter in a repository form doesn't report an error anymore (EZP-24942)
- Notifications will be correct after publishing content (EZP-25035)
Platform
XmlText moved to its own package
The XmlText FieldType has been moved to its own package (EZP-24925). It can be installed by requiring ezsystems/ezplatform-xmltext-fieldtype
.
Default view templates
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.
Changelog
Anchor | ||||
---|---|---|---|---|
|
Changes (Stories, Improvements and bug fixes) can be found in our issue tracker:
JIRA | ||||||||
---|---|---|---|---|---|---|---|---|
|
Known issues & upcoming features
List of issues specifically affecting this release:
JIRA | ||||||||
---|---|---|---|---|---|---|---|---|
|
General "Known issues" in Platform stack compared to Legacy:
JIRA | ||||||||
---|---|---|---|---|---|---|---|---|
|
Epics tentatively* planned for first stable release:
JIRA | ||||||||
---|---|---|---|---|---|---|---|---|
|
Epics tentatively* planned for first LTS release:
JIRA | ||||||||
---|---|---|---|---|---|---|---|---|
|
'* 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.
...