-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug with 'I don't know' after correct answer #43
Comments
thanks for reporting this. This is a very interesting bug which we never came across before. WIll it be possible to share the backup of the cardbox instance |
I tested this situation and couldnt recreate it. As before if this problem persists, please send us a backup of your activity(where this problem is occurring) so that we can analyse |
Thanks, @Amrita1991 - I've just tested again with the attached and the same problem occurs for me. After one (or sometimes two) correct answers, when I click 'I don't know' it still says 'Well done!' rather than the correct answers. I've also found that when I upload the attached even though 'Default settings for "How many answers are necessary?"' is set to 'one', it defaults all imported cards to 'All' meaning they have to be edited individually? |
@Amrita1991 - just following up on this to see if the bug can be fixed? The issue occurs with multeans where the 'How many answers are necessary?' setting to 'one'. Then, when you get one of these correct and then click 'I don't know' on the next card, it says 'Well done!'. This doesn't happen if ALL answers are required for the multean. I also just tested it on a fresh installation of Moodle with the latest cardbox plugin and the bug persists. |
I had a teacher reporting the same problem, so I can confirm this bug. |
The 'I don't know' button correctly displays the answers until the user has got one right and gets 'Well done!'. Following this, clicking on 'I don't know' gives 'Well done!' instead of the correct answers... see here: https://drive.google.com/file/d/1kxKXZ9f1rTKJZImQ4UFIEIKtH4sd01b3/view?usp=sharing
The text was updated successfully, but these errors were encountered: