Issue Details (XML | Word | Printable)

Key: CONF-6936
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: Ivan Benko [Atlassian]
Votes: 0
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Confluence

ConfigureSpaceLogoAction affected by attachment size

Created: 05/Sep/06 02:37 AM   Updated: 10/Dec/08 05:18 PM
Component/s: Attachments
Affects Version/s: 2.2.8, 2.3
Fix Version/s: 2.2.10

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Agnes Ro [Atlassian] and Ivan Benko [Atlassian]
Since last comment: 2 years, 42 weeks, 2 days ago
Resolution Date: 12/Sep/06 12:45 AM
Labels:


 Description  « Hide
Presently, the Attachment Settings under the General Configuration affects the loading of space logo file size. This seems to be OK as far as the max attachment size is consistently verified by ConfluenceWebWorkConfiguration.

Two problems:
1. When I set the attachment size and try to load the logo file larger then the predefined file size I should get an error different to the one below.

The following error(s) occurred:

  • Could not locate uploaded logo in request. Double check the file you are sending through.
    ConfigureSpaceLogoAction

The error should be more descriptive to clearly state that the file attempted to upload is larger then allowed. Not that it is not found.

2. Also, ones you load the logo, the only way of removing it is to set the Logo back to default. This mean, when you want to revert the process, you need to upload the logo again. Kind of user-unfriendly There should be an option to remove the logo. Or when using the default logo, one should be able to use already uploaded logo. Can we store it somewhere and be able to retrieve it when needed? Or is this "unwanted" behaviour?

Ib



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Agnes Ro [Atlassian] added a comment - 12/Sep/06 12:45 AM
Fixed error message.