UPDATED TO=
REFLECT DECEMBER 2016 1.7 RELEASE
Feature changes= from eZ Publish to eZ Platform open source and enterprise editions:=
| eZ Publish Feature | Description | Will it be included in eZ Platform Open Source or Enterprise Editi=
on? |
Time Frame |
|---|---|---|---|
| e-Commerce shopping cart and product datatypes | Ability to manage the sale of goods and other products in eZ and t= o give end users an online cart and a check-out process | The feature will not be ported to the first version of eZ Platform= , which will serve as an infrastructure for e-commerce. eZ=E2=80=99s recomm= endation is to use silver.e-shop, a commercial= solution from eZ Partner silver.solutions that is based on e= Z Publish Platform, or to build a solution on top of eZ Platform (for i= nstance, integrating Sylius or other e-commerce related components). | Use with silver.e-shop is available now as a side complementary= solution, and in the community there is attempts at integrations with Syli= us. An integrated solution for eZ Platform based on the next version of sil= ver.e-shop is under development. |
| Online Editor | Ability to manage some rich text fields, apply formatting, and add= assets such as images or existing content. Based on TinyMCE in eZ Publish.= | The Rich Text Editor is being redesigned to provide a better user = experience. It is available in eZ Platform. It is no longer based on TinyMCE, but is now bui= lt on Alloy Editor. | As of Febr= uary 2016 supports basic text styling, alignment, image/content embedding, = and migration tool from eZ Publish for the full format. Remaining features such as custom tags and tab= ular data is currently slated for early 2017. After that support for inline embed/custom tags will be = looked into. <= /p> |
| eZ Flow | Ability to manage landing pages, create custom blocks and manage f= low of content in a block. | eZ Flow is being redesigned to provide a better user experience, a= more visual interface and to simplify the business logic. The new feature,= Landing Page Management, is part of Studio and therefore only available fo= r eZ Platform Enterprise Edition users. | As of February 2016 feature parity with eZ Flow, and greatly im= proved editorial experience. |
| ODT Import and export | Ability to import Open Office (ODT) documents (and, with an extens= ion, Word documents) as a content object (not as a file) | This feature will not be built into eZ Platform in the short te= rm. Import services will be developed first. eZ is researching similar feature= s for online word processors such as Google Docs, since desktop software - = especially Open Office - is losing market share |
No plans. It = could come as a nice contribution to eZ Platform from the community as a Bu= ndle. |
| Multi-upload | Ability to drop a selection of many files in one =E2=80=9Cdrag = and drop=E2=80=9D into the content repository and have them imported as ass= ets (File, Image, Video or others=E2=80=A6) based on the MIME type of the f= ile. = Note: this is distinct from the ODT import in that with ODT import the file= s are just uploaded into a Field Type such as File, Image or other.<= /p> |
This feature will be ported to the Enterprise Edition as an editorial to= ol in Studio. It will be available in the Sub-item view of a Content item to allow the= simple creation of image galleries, for example. It will also be available= from the content edit view directly to minimize the number of clicks for t= he editor when creating collection of items. The feature is named File Import. | Target: First half of 2017. It will likely be introduced progressi= vely. |
| WebDAV | Ability to navigate the content repository using a WebDAV client, = and ability to read and write from there (ie. to create documents) | This is not a feature that we plan to implement for eZ Platform= since the WebDAV protocol is used less and less and extremely unstable dep= ending on the client software used. A potential replacement for this feature would = be to use a CMIS client but it is equally unstable and not widely adopted.<= /span> |
No plans. It could come as a nice contribution to eZ Platform from= the community as a Bundle. |
| Content Staging | An extension that enables users to set up content workflow across = different eZ Publish installations (for example: create content on one inst= allation and transfer into another one at some point, for staging or archiv= ing reasons). | While this eZ Publish extension has been adopted by organizations = for several use cases, it has not always fully answered the business needs.= eZ plans on to bring similar capabilities to eZ Platform Enterprise Editio= n users, but in a different way. For that, eZ will not =E2=80=9Cport=E2=80= =9D content staging to the new platform but instead will redesign features = and develop them progressively on the new products. Initially, eZ will deve= lop Content Deployment services within eZ Platform and a =E2=80=9CWorkspace= =E2=80=9D feature in the Enterprise Edition that will enable users to creat= e content in a workspace and then deploy it to a location local or remote f= rom the installation the user is in. This will enable editors to deploy con= tent to environments such as Test, Production or others. The feature is cal= led Workspace. | Plan is to design the deployment services sometime in 2017 and = implement after that. In the Enterprise Edition, our plan is to have content de= ployment capabilities in a workspace also in 2017. |
| Image Editor | A simple image editor which allows image manipulation such as resi= zing, cropping, flipping, rotating and simple image effects such as blurrin= g elements in a photo and placing a watermark. | eZ plans to create an image editor in the Enterprise Edition. Imag= e editor will be slightly redesigned to be more user-friendly. A key goal, = allowing the creation of image variations such as size and compression, may= be done in a second phase. | This is not prioritized for 2017. It could be accelerated by user = contributions. |
| Import/Export eZPkg package system | eZPkg is a convenient way to import and export content, but also c= ontent types, styles and extensions, into a single package that can be used= for deployment. | We are not planning to port this feature in a similar way to eZ= Platform. We plan to implement the content import/export capability using a co= ntent deployment service, which will use API directly to replicate some or = the full amount of content from one repository to another; preferred format= : XML or JSON. For the deployment of styles, extensions and Content Types, we ar= e still investigating but many requests suggest to use source control for t= hat. = Topic still to be refined. |
No plan and no timing in the short term but some of the problems t= his feature solved will be covered by other features such as content deploy= ment in workspaces. |
| Legacy Monitoring | eZ Publish Enterprise customers can benefit from a service of site= monitoring that is used to better understand how their installation evolve= s (i.e., size of the content repository). | The legacy site monitoring service will not be ported to the ne= w platform. New monitoring, which is being designed, will focus more on monitoring= the installation from a software perspective (content repository, web serv= er, database) to make sure it is healthy and conforms to the requirements o= f the platform. The new monitoring will focus less on the activity on the p= latform itself (ie. monitoring the object created etc.). |
A new monitoring service is under consideration for eZ Platform En= terprise Edition. |
| eZ Find / Advance Search | An extension that upgrades search capabilities into a strong enter= prise search engine, thanks to the use of the Solr Open Source search softw= are. | In eZ Platform, access to powerful search capabilities is now b= uilt-in to the platform with the ability to use Solr (and, in the future, p= robably Elasticsearch) as a back end for the repository search and na= vigation. No standalone extensions or bundles required. Specifically:
There are = so far no plans for other advanced features such as:
|
Most featu= res already in place. Comin= g in 2017:
|
| Workflow | A workflow system that allows developers and editors to set up com= plex business processes such as editorial workflows, e-commerce check-out p= rocesses, and other multi-step processes. The feature includes an engine as= well as a basic user interface, with support for limited collaboration dur= ing the editorial process. | A new feat= ure, Flex Workflow, has been added to the Enterprise Edition. It helps stre= amline the editorial process by giving the user full control over the valid= ation and approval process for the content they crafted. Finally, we also foresee the development of a more tradit= ional advanced workflow system for editors and information architects. This= is a feature that we will most likely implement in the Enterprise Edition.= |
Flex Workflow is part of 2015.12 (and later) release.<=
br> More advanced editorial workflow system is planned for 2017 in Studio. The wo= rkflow related features in eZ Platform will be released progressively as ne= eds come. |
| URL Alias | An administrative interface enabling developers and editors to man= age URL aliases and URL wildcards. | A redesigned user interface will be offered in eZ Platform.= | Specific timing to be defined. |
| Object states | An administrative interface enabling developers and editors to manage Obje= ct Sates, Object State Groups and Content assigments. | Specific timing to be defined. | |
| eZ Survey | An extension that enables content editors to create and publish su= rveys on their eZ Publish-powered by website. This survey feature is indepe= ndent from the content repository. | A survey system is not planned for eZ Platform or in the short ter= m. However, we introduced a Form Builder in Studio with the 1.7.0 release t= hat may be used for simple survey needs, and that might evolve or be extend= ed in a more complex survey solution. | The initial version of the Form Builder for Studio is part of t= he 1.7.0 release. Further development on Form Builder will be done on the 1st ha= lf of 2017. |
| eZ Tag | eZ Tag provides a sophisticated solution for tagging content wi= th powerful capabilities to manage taxonomies. It is an extension initialized by eZ= and Netgen, and then developed further by Netgen. It was ported to eZ Publ= ish Platform and the Symfony stack later on. |
We plan to develop/integrate similar features in eZ Platform. We thi= nk tagging should be a core part of the content repository. | Community has funded the support of eZ Platform UI for the eZ Tags= bundle. When this is done, eZ will prioritize the integration with the eZ = Platform core. |
| RSS feeds | RSS import and export capabilities are available with a UI in the = administration interface. Users can import an RSS feed into eZ Publish obje= cts. The export function exposes an eZ Publish feed (defined via the UI) in= to an RSS feed. | This function is not planned for eZ Platform. | No plans. = It could come as a nice contribution to eZ Platform from the community as a= Bundle. Note: Could use same underlying functionality as import/export. |
| eZ XML Export extension | An Export extension that enables users to export any content set t= o many different formats using XSLT. Exports can be automated / scheduled i= n different ways, and remote export targets (FTP servers) are supported. | This function is not planned for eZ Platform. | New export capabilities will progressively be built into the platf=
orm based on the new import/export system and installation packages with ab=
ility to pick a new format cable and use streaming or batch handling. It |
| Commenting capabilities | eZ Comment is an extension for eZ Publish legacy. |
eZ has develope= d a bundle called =E2=80=9CComment Bundle=E2=80=9D that allows developers t= o set up commenting capabilities in different ways. The comment bundle supports the us= e of third party commenting services such as Disqus or Facebook and also pr= ovides developers with the ability to manage their own commenting service.<= /span> |
The comment bundle is integrated into the eZ Platform and No pla= n to prioritize further development, but contributions welcome. <= /td> |
| Link Management | A feature that lists all links on a website, which helps users det= ect invalid links. | There is no plan to develop similar functions in the short term. | Specific timi= ng to be defined. |
| LDAP connector | A feature that enables enterprises to plug their LDA= P directories into eZ Publish and manage user roles and permissions from th= e directory. | eZ Platform already provides a much more powerful= solution for user management that benefits from Symfony capabilities. Ther= e is, however, no built-in LDAP connector. eZ plans to provide a standard L= DAP implementation. |
Builtin LDAP implementation is planned for second ha= lf 2017, until then this is possible via Symfony bundles. |
| Front-end content editing and user generated content= | eZ Publish and eZ Publish Platform can be used to gi= ve end users of the sites the ability to create and edit content objects in= the content repository. We often refer to this as User Generated Content (= UGC). | We implemented a system that enables developer to mo= re simply implement similar UGC capabilities in the =E2=80=9Ccontent module= =E2=80=9D in eZ Platform, this does not imply out of the box front end edit= ing ala web site toolbar in legacy. | Framework for User Generated Content has been int= roduced in the June 2016 release (1.4.0). This release came with the suppor= t of a limited set of field types. Solution for more field types planned for lat= er releases. Community contribution could speed up the process here.= |
| PDF Export | Automatically generate PDFs from content based on a = template and make them available on the front-end of the site. | No plan to implement this function in eZ Platform = =E2=80=9Cout of the box=E2=80=9D. | No plan for an out-of-the-box feature but it is poss= ible to do it on a project basis using templates and overrides. |
| Preview | Users of the administration interface can preview co= ntent in the different siteaccess points where it can be published.<= /td> | Preview is implemented in eZ Platform as well as Stu= dio landing page management tool. Preview will be improved, allowing to bet= ter emulate different devices. | From the first stable (Dec 2015), with additional fe= atures being developed progressively. |
| Information Collection | Collect user data in the content repository by using= information collectors. | This feature will not be ported in the same way. = eZ Platform users can use the Sym= fony Form component. Studio can use the Form Builder. |
No plans. See eZ Survey. |