Since eZ Publish 5.1, it is possible to serve multiple, complete= ly different sites using one eZ Publish instance and database.
Each site will have its own content root, at a lower level than the defa= ult 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 PathPrefi= x one that existed in eZ Publish Legacy.
The feature is configured in ezpublish.yml, either at sitea=
ccess or siteaccess group level:
ezpublish:
=09system:
=09=09ezdemo_site_group:
=09=09=09content:
=09=09=09=09tree_root:
# Root locationId. Default is top locationId
=09=09=09=09=09location_id: 123
# Every URL aliases starting with those prefixes will b=
e considered=20
# being outside of the subtree starting at root_locatio=
n.
# Default value is an empty array.
# Prefixes are not case sensitive.
=09=09=09=09=09excluded_uri_prefixes: [ /media, /images ]=20
c=
ontent.tree_root.location_idThis parameter sets the location id of the content root. The API is jail=
ed within this root, and nothing above this level will be accessible by def=
ault. This parameter can be filtered using the excluded_uri_prefixes<=
/code> parameter described below
content.tree_root.excluded_uri_prefixesUse this parameter to exclude a list of URI from the root jail defined u=
sing location_id described above. Add as many locations p=
athString as you like. In the example above, the Media and Images folders w=
ill be accessible using their own URI even though they're not below t=
ree_root.location_id.
Note: Leading slashes (/) are automatically trimmed interna=
lly by eZ Publish, so they can be ignored.