[MAGNOLIA-3839] Addition of non-existent class in freemarker configuration will break AdminCentral Created: 15/Sep/11  Updated: 23/Jan/13  Resolved: 27/Dec/11

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 4.4.5

Type: Bug Priority: Critical
Reporter: Frank Sattler Assignee: Zdenek Skodik
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS


Issue Links:
Cloners
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:
Visible to:
Fei Phoon

 Description   

The creation of node data called 'class' which points to a non-existent class will result in an unhandled FileNotFoundException within AdminCentral, resulting in the inability to access Magnolia.

Steps to reproduce:
WARNING: FOLLOWING THESE STEPS WILL RESULT IN THE MAGNOLIA INSTANCE BECOMING INACCESSIBLE. MANUAL MODIFICATION OF THE JCR WILL BE REQUIRED.

1. Go to 'config:/server/rendering/freemarker/templateLoaders'.
2. In this location, create a new content node called "file".
3. In the newly created content node, create node data of type "String", giving it the name "class" and the value "info.magnolia.freemarker.loaders.nonexistentClass"

From that point onwards, any attempt to access parts of AdminCentral or the web site it manages will result in unhandled exceptions.



 Comments   
Comment by Zdenek Skodik [ 27/Dec/11 ]

Can't be reproduced anymore - ClassNotFoundException gets thrown properly while AdminCentral or any websites are still accessible.

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