[MULTISITE-19] MultiSiteManager should distinguish standard from pro license Created: 21/May/14  Updated: 07/Jun/19  Resolved: 09/Sep/14

Status: Closed
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.7, 1.1.2

Type: Bug Priority: Neutral
Reporter: Zdenek Skodik Assignee: Christopher Zimmermann
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MULTISITE-67 MultiSiteManager should distinguish s... Closed
causality
dependency
duplicate
is duplicated by MULTISITE-29 Multisite module floods log with "Lic... Closed
relation
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

No matter whether you own standard or pro license you're allowed to install this enterprise module. However if you reconfigure it to provide only one site definition in order to meet your license agreement, your log files are still flooded by License issue: No valid license found for MultiSite!.



 Comments   
Comment by Christopher Zimmermann [ 09/Sep/14 ]

MultiSiteManager#isEELicensed now only logs a warning if a non-pro ee license has more then one site."

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