[MULTISITE-17] Use the configuration to omit area nodes for areas like brandings rather than passing the content. Created: 07/Apr/14  Updated: 16/Apr/14  Resolved: 14/Apr/14

Status: Closed
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.4, 1.1

Type: Improvement Priority: Major
Reporter: Philipp Bärfuss Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: maintenance, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLSTK-1037 Use the configuration to omit area no... Closed
dependency
depends upon MAGNOLIA-4711 Templating: Allow to omit the area no... Closed
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   

Once MAGNOLIA-4711 is fixed we have to use it in all the places where we pass the current content node to the area.



 Comments   
Comment by Milan Divilek [ 14/Apr/14 ]

Reopen:
http://hudson.magnolia-cms.com/view/Tests/job/int_migration-tests_5.0-to-5.2.x-branch/60/Diff_Reports/
http://hudson.magnolia-cms.com/view/IntegrationX/job/int_migration-tests_4.5-to-5.2.x-branch/49/Diff_Reports/

Comment by Milan Divilek [ 14/Apr/14 ]

Differences in migration-tests_5.0-to-5.2.x-branch were caused by missing hudson job for multisite 1.0.x branch. SYS-495
Difference in migration-tests_4.5-to-5.2.x-branch. Added tasks for adding createAreaNode also when migrate from ETK.

Generated at Mon Feb 12 06:05:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.