
| Key: |
SAK-10047
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Jeff Ziegler
|
| Votes: |
0
|
| Watchers: |
3
|
|
If you were logged in you would be able to see more operations.
|
|
|
Sakai
Created: 16-May-2007 09:16
Updated: 13-Jun-2008 14:44
|
|
| Component/s: |
Resources
|
| Affects Version/s: |
2.4.0,
2.4.1
|
| Fix Version/s: |
2.5.0,
2.4.x
|
|
|
Issue Links:
|
Relate
|
|
|
|
This issue is related to:
|
|
SAK-9079
Creating: No error message shown when files exceed quota
|
|
|
|
 |
SAK-10042
Creating: After exceeding upload quota, 'add anohter file' link does not work
|
|
|
|
 |
SAK-10761
The upload size limit of ___ MB has been exceeded.
|
|
|
|
|
SAK-5607
Wrong error message displayed to user
|
|
|
|
|
|
|
| 2.4.x Status: |
Resolved
|
| 2.5.x Status: |
None
|
|
In any folder, select Add -> "Create Folders". The folder creation UI is displayed. Without entering any text in the Title box, click the "Create Folders Now" button. No alert is displayed - instead the original page is loaded (in other words, your'e taken back to the point in Resources where you first began the process to add the folder).
In 2.3, attempting to create a Resources folder without first entering a title would display "Alert: Please specify a title".
|
|
Description
|
In any folder, select Add -> "Create Folders". The folder creation UI is displayed. Without entering any text in the Title box, click the "Create Folders Now" button. No alert is displayed - instead the original page is loaded (in other words, your'e taken back to the point in Resources where you first began the process to add the folder).
In 2.3, attempting to create a Resources folder without first entering a title would display "Alert: Please specify a title". |
Show » |
|
SAK-10042,SAK-10047,SAK-5607,SAK-9079, and any other tickets that describe ambiguity or misdirection or lack of direction in the messages given to users when the Resources tool fails to perform the requested action. If the problems described in a particular ticket are fixed, please close that ticket. If not, please try to provide as much information as possible about how to reproduce the error and about what the desired behavior would be. Please set the target version of those tickets as the next QA version for the 2.5.0 release. That will help focus attention on fixing them ASAP.