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
Expected result: User's choice removed. Actual result: User's choice removed, along with any choices submitted by other users. Steps to reproduce:
Create an updateable choice activity
Student submits choice using app
Teacher submits choice using app
Teacher clicks Remove my choice using app
Workaround
Don't select Remove my choice if you have Teacher role or greater.
Comments
This behaviour was observed on https://moodle.bbk.ac.uk/ which is Moodle 2.8.7. The behaviour is not triggered when the choice is removed using a web browser, which suggests the bug is triggered by the app. It appears that this issue is not triggered for users with Student role, although this hasn't been rigorously tested. Example call to the web service when this issue is triggered:
This appears to be a valid API call which should delete all responses for the current user. Next step is to reproduce on dev. If the issue is present, then enable MySQL query logs to see what the generated SQL looks like.
The text was updated successfully, but these errors were encountered:
Details
Description
Expected result: User's choice removed.
Actual result: User's choice removed, along with any choices submitted by other users.
Steps to reproduce:
Remove my choice
using appWorkaround
Don't select
Remove my choice
if you haveTeacher
role or greater.Comments
This behaviour was observed on https://moodle.bbk.ac.uk/ which is Moodle 2.8.7. The behaviour is not triggered when the choice is removed using a web browser, which suggests the bug is triggered by the app. It appears that this issue is not triggered for users with
Student
role, although this hasn't been rigorously tested. Example call to the web service when this issue is triggered:This appears to be a valid API call which should delete all responses for the current user. Next step is to reproduce on dev. If the issue is present, then enable MySQL query logs to see what the generated SQL looks like.
The text was updated successfully, but these errors were encountered: