SiteAccess is partly taken into account in UI, however not in:
- preview url
- rest url
- .. and besides UI won't work inside siteaccess when matching is on url, it always need to be on root of domain name
This causes problems, especially for beginners setting up the software and not following every step correctly, or for people that want to setup different SA setups. So we need to make a decion how this should work, and find a way to take it into account, by passing the right url to preview, and by sending siteaccess by X-SiteAccess via CAPI to REST API as it does not support prefix on URL and so on.
This Epic needs Spec, cause if we want to have a drop down to select site (access) in the future, this would imply overall UI (login, admin, ..) is loaded in the context of the repository, and not SA, while content and page sections for instance should take it into account. Also need to have multi site setups in mind here in regards to permissions.
Issues in Epic
|EZP-23759||PlatformUIBundle assumes proper VirtualHost setup||Backlog||Unassigned|
||EZP-24370||Platform shell url do not include siteaccess||Closed||Unassigned|
|EZP-24930||Preview iframe URI assumes the eZ Platform is setup in Host SiteAccess matching||Backlog||Unassigned|
||EZP-25409||capi needs a way to set site access||Closed||Unassigned|
|EZP-25410||The correct api endpoint need to be used for ui and uri based site accesses||Backlog||Unassigned|