[MGNLSTK-1382] For specific mappings the incorrent site definition is returned from ExtendedAggregationState Created: 29/Apr/14 Updated: 02/Jul/18 Resolved: 02/Jul/18 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | 2.0.19 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Bence Vass | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
unchanged Magnolia Enterprise 4.5.18 bundle |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
When setting the mapping of a site definition to specific values, the wrong site definition is saved and returned from ExtendedAggregationState F.e. consider the following setup: Site1 (mapping -> URIPrefix: /en handlePrefix: /site1 repository: website) When opening: This is a big problem when using the multiple tree strategy for multilanguage sites (http://documentation.magnolia-cms.com/display/DOCS45/Multilanguage+structure), which have the same domain, but different URIPrefixes. |
| Comments |
| Comment by Jan Haderka [ 02/Jul/18 ] |
|
STK have been deprecated in September 2017. As part of this project nearing end-of-life, we are not planning to fix any of the existing issues except for the critical security issues. For more details, please consult documentation. |