Global navigation

   Documentation Center
   eZ Studio & eZ Platform
     User Manual
     Technical Manual
     Glossary
   eZ Publish 4.x / legacy

 
eZ Publish (5.x)

eZ Publish 5.x | For eZ Platform & eZ Studio topics see Technical manual and User manual, for eZ Publish 4.x and Legacy topics see eZ Publish legacy

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

5.x Feature4.x FeatureNote/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) Relation(Object) Relation 
Field(Object) AttributeMissing 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"
FieldTypeDataTypeSee FieldTypes reference for list of supported types, known unsupported FieldTypes are mentioned in Known issues
LocationsNode

 

Section 

 

ContentType(Content) Class 
FieldDefinition(Content) Class Attribute 
FieldGroups(Content) Class Attribute Grouping 
ObjectStateObjectState 
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 APIn/aLegacy/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 environmentDevelopment modeIn 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
ControllersModules 
BundlesExtensions 
(Twig) Template system(eZ) Template system 
ViewProviderOverride systemRestricted to viewLocation in 5.0, viewContent added in 5.1, for changing presentation logic.
Controller overriden/a5.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 systemDesign systemPlanned to use LiipThemeBundle, potentially in version 5.3.
HTTP CacheView- / Static- CacheFor anonymous users with content aware caching since 5.0, also for logged in users with context aware caching since 5.2
SiteAccessSite accessCustom Url, host, port and combination matching to a specific set of settings
SiteAccessGroupn/aNew in 5.x, grouping of related SiteAccesses and common settings for them, typically used to denote a "Site"
CSRFeZ FormTokenProvided by Symfony
Render + Query / API usefetch functionsCombining the render functionality of Symfony combined 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 native support for cache while at itcache and view / logic separation handled in a native way.
   
Data  
Persistence cacheCluster- / Class- / ClassAttribute- / var- / "Global"- cacheIntroduced in 5.1, multi repository (aka multi-db) setups support added in 5.2.
IOCluster (-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 repositoryMulti-dbSupported, however see note on "Persistence cache", as of 5.3 with own "repository" configuration.
   

...