[MULTISITE-67] MultiSiteManager should distinguish standard from pro license Created: 07/Sep/16  Updated: 17/Oct/16  Resolved: 17/Oct/16

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

Type: Improvement Priority: Neutral
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MULTISITE-19 MultiSiteManager should distinguish s... Closed
causality
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)
Date of First Response:

 Description   

This issue is a clone of: MULTISITE-19

Original 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!."

Solution form MULTISITE-19 as a comment, which I think is wrong!
"MultiSiteManager#isEELicensed now only logs a warning if a non-pro ee license has more then one site."

This solution just doesn't make sense:
When adding a demo, travel or stk, you will have more than one site definition.
And this should be ok, HAVING multiple Site Definitions does not mean that the system HAS TO USE them. Its a cheap solution restricting the amount of site definitions by bombarding the log file.
Why should I not have more then one, having the fallback extending one and using the extended one. So I can try out different site definitions by extending once site def A and then site def B. This is still ONLY using one at the time, which is fully ok. Or backing up one by just duplication it, before changing something -> and the log is flooded again...



 Comments   
Comment by Philip Mundt [ 17/Oct/16 ]

Multisite module can only be used in an EE Pro environment.

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