We are updating Moodle from 3.0 to 3.2 and updated the attendance plugin as well. It just hangs when trying to update the mod: attendance. Help please! Can we use the attendance module that worked for Moodle 3.0?
What do you mean by 'freezes'? Can you please make sure you have developer debugging level set with display errors on and take a screenshot of the error shown?
it was in development mode, but no errors. What happens is when you click "upgrade database" because it shows available plugins, it usually scrolls through the list of things that have been successfully installled, one at a time if you are upgrading everything. It got to "mod-attendance" and just sat there on the page and didn't go to any other plugins. So we deleted attendance from the mod and blocks folder, and clicked "ugdrade database" and it quickly finished the rest. Tried to do attendance (new version) and it stuck. Installed the prior block and mod and it worked. The new block and mod worked on the test server with no problems.
make sure you have the right version of the block and the right version of the module for your Moodle version. Where did you get the updated code from? - did you grab the version from the moodle.org plugins db or did you get it from the github repositories?
Typically it won't just "hang" - there will be an error somewhere - make sure you have "display errors" On and your debugging mode set to "developer"
Got it to work. Apparently, when updating PHP it threw some warnings or errors that went unnoticed, or it was because we didn't change the permissions to all of the blocks... What fun!
great to hear you have it sorted.
FYI - the version in github has a number of new fetaures that aren't in the version released in the plugins db. In particular the new at-risk reports/warnings etc. These features are still under development so may change a bit more in the next couple of weeks.
Nice! Thanks!
On Thu, Jul 13, 2017 at 6:57 PM Dan Marsden (via Moodle.org) <
On Thu, Jul 13, 2017 at 6:57 PM Dan Marsden (via Moodle.org) <