[MULTISITE-92] Multisite module: implement limitation Created: 10/Apr/19  Updated: 13/Jun/22  Resolved: 12/Jun/19

Status: Closed
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0

Type: Task Priority: Neutral
Reporter: Simon Lutz Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 0.25d
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes MGNLADVCACHE-116 Site aware caching no longer creates ... Closed
causality
dependency
depends upon MGNLSITE-93 SiteRegistry cannot be extended becau... Closed
relation
is related to MGNLADVCACHE-116 Site aware caching no longer creates ... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: DX Core
Sprint: Features 12, Features 13
Story Points: 8

 Description   

Customers on EE Standard today, will be limited to one domain in DX Core → update multi-site module and include a limitation possibility through a license check

  • licenses can take arbitrary params
  • multisite itself has the generic check in module class / invoked from MultiSiteManager via filter
  • by then, site def is either in agg-state already or we have the module config to fetch site defs
  • multisite already have fallback mechanism to “default” only when license is expired so all we need is to make license check there more sophisticated.
  • would need some tests


 Comments   
Comment by Dai Ha [ 12/Jun/19 ]

Verified with magnolia-dx-core-demo-webapp-6.1-20190612.061327-34-tomcat-bundle.zip. The number of registered sites now is defined by license.

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