[MGNLSTK-1135] SiteMergeFilter hardcodes Site for variations Created: 15/Mar/13  Updated: 17/Feb/14  Resolved: 13/May/13

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: 2.0
Fix Version/s: 2.0.10

Type: Bug Priority: Neutral
Reporter: Zdenek Skodik Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLSTK-1357 Forward mapping doesn't work Closed
relation
Template:
Acceptance criteria:
Empty

 Description   

It makes casting any custom node2bean class impossible for site variations. We should at least request it from provider, or even better rewrite this part at all when the comment says:

workaround until SCRUM-835 is solved. The fakeSiteWithProperName will no longer be needed then. Right now not creating/merging the fakeSite would result in mgnl searching for various resources under <webappName>/variation-siteName instead of <webappName>/currentSiteName.


Generated at Mon Feb 12 07:33:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.