...
| 5.x Feature | 4.x Feature | Note/Limitation |
|---|---|---|
| Content Model | 5.x aimed at not adding any features in the content/data model that would lead to backwards compatibility breaks, new features will instead be introduced when we reach "eZ Platform 1.0" and beyond. | |
| Content* | (Content) Object |
|
| (Content) Relation | (Object) Relation | |
| Field | (Object) Attribute | Missing FieldTypes will cause eZ Publish to return exception, this can be avoided by either implementing the FieldType or configuring it as "NullType" if you want to just quickly ignore it for now in your front end. |
| Field Type | Data Type | See FieldTypes reference for list of supported types, known unsupported FieldTypes are mentioned in Known issues |
| Locations | Node |
|
| Section |
| |
| Content Type | (Content) Class | |
| Field Definition | (Content) Class Attribute | |
| Field Groups | (Content) Class Attribute Grouping | |
| Object State | ObjectState | |
| Url Alias | When following a virtual url alias ("nop:") in legacy, it will return an "Object not found" page. On Plaform it will redirect to the home page. | |
| Url Wildcard | ||
| Language | ||
| User | ||
| User Group | Can by design (and intention) only have one location in 5.x when using Public API UserService | |
| Policy | ||
| Policy Limitation | ||
| Role | ||
| Role Limitation | ||
| Role Assignment | Until eZ Platform 2015.09.01 there was no exposed unique id for Role Assignments making it hard to delete a specific assignment. | |
| Core | ||
| Public API | n/a | Legacy/4.x does not have a official public API, almost all internal functions are exposes publicly |
| REST API | 5.1 and higher includes a working read/write REST v2 API, 4.x only had a readonly REST v1 API as of 4.5 | |
| Development environment | Development mode | In 5.x this is provided by Symfony, and web debugger is extended by eZ Publish. |
| Web stack | 5.x web stack is Symfony with several eZ features on top | |
| Controllers | Modules | |
| Bundles | Extensions | |
| (Twig) Template system | (eZ) Template system | |
| View Provider | Override system | Restricted to viewLocation in 5.0, viewContent added in 5.1, for changing presentation logic. |
| Controller override | n/a | 5.2 added feature for being able to also use override system of View Provider to also be able to override content controller under your own conditions to be able to modify behavior. |
| Theme system | Design system | Basic template/ bundle inheritance supported in Symfony, full siteaccess aware design overrides like in legacy planned for future release. |
| HTTP Cache | View- / Static- Cache | For anonymous users with content aware caching since 5.0, also for logged in users with context aware caching since 5.2 |
| Site Access | Site access | Custom Url, host, port and combination matching to a specific set of settings |
| Site Access Group | n/a | New in 5.x, grouping of related SiteAccesses and common settings for them, typically used to denote a "Site" |
| CSRF | eZ FormToken | Provided by Symfony |
| Render + Query / API use | fetch functions | Combining the render functionality of Symfony with Override system and API you are able to create reusable views of your content similarly to how you would use fetch functions in the past, but getting cache and view / logic separation handled in a native way. |
| Data | ||
| Persistence cache | Cluster- / Class- / ClassAttribute- / var- / "Global"- cache | Introduced in 5.1, multi repository (aka multi-db) setups support added in 5.2. |
| IO | Cluster (-ing of files) | 5.0-5.3 uses legacy cluster system. New improved clustering system using Flysystem introduced in 5.4 using same paths as legacy for compatibility, path layout improved in eZ Platform 15.09 and higher. |
| Multi repository | Multi-db | Supported, however see note on "Persistence cache", as of 5.3 with own "repository" configuration. |
...