History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SAK-9823
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Unassigned
Reporter: Steve Lonn
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Sakai

Creating: Incorrect error message if file exceeds maximum file size allowed

Created: 02-May-2007 06:03   Updated: 11-Jun-2008 09:48
Component/s: Resources
Affects Version/s: 2.4.0
Fix Version/s: 2.4.0

Time Tracking:
Not Specified

Environment: Tested on qa1-us

2.4.x Status: None
2.5.x Status: None


 Description  « Hide
If the user attempts to upload a file that exceeds the maximum upload size limit, they receive this error message:
Alert: Please choose the file to attach.

They should instead receive an error message that looks like this (copied from Sakai 2.3.1):
Alert: The upload size limit of 20MB has been exceeded.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Jim Eng - 02-May-2007 13:54
This should be included in the 2.4 release if possible.

Harriet Truscott - 09-May-2007 04:20
verified on Nightly on IE7 - error message is now "The upload size limit of 20 MB has been exceeded."

Jim Eng - 01-Jun-2007 10:57
Steve,

Could you verify two things:

1) this is broken in 2.4.x on nightly2
2) this is fixed on the trunk instances on nightly2

If both are true, please close the ticket, assign it to Mike Osterman, and include a comment documenting that the item is verified and ready to be merged. Otherwise, please assign back to me with comments about items 1 and 2.

Thanks.

Jim

Steve Lonn - 06-Jun-2007 10:52
Jim appears to be fixed (and NOT broken) in trunk and in the 2.4.x branch. I tested with Firefox on Mac 10.4.

I'm not sure why this should be broken on 2.4.x, but per your instructions, I'm assigning it back to you for now.


Jim Eng - 06-Jun-2007 11:15
Steve verified that the fix for this was in fact merged into 2.4.0 before the release. Therefore, there's nothing to merge into the maintenance branch.

Jim Eng - 06-Jun-2007 11:17
Changing fix version to document that this did make it into the release.