by Jeff Lewis.
Wow, Dan... With all due respect, don't you think a warning for a two-year old bug as serious as this should have been included in the plugin's documentation, so anyone downloading it was made aware of the fact that their work might get destroyed if they didn't mitigate against it?! If it had been, it would have saved me the entire day it took to restore the seventeen (17) unique, multi-paragraph, carefully composed instances of the plugin that I thought were protected by course backups.
How many others are not even aware that their course backups are meaningless in this regard... And are there other seriously damaging bugs that users aren't being properly warned about? I certainly wouldn't have known if other weirdness with this plugin (like Completion dates of 1969 popping up in testing that wouldn't correct), hadn't forced me to restore what I thought would be a clean backup free of test-accounts that I could use for further testing.
Yes, I understand the challenges of open source, and really appreciate everyone that contributes to the wonderful world of Moodle, which I contribute to as well in the ways that I can. However, it still seems quite abusive of your users' trust to simply dismiss such an issue with what appears to be your standard response (in one way or another), to reported bugs:
That's what you said two years ago in response to this bug, and what you've said again now, in so many words. By not bothering to even list this as a potential problem for new users, you literally proclaimed then, as you have now, that you just don't care if someone gets hurt by what is being falsely presented as a safe plugin to use. I'm sure all those nifty icons to the right of your name (like the one for "Particularly helpful Moodlers", or "Plugins guardians"), aren't meant to imply that!
Yes, I understand the challenges of open source, and really appreciate everyone that contributes to the wonderful world of Moodle, which I contribute to as well in the ways that I can. However, it still seems quite abusive of your users' trust to simply dismiss such an issue with what appears to be your standard response (in one way or another), to reported bugs:
"Feel free to help us work on this by submitting a pull request, otherwise we'll try to get to it at some point. Thanks!"
Of course, it would be unreasonable to do or expect this for every bug that pops up, but for bugs that could literally cost Course Creators and Administrators many hours or days of their time, there's certainly a need for protecting us from such a known issue, especially when it involves something like the integrity of course backups, don't you think?
...But that's just my humble opinion as someone who just got seriously burned by your approach to this two year-old bug.
Not appreciated!