Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2.8.3
-
Component/s: Administration
-
Labels:
-
Testing Instructions:
-
Affected Branches:MOODLE_28_STABLE
-
Fixed Branches:MOODLE_27_STABLE, MOODLE_28_STABLE
-
Epic Link:
-
Pull from Repository:
-
Pull Master Branch:
MDL-49070_scheduled -
Pull Master Diff URL:
Description
A scheduled task exists in lib/classes/task/registration_cron_task.php. The code that actually does the work is in /admin/registration/lib.php cron().
Its output if run on an unregistered site doesn't mention not being registered and probably should.
Execute scheduled task: Site registration
... started 07:25:20. Current memory use 24.1MB.
... used 4 dbqueries
... used 0.060204029083252 seconds
Scheduled task complete: Site registration
The scheduled task, having run, is now set to run again tomorrow. Within the task there is code that silently does nothing if the task has been run within the last seven days. Imposing a hard limit on how often registration is updated seems fine but it would be nice if the scheduled task didn't pretend like it was updating the registration every day.
Also, can the registration page determine if the scheduled task is enabled and output something to the UI? We don't need to tell users to manually update their registration if it will happen automatically. Also, if Moodle is "phoning home" we want to be very explicit about that.