...
| 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 implementing<TODO:Add link when article on this> the FieldType or configuring it as "NullType"FieldType |
| Field Type | DataTypeData Type | See FieldTypes reference for list of supported types, known unsupported FieldTypes are mentioned in Known issues |
| Locations | Node |
|
| Section |
| |
| ContentTypeContent Type | (Content) Class | FieldDefinition |
| Field Definition | (Content) Class Attribute | FieldGroups |
| Field Groups | (Content) Class Attribute Grouping | ObjectState |
| Object State | ObjectState | UrlAlias |
| Url Alias | UrlWildcard | |
| Url Wildcard | ||
| Language | ||
| User | UserGroup | |
| User Group | Can by design (and intention) only have one location in 5.x when using Public API UserService | |
| Policy | PolicyLimitation | |
| Policy Limitation | ||
| Role | RoleLimitation | |
| Role Limitation | RoleAssignment | |
| Role Assignment | Currently not possible to delete specific assignment by id, can be deleted by Role and User. | |
| 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 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 | ViewProvider |
| 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 | Planned to use LiipThemeBundle, however as there is lack of caching and support for assets currently which is blocking us from using it easily. |
| 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 |
| SiteAccessSite Access | Site access | Custom Url, host, port and combination matching to a specific set of settings |
| SiteAccessGroupSite 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) | Currently uses 4.x cluster system, new and simpler file clustering is planned for "eZ Platform 1.0" however this is abstracted away by the API and will only affect how cluster setups are configured. |
| Multi repository | Multi-db | Supported, however see note on "Persistence cache", as of 5.3 with own "repository" configuration. |
...