Bug #2903
Wrong corpus access error message when opening a command
Status: | New | Start date: | 10/06/2020 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% |
|
Category: | Corpus | Spent time: | - | |
Target version: | Portal 0.7 |
Description
The current '500 error' message is not informative.
Commands using a CQL query as an argument, produce a message "La requête CQL est mal formulée : \nFailed to get properties" which is misleading, and may cause the user to indefinitely search for a CQL expression that works (and that cannot be found).
Solution¶
- If the corpus is not accessible the command must not open its interface
- change the error message to explicitly tell : the corpus is not available and the admin must be contacted
History
#1 Updated by Serge Heiden over 2 years ago
- Description updated (diff)
#2 Updated by Matthieu Decorde over 2 years ago
- Target version changed from Portal 0.6.3 to Portal 0.7