Bug #2354
closed
Error not displayed on archive screen
Added by François ARMAND over 12 years ago.
Updated about 12 years ago.
Category:
Web - Maintenance
Description
When one action failed in the archive screen, the user does not see anything - not even an error message saying "Failed", it's just as if nothing was done, what is really disturbing.
See for example #2261.
=> error must be handle and displayed to the user.
Files
- Status changed from 8 to New
- Target version changed from 2.4.0~alpha7 to 2.4.0~beta1
- Status changed from New to 2
- Status changed from 2 to Discussion
I'm not sure this bug is entirely exact. As shown in #2588, at least some errors are displayed.
Is this bug still valid? If so, it must not be described precisely - what errors are not displayed? If not, please reject it.
- Target version changed from 2.4.0~beta1 to 2.4.0~beta2
Moving this to beta2 for now, but François your input is needed!
- Target version changed from 2.4.0~beta2 to 2.4.0~beta3
2.4.0~beta2 has been released. This ticket must be moved to 2.4.0~beta3.
- Target version changed from 2.4.0~beta3 to 2.4.0~beta4
Jonathan CLARKE wrote:
Moving this to beta2 for now, but François your input is needed!
I agree !
As this is not a blocking issue so I moved it to the next run.
- Status changed from Discussion to 2
- Assignee changed from François ARMAND to Jean VILVER
- Target version changed from 2.4.0~beta4 to 2.4.0~beta5
It seems to be working, I can produce some errors in every box in the Archives section and see the error (cf. screenshot attached).
I'm putting this ticket in Technical Review. But just in case, François can you check if everything is OK ?
- Status changed from Pending technical review to Released
That seems to be working, and so if no error are displayed at some time, it should be considered as an other bug (for ex. : "*that* action leads to an error without any error message").
- Status changed from Released to Discussion
François ARMAND wrote:
That seems to be working, and so if no error are displayed at some time, it should be considered as an other bug (for ex. : "*that* action leads to an error without any error message").
It seems that no commits were made on this ticket. Does this mean this bug was not actually a bug? If so, this ticket should be rejected, not closed. "Closed" means that this ticket will be listed as a new fix in the release notes for this version... but if nothing was changed, this is not true.
I'm almost sure there was at some point no error reporting, but I can't find what commit could have solve that. So OK for the rejected.
- Status changed from Discussion to Rejected
François ARMAND wrote:
I'm almost sure there was at some point no error reporting, but I can't find what commit could have solve that. So OK for the rejected.
Thanks for confirming, rejecting.
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by Nicolas PERRON 
Updated by Jean VILVER 
Updated by 