The explore page presently does not show error messages when content loading and filtering does not work. For example, on the Isis CB instance, the following URLs return HTTP 500 errors:
However, the status bars for loading instances or the conceptFilter do not change.
To fix this, the calls to jQuery.get() on lines 124 and 149 in app/views/content/index_content.scala.html need to add a .fail() handler to change the progress bar to red with an appropriate message, like the Topic Explorer does on lines 382-391 and 396-400 of index.html. The Topic Explorer uses calls to d3.json() so the syntax will be different for error handling.
The explore page presently does not show error messages when content loading and filtering does not work. For example, on the Isis CB instance, the following URLs return HTTP 500 errors:
However, the status bars for loading instances or the conceptFilter do not change.
To fix this, the calls to
jQuery.get()on lines 124 and 149 in app/views/content/index_content.scala.html need to add a.fail()handler to change the progress bar to red with an appropriate message, like the Topic Explorer does on lines 382-391 and 396-400 of index.html. The Topic Explorer uses calls tod3.json()so the syntax will be different for error handling.