[MGNLETK-3] Public-Instance fails without valid license key Created: 02/Jun/09  Updated: 03/Jul/14  Resolved: 07/Oct/10

Status: Closed
Project: Extended Templating Kit (closed)
Component/s: None
Affects Version/s: 1.0
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Olivier Marti Assignee: Ondrej Chytil
Resolution: Outdated Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
Issue Links:
relation
is related to MGNLETK-5 Due to ETKi18nSupport the filter chai... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When there is no valid license key, sites using the extended templating kid (such as the demo project) are failing with the following error:
javax.servlet.ServletException: info.magnolia.module.templating.RenderException: Can't create rendering model: IllegalStateException: Can't instantiate an implementation of this class [info.magnolia.module.templatingkit.sites.SiteManager]: IllegalStateException: License issue: No license found for the Extended Templating Kit!

This should not happen for a public instances and leads to potential downtimes for major site using the extended templating kid. Are more elegant solution should be achieved when no valid license is set for the instances, such as a note withing admin central and/or no activation capabilities.



 Comments   
Comment by Magnolia International [ 11/Aug/09 ]

Is this still the case ?

Comment by Jan Haderka [ 11/Aug/09 ]

yes, fixing MGNLETK-5 fixed only the admin central so one can go and correct the license. The content view (and therefore whole public site) is still affected. Stacktrace of the error attached.

Comment by Philipp Bärfuss [ 03/Sep/09 ]

License issue: No license found for the Extended Templating Kit!

I think this is the absolute correct message, no?

Comment by Olivier Marti [ 09/Oct/09 ]

Philipp, the problem is not that it's not clear what is happening (the logs are quite clear here), the problem is how it's happening.
Means: with an invalid license the public instance fails to render which is a no go as people tend to forget to reactivate their license now and then.

Comment by Ondrej Chytil [ 07/Oct/10 ]

Issue was solved by some other change within ETK module. Cannot reproduce it now.

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