Since eZ Publish 5.1, it is possible to serve multiple, completely different sites using one eZ Publish instance and database.
Each site will have its own content root, at a lower level than the default one (location number 2). One backoffice can be used for each site, but it is also possible to use a global one.
This feature is a reimplementation of the PathPrefix one that existed in eZ Publish Legacy.
Configuration
The feature is configured in ezpublish.yml, either at siteaccess or siteaccess group level:
content.tree_root.location_id
This parameter sets the location id of the content root. The API is jailed within this root, and nothing above this level will be accessible by default. This parameter can be filtered using the excluded_uri_prefixes parameter described below
content.tree_root.excluded_uri_prefixes
Use this parameter to exclude a list of URI from the root jail defined using location_id described above. Add as many locations pathString as you like. In the example above, the Media and Images folders will be accessible using their own URI even though they're not below tree_root.location_id.
Note: Leading slashes (/) are automatically trimmed internally by eZ Publish, so they can be ignored.
2 Comments
Philippe Vincent-Royol
Same comment as Re: 2. Browsing, finding, viewing
Harald Tollefsen
When i define my own content.tree_root.location_id for my backend siteaccess (group acctually), eZ doesn't seem to be able to resolve /Users/xxx url alias'. E.g. when I define 246 instead of just 2, I get a 404 on /Users (and other subfolders of this container). Though it works if i point to it directly with /content/view/full/5 etc. Any idea how I may solve this? All other url alias seems to work except with the once below the Users hierarchy.