Message-ID: <1274876264.2842.1485850980452.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2841_1664596259.1485850980451" ------=_Part_2841_1664596259.1485850980451 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
With eZ Platform it is possible to serve multiple, completely different = sites using one eZ Platform instance and database.
Each site will have its own content root, at a lower level than the defa= ult one (Location ID 2). One backoffice can be used for each site, but it i= s 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 ezplatform.yml
, either at site=
access 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
content.tree_root.=
location_id
This 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_prefixes
Use this parameter to exclude a list of URIs 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 Platform, so they can be ignored.
The Index Page is the page shown when the =
root index / is accessed.
You can configure the Index Page separat=
ely for each siteaccess. Put the parameter index_page
in your =
ezplatform.yml
file, under the right siteaccess category.
ezpublish: system: mygreat_site: languages: - eng-US #The page to show when accessing IndexPage (/) index_page: /yourURIPage=20
index_page
is the configured content root.