Null pointer exception when submitting a template
I currently have a template, on my local instance of hannon hill. 7.14.2. I just restarted the server this morning, thinking that might fix the problem but no. We did just recently upgrade from 7.12.x. I am attaching the log.
Starting this morning, every time I try to submit an edit to a template, I get the following error:
Jun 24, 2016 8:35 AM
An error occurred: java.lang.NullPointerException
You may choose to retry the operation. If the problem persists, please contact a system administrator.
The error has been logged to the system console.
- cascade.log_(1).zip 32.9 KB
Discussions are closed to public comments.
If you need help with Cascade CMS please start a new discussion.
|?||Show this help|
|ESC||Blurs the current field|
|r||Focus the comment reply box|
|^ + ↩||Submit the comment|
You can use
Command ⌘ instead of
Control ^ on Mac
1 Posted by ediego on 24 Jun, 2016 12:42 PM
other assets on the site allow me to submit, and on other sites as well.
Support Staff 2 Posted by Tim on 24 Jun, 2016 02:58 PM
Thanks for attaching that log file. When you have a moment, can you attach a file containing the contents of the Template you're attempting to submit? Also, before you submit this Template, can you tell me which Advanced Options are currently checked in your instance (and whether un-checking any of those seem to change the outcome)?
I'll do some testing locally once I have a copy of your Template.
3 Posted by ediego on 24 Jun, 2016 03:08 PM
here is the file of the template.
the only option that is checked, is "Broken Links"
Support Staff 4 Posted by Tim on 24 Jun, 2016 03:30 PM
Thanks for attaching that. It seems like this is tied to something with the Broken Link check when you submit. Can you verify that if you disable that check, you're able to submit the Template?
I'll have to take a closer look at this to see what the underlying issue is with the link checking that is causing this NPE.
5 Posted by ediego on 24 Jun, 2016 03:52 PM
yes, if i uncheck the broken links option I am able to submit the changes.
Support Staff 6 Posted by Tim on 24 Jun, 2016 05:06 PM
Thanks for confirming. Once I have the chance to debug this I'll let you know.
It sounds as though you should be OK in the meantime by un-checking that option any time you need to submit this particular Template.
7 Posted by ediego on 28 Jun, 2016 11:57 AM
any update on this issue?
Support Staff 8 Posted by Tim on 28 Jun, 2016 02:08 PM
Just had a chance to look into this a bit further. I believe the problem is this link:Can you confirm that the path to this
themepage is correct? So far, I've only been able to replicate this NPE when I attempt to point to an asset that doesn't exist.
Let me know. Regardless, this does appear to be some sort of bug with the way the application is handling path rewriting within these types of tags.
Support Staff 9 Posted by Tim on 18 Jul, 2016 10:15 PM
Just wanted to make sure you saw my previous comment. Let me know if what I mentioned appears to be the case.
10 Posted by ediego on 19 Jul, 2016 12:44 PM
The theme.css file isn't in that site.
Here's the way this is setup.
Those themes are in a Common site (that shares themes/formats/etc with multiple properties) called UM Common Assets.
The sites that actually use those themes are in different "sites" and they do have that css file present.
Should I just create an empty theme.css in the UM Common Assets folder to resolve this until the bug is fixed.
Support Staff 11 Posted by Tim on 19 Jul, 2016 06:31 PM
The bug appears to be related to the path rewriting when the link is surrounded with these particular tags.Since this asset doesn't exist, rather than prompting you to change it to a valid link, it's throwing a NPE. Even if this were corrected, you'd still run into issues here since this particular asset doesn't actually live in the Site where the Template resides. In terms of the setup, since you mentioned that the Sites using this Template do have that file present, what happens if you try using 'asset local' links?:One downside here is that I don't know if you'll be able to point to a specific Output in addition to using the 'asset local' notation, so this may not work if your theme Page has multiple outputs.
Tim closed this discussion on 15 Aug, 2016 03:26 PM.