Skip to the content
Documentation

Multisite using content_root

No ratings yet

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 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 Exponential Legacy.

Configuration

The feature is configured in ezplatform.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 Platform, so they can be ignored.

Contributors

Comments (1 historical)

Written by readers of the earlier documentation sites, kept as they were.

Comments

Add a comment

Comments are read by a moderator before they appear.