...
| 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 6.x and beyond. | |
| Content* | (Content) Object |
|
| (Content Relations) Relation | (Object Relations) Relation | |
| Field | (ContentObject) 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 | DataType | See FieldTypes for list of supported types, known unsupported FieldTypes are mentioned in Known issues |
| Locations | Node |
|
| Section |
| |
| ContentType | (Content) Class | |
| FieldDefinition | (Content) Class Attribute | |
| FieldGroups | (Content) Class Attribute Grouping | |
| ObjectState | ObjectState | |
| UrlAlias | ||
| UrlWildcard | ||
| Language | ||
| User | ||
| UserGroup | Can by design (and intention) only have one location in 5.x when using Public API UserService | |
| Policy | ||
| PolicyLimitation | ||
| Role | ||
| RoleLimitation | ||
| RoleAssignment | 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 | 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, additional debugging planned and in progress as "pull request". |
| 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 | 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, potentially in version 5.3. |
| 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 |
| SiteAccess | Site access | Custom Url, host, port and combination matching to a specific set of settings |
| SiteAccessGroup | 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 |
| 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 6.x 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". |
\* When referring a specific instance of any of the content model entries, either "object" or "item" is normal to append depending on context. In our BDD specifications the domain names have "object" appended to them forming "Content object(s)", "Location object(s)" and so on.
Known missing in Symfony stack (black/grey list):
...