-
Bug
-
Resolution: Fixed
-
Critical
-
4.3.1
-
None
-
None
The Problem
The aggregation state is set to null on each forward. This is problematic as we also store the locale and site in the aggregation state. As a consequence all this information is lost after a virtual uri mapping which forwards.
Example:
- request to /de/page/param.html
- locale is set to de
- current uri is /page/param.html
- virtual uri mapping
- forward to /page.html?param
- re-execution
- ContentTypeFilter resets the aggregation state
- locale is now the default locale:en
Solution
We could simply not reset the aggregation state but this conflicts with MAGNOLIA-3203 (resetting original URI on forward). So we can either fix MAGNOLIA-3203 or reset the aggregation state partially.
- depends upon
-
MAGNOLIA-3203 aggregation state: original uri reset after forwards
- Closed
- is causing
-
MGNLETK-27 Multi site support and virtualURIMappings don't play nice together: can not resolve site definition
- Closed
- is related to
-
MGNLETK-28 multi-site support: fixing various issues in the new
- Closed
-
MAGNOLIA-3814 MgnlContext.getAggregationState().getOriginalBrowserURL() returns path to template not requested URL
- Closed