Hi Moodle I upgraded from Moodle 3.4.2 (Build: 20180319) to Moodle 3.8.3+ (Build: 20200527). However, problems such as the following occurred. Lessons are going on right now. I need help urgently. How can I solve this problem? I use Plesk panel and Php 7.3 version is selected.
They all point to lib/completioinlib.php but different lines.
1020,1029,1036,1013 - then repeat
That file lib/completionlib.php has required lines:
require_once $CFG->dirroot.'/completion/completion_aggregation.php';
require_once $CFG->dirroot.'/completion/criteria/completion_criteria.php';
require_once $CFG->dirroot.'/completion/completion_completion.php';
require_once $CFG->dirroot.'/completion/completion_criteria_completion.php';
line 1020 of file has this:
$data['coursemoduleid'] = $cm->id;
and that line is in a section of code that gets:
// Get single record
$data = $DB->get_record('course_modules_completion',
*** and uses cache ***.
So ... think I'd try purging cache ... GUI first then manually.
contents of moodledata/cache/ and moodledata/localcache/
That's moodledata ... NOT moodle code.
Manually removing cache in moodledata is safe ... moodle will regen what it needs as site is used. Removing manually will slow site down a little while cache is being rebuilt.
Also ... is your cron/task running often enough ... has a job for completion data updating. Check those.
'SoS', Ken
"Cannot find data record in course_categories database table."
I can't run the cron web line. I made the option to run cron web browser from sql to 0. However, I still couldn't run cron. Site address as follows
https://kurs.isgakademi.net/
In addition to the good advice you are getting, also check out Plesk pages.
Plesk is a different beast ... on top of the beast you are attempting to run ... moodle 3.8.x.
https://support.plesk.com/hc/en-us/articles/115003085349-How-to-schedule-a-task-in-Plesk-for-Linux-
'SoS', Ken
Can't be. Moodle release 3.4 goes only up to PHP 7.2. https://docs.moodle.org/dev/Moodle_3.4_release_notes#Server_requirements.
However, as others are suggesting, this could be a trivial issue like wrong (old) data in the server cache. Follow their line first.