Hi, I work for a Moodle partner and wanted to raise a concern we and our customer had regarding a recent Moodle upgrade to version 3.5.2 and it's affect on the Mobile app. I would log this on the Moodle Mobile Tracker however this cannot be replicated on other platforms. This is why I'm hoping someone may be able to provide some advice or shed some light on this. I have scoured the Moodle Tracker but can see no similar issues to this.
After upgrading the Moodle platform to version 3.5.2 the Feedback activity when using Multiple Choice question type (specific "type" setting on - Multiple choice - single answer). When a user tries to submit a Feedback activity that contains one or more of these question types, upon clicking Submit, the page simply reloads (normally it would load a message confirming the submission). The answers in the multiple choice are not saved (any info in text fields is) BUT in the submissions area the response is under Non-respondents and the status is "started" as if it saves a draft version of this feedback submission. It works/submits fine on on the web interface.
Now, interestingly, this ONLY occurs:
- ONLY occurs on their existing courses (not on new test course on their server)
- Happens on EITHER the official mobile app AND their custom branded app
- Does NOT happen on other servers
- ONLY happens with multiple choice question types
The only available solution is to manually alter the settings for every feedback module (hundreds) for every multiple choice question type, save the settings then change the setting back and save it again. This way it then works on the mobile app.
Has anyone experienced this or something similar? Can anyone provide any insight into how this could have happened? Any help or advice appreciated.
that's really weird. If it cannot be replicated in new courses or so then it probably means that some setting or DB value was "corrupted" during the upgrade.
We used to debug this kind of errors ourselves, but due to GDPR we can no longer do that. We created a guide to debug WebServices calls, you should check if the WebServices response give you any clue on what could be going on:
Hi Dani, thanks for the response We'll take a look at the link you posted.