[MULTISITE-123] As a developer, i want the site definition to be determined based on the path of the page, in pages app Created: 19/May/22 Updated: 18/Apr/23 Resolved: 02/Nov/22 |
|
| Status: | Closed |
| Project: | Magnolia Multisite Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||
| Epic Link: | MultiSite on Saas | ||||||||||||||||||||||||||||
| Sprint: | DevX 14 | ||||||||||||||||||||||||||||
| Story Points: | 0 | ||||||||||||||||||||||||||||
| T-Shirt Size: | X-Small | ||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||
| Description |
|
Each site is going to be mapped to a content path in Pages. Since we cannot ensure load order in registry, each site must uniquely match the content. If multiple sites match same pattern -> first matching site wins. Check if Note: On SaaS we want to map by the content path in Pages rather than just by domain - because different domains might not be configured for the different sites. This applies to development and to production. Customers may just be using the magnolia-cloud.com domain. Our main use case currently is for the authors who are logged into magnolia-cloud.com that the Page Editor loads the correct SPA based on the 'baseUrll' and 'routeTemplate' on the site configuration. |
| Comments |
| Comment by Christopher Zimmermann [ 27/Sep/22 ] |
|
It looks like this ticket will be completed when the linked tickets are complete. We keep this ticket open primarily so we remembver to check the behaviour that is describved here. |
| Comment by Dai Ha [ 02/Nov/22 ] |
|
The text in ticket's title might lead to the confusion of those multisite usecases, for example on demo author: The site travel can be accessed by either: https://travel-demo.magnolia-cms.com/ or https://demoauthor.magnolia-cms.com/travel The second link describes better "map site to the content path" behavior
|
| Comment by Christopher Zimmermann [ 02/Nov/22 ] |
|
It works. Verified in related ticket. https://jira.magnolia-cms.com/browse/MGNLSITE-165 |