eZ Platform "Alpha4" avai= lable for testing
Quick links
- Installation instructions=
- Requirements (currently same as eZ Publish Platform 5.4)<= /li>
Upgrading: As this is a alpha release, there is no upgrade= instructions yet, this is planned for Beta.
Download: See share.ez.no/do= wnloads, or see Install for how to install via compo= ser.
The fourth alpha release of eZ Platform,15.07, builds= upon the 15.05 July release. It most noticeably adds support for = Solr, as well as many UI enhancements and additions. It also contains most = improvements and fixes that are part of the 5.4.3 and 5.4.4 enterprise releases.
Highlights
With the many improve= ments and fixes listed at the bottom, the main changes are:
RichText = editor improvements
- The active element is now highlighted (EZP-24769)
- The contextual toolbar now works on the following elements:
- Headings: change level, or remove heading (EZP-24725)=
- Paragraphs: change alignment
- The native Alloy Editor "append content" can be used to add a new headi= ng or an embed element (EZP-24768)
Cont= ent language display selection
On Content that has translations, a dropdown will now list the available= languages. Selecting one of them will display the Content in that language= instead. The Edit button will now use the currently active translation.
Stories: EZP-23765, EZP-24549<= /a>
Translate content
When there are multiple languages configured, translations can be added = and edited.
Story: EZP-23766
Roles man= agement UI prototype
An UI to manage Roles and Policies has been started, and can be previewe= d.
It is currently limited to listing, creating and deleting roles, without= policy management, even though policies can already be viewed.
Epic: EZP-24071
As can be seen in the epic, this feature is being worked on, and will qu= ickly evolve over the next weeks.
=
Other UI changes
- Details of locations can now be viewed from the backof= fice: content id, creator, modification date, remote id... (E= ZP-24512)
- Interactive confirmation messages as well as n= otifications can now be triggered by server side admin pages (EZP-24652, EZP-24536)
- AlloyEditor has been updated to 0.5.x (E= ZP-24712)
- Section Management has been reworked, and moved from <= a href=3D"https://github.com/ezsystems/PlaformUIBundle" class=3D"external-l= ink" rel=3D"nofollow">ezsystems/platform-ui-bundle to ezsystems/repository-forms (EZP-24380)
- Configuration can now be sent to the PlatformUI JS app (E= ZP-24129)
Native Solr suppor= t
Until now, the SearchService was using the Legacy=
database search implementation. It was quite limited, and performed very b=
adly. The Solr implementation has been worked on since last summer, and fin=
ally made it into the product.
After config= uration and setup, Solr will be used by the SearchService for all of yo= ur Location, Content and ContentInfo queries. It has very advanced multilan= guage capabilities, and will offer great performances whenever you need to = grab Content or Locations from the Repository.
Note that as it is lifts off many limitations, this feature will also be= made available to Enterprise customers eZ Publish Platform 5.4 via a speci= fic update.
Documentation: https://doc.ez.no/display/EZP/Solr+Search+Engin=
e+Bundle
Source: ezsystems/ezplatform-solr-search-engine
Other Platform = changes
- Locations returned by the REST API will now include the Content= Info. This should avoid quite a few calls o= nly to get the name, or basic info about the Location's Content (EZP-24672)
- The REST API will now let you search for Locat=
ion in addition to Content. While the existing resource remains va=
lid, note that
/viewsshould be used instead of
Changelog
Changes (Stories, Improvements and bug fixes) can be found= in our issue tracker: = 67 issues (some are still= pending additional documentation changes)
Known issues & upcoming features
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.