Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
When reporting an issue, the more information you provide, the better we can address your issue. Here's how to collect information from your system.
If the item on which you have and issue is configured in a YAML file, provide a copy of the that file.
When the item is configured in the Configuration app, export the appropriate fragment, see Importing and exporting JCR data. The resulting XML file contains the node hierarchy. File name matches the path in the repository.
Error messages tell you which Java class produces the error. This is vital information for finding the root cause of an issue.
The first task in tracing errors is to identify the fully-qualified name of the Java class.
Example: Magnolia was unable to send mail. The fully-qualified name of the Java class where the error was raised is
The class name is not always available. For example, in Freemarker templating errors only a stack trace is displayed, no class name.
A stack trace is a sequence of nested functions called up to the point where the stack trace is generated. The error log displays the stack trace up to function where the failure occurred.
Errors are dealt with sequentially. Magnolia logs the error that first caused the failure. Rectifying the first error does not always solve the problem entirely but will help you to find the ultimate source. For example, if you try to send email and there is both a templating error and an error in your SMTP configuration, you will first need to resolve the templating error before you can see that there is also an authentication issue. See an example of error logging in the Mail module.
Once you know class name, configure logging to get more details.
Once you have collected the information necessary to troubleshoot the issue, submit it to Magnolia Support or the community.
If you opened a support ticket, attach the exported XML, log files and screenshots to the ticket. Don't paste large amounts of text in ticket comments.
To attach a file:
- Click Attach file.
- Upload the file in the Attach file screen.
- A Comment box is provided for any additional necessary details.
- If the file is larger than 10MB, zip it and attach the
To include a screenshot:
- Click More Actions.
- Select Attach Screenshot.
- Copy the screenshot, paste it in the first box and click Paste.
- Complete any other relevant fields.
- Click Attach.
If you don't have a Magnolia support contract and therefore no support account, you can still get some help from the community. Describe your issue on the forum, paste logs to a text storage service such as pastebin.com and link to them from your forum post. Don't paste large amounts of text in the forum post itself.