File upload limit exceeded error
We are running into an issue when users try to upload a file that exceeds the pre-determined file upload limit. There are two ways that our users upload files, and in one instance, they get a notice saying the file exceeds the limit and to try again. In the other scenario, the user is presented with the following JAVA error:
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.
The first scenario, a user can go to New-> File and browse their computer for the proper file. This was works as expected, and the user sees this screenshot:
The second way, and the way that produces the JAVA error is this. Let's say a user wants to add a link. They'll highlight the text they want linked in the WYSIWYG editor, and click the Insert/Edit link icon. While browsing assets within Cascade, they also have the option to click on 'Upload' as shown in the below screenshot. If the file they chose at this point exceeds our set file upload size limit, they get the JAVA error. Any ideas on how to prevent this or fix this issue?
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by Ryan Griffith on 09 Aug, 2012 08:07 PM
Hi Jeremy,
I was able to reproduce this in Cascade 7.0.3 using the steps you provided. What version of Cascade are you experiencing this in?
Thanks.
2 Posted by Jeremy Britten on 09 Aug, 2012 08:12 PM
We are using version 6.10.9.
Interesting to hear that same issue came up for you using 7.0.3. Was it the exact same JAVA error message? Any ideas on how to resolve this issue?
3 Posted by Ryan Griffith on 09 Aug, 2012 08:31 PM
Hi Jeremy,
Thank you for notifying us of the behavior, I have logged this as a known defect in Cascade. Feel free to track the status of this issue using the link I have provided to see if it is resolved in a future version of Cascade.
In the meantime, possible workarounds here would be to:
Please let us know if you have any questions.
Thanks.
Ryan Griffith closed this discussion on 18 Oct, 2012 07:56 PM.