Bug #4629

Institutional Edit theme page: User should receive warning when banner/logo image upload fails

Added by Dan Gillean over 9 years ago. Updated over 8 years ago.

Status:VerifiedStart date:02/04/2013
Priority:MediumDue date:
Assignee:José Raddaoui Marín% Done:

100%

Category:ThemingEstimated time:2.00 hours
Target version:Release 2.0.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

To reproduce this issue
- Log in as an authenticated user to the AtoM 2.0 development site
- Navigate to an exisiting institution without a banner and/or logo and click "Edit theme"
- In either the banner or logo image upload fields, try to upload an image in JPEG format (.jpg), AND/OR
- In either the banner or logo image upload fields, try to upload an image exceeding 256k
- select "save"

Resulting Error
- Page reloads without uploading the image. no warning message or indication of the failure to upload is received.

Expected Result
User should receive a warning message informing them that the upload has not succeeded.

IDEALLY this could be done with some kind of JavaScript validation to provide specific feedback - if the image is not in PNG format, the user is reminded to select an image in the correct format. If the image exceed 256K, the user is reminded of the size limits and recommended dimensions. IF BOTH the format and the file size are wrong, then the user is supplied with both messages.


Related issues

Related to Access to Memory (AtoM) - Bug #5217: Institutional Edit Theme page: a logo or banner cannot be... Won't fix 06/10/2013

History

#1 Updated by Jesús García Crespo about 9 years ago

  • Target version changed from Release 2.0 - interim 1 to Release 2.0.0

#2 Updated by Jesús García Crespo almost 9 years ago

  • Estimated time set to 2.00

#3 Updated by Jesús García Crespo over 8 years ago

  • Assignee changed from Jesús García Crespo to José Raddaoui Marín

#4 Updated by José Raddaoui Marín over 8 years ago

  • Status changed from New to QA/Review
  • % Done changed from 0 to 100

I couldn't manage to show both errors at the same time, but showing one error should be good enough.

#5 Updated by Dan Gillean over 8 years ago

  • Status changed from QA/Review to Verified

I would love in the future if we could use some in-page JavaScript validation on this, so it doesn't have to reload, with multiple detailed error messages possible... but this totally works. Marking verified. Thanks Radda!

Also available in: Atom PDF