[MULTISITE-83] Language handling with MultiSite should be more strict Created: 14/Feb/18 Updated: 23/Sep/19 |
|
| Status: | Open |
| Project: | Magnolia Multisite Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Unassigned |
| Resolution: | Unresolved | 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: | |||||
| Description |
|
When using MultiSite together with I18nContentSupport, one can access language mutations multiple ways: then one can access site using In both cases MultiSite removes the URIPrefix and language is then resolved by the I18nContentSupport. Same can happen if we use site prefix, for example these will also work: Same as above, in both cases MultiSite removes the site prefix and language is then resolved by the I18nContentSupport. I'd consider good practice to support only the first case as it seems confusing that we can access same content under two same urls. |