Sorry I've been neglecting this blog again. I'll do a proper post sometime (er I guess) but I just wanted to throw in a quick post that might be of interest to Moodle 2 developers.
Have you ever needed to test the 'restore' of a course (e.g. that includes your new module) and got annoyed because restoring involves clicking through about a million screens?
I've written a plugin that you can use to do temporary restore in one click (once you have set up the backup file you want to use). Then you can view the restored course in one click, delete it also in one click, restore it again (in, yes, one click), and repeat as much as you like while fixing bugs.
(I guess I said one click enough times that it's technically like three clicks now, but still. It's a lot better than doing the same thing manually.)
Plugin is called Broom (thanks to Tim for acronym help) because it's both fast and it also helps you keep your database clean by deleting all those courses.
New blog post
Sorry I've been neglecting this blog again. I'll do a proper post sometime (er I guess) but I just wanted to throw in a quick post that might be of interest to Moodle 2 developers.
Have you ever needed to test the 'restore' of a course (e.g. that includes your new module) and got annoyed because restoring involves clicking through about a million screens?
I've written a plugin that you can use to do temporary restore in one click (once you have set up the backup file you want to use). Then you can view the restored course in one click, delete it also in one click, restore it again (in, yes, one click), and repeat as much as you like while fixing bugs.
(I guess I said one click enough times that it's technically like three clicks now, but still. It's a lot better than doing the same thing manually.)
Plugin is called Broom (thanks to Tim for acronym help) because it's both fast and it also helps you keep your database clean by deleting all those courses.
https://github.com/sammarshallou/moodle-local_broom