Details
-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
Error in the UI when the task has no workflow preferences entries which can happen if the task can not be imported.
-
Empty show more show less
Description
problem
Translate5 is not usable for users assigned to a task in status error if the task was set to status error in a very early stage of import (before default userprefs were added).
reproduction
- create a task
- assign a editor user to that task
- set that task to status error
- delete the entries in LEK_workflow_userprefs belonging to that task
- login as the above used editor user
additional problem
It seems that when accessing that task a request to "/editor/log" is made, which is leading to a 403 status - since the editor user has no access to the log page.
This request is only made if the editor user is assigned to that error task. After deleting the error task no request to /editor/log is made. The question is why the request to that endpoint is made at all?
The 403 triggers a reload of the application.THIS IS WRONG! Only a 401 from the backend should trigger a reload to put the user to the login page. A 403 MUST NOT do that. Investigate that too!
solution
- ensure that the missing userprefs are not leading to an exception
- When I tested