You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When downloading a workflow (wf) that uses a category trigger the upload can not handle unknown categories.
The .XML file uses the id of the categories to identify the categories to be used. When this ID is not allocated in the system e.g.
throws Call to a member function get_all_children_ids() on bool .
To the best of my knowledge, the most reasonable behavior would be to either
a) delete the category trigger completely during the upload process.
b) replace the category with some random category
and provide a warning to the user.
I am not completely happy with both options but I guess implementing a category selection option during the upload process is overkill.
The text was updated successfully, but these errors were encountered:
I think this issue can also appear if you delete a category (that has already been emptied) whilst the process of backup and delete in a category trigger is still ongoing. Then, at a certain point, this hits.
When downloading a workflow (wf) that uses a category trigger the upload can not handle unknown categories.
The .XML file uses the id of the categories to identify the categories to be used. When this ID is not allocated in the system e.g.
moodle-tool_lifecycle/trigger/categories/lib.php
Line 79 in 38d6dc7
throws
Call to a member function get_all_children_ids() on bool
.To the best of my knowledge, the most reasonable behavior would be to either
a) delete the category trigger completely during the upload process.
b) replace the category with some random category
and provide a warning to the user.
I am not completely happy with both options but I guess implementing a category selection option during the upload process is overkill.
The text was updated successfully, but these errors were encountered: