Bug #2903
Wrong corpus access error message when opening a command
Statut: | New | Début: | 06/10/2020 | |
---|---|---|---|---|
Priorité: | Normal | Echéance: | ||
Assigné à: | - | % réalisé: | 0% |
|
Catégorie: | Corpus | Temps passé: | - | |
Version cible: | 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
Historique
#1 Mis à jour par Serge Heiden il y a presque 5 ans
- Description mis à jour (diff)
#2 Mis à jour par Matthieu Decorde il y a presque 5 ans
- Version cible changé de Portal 0.6.3 à Portal 0.7