Hi all. I have a problem that I can't seem to figure out.
I have two installs of Moodle in separate locations. Both were originally installed with Softaculous in 2017. One is a clone install that is a development installation on a non-SSL address and the other is on my production SSL site.
I can upgrade the development site clone via Softaculous auto upgrade without issues. The process works as expected; request upgrade, do backup, let Softaculous do upgrade, visit admin page/notifications and verify DB upgrades, click confirmation, done. No problems. Dev site via the auto upgrade in Softaculous was running V3.7.3 (newest version available via Softaculous).
On my production site, Softaculous goes through the motions but then when I visit admin/notifications all I get is the notification that an upgrade is available and no notice that the Moodle files have changed and the confirmation of the DB upgrade. Softaculous *thinks* the site is running v3.7.3 but Moodle's upgrade check shows that it's running 3.6.1
I wanted to rule out a Softaculous issue. So, I got brave and did a manual upgrade on the development site (i.e. upload the .zip to the server, unpack, copy config.php, maintenance mode, rename folders, go to admin/notifications, confirm DB upgrade....etc....) to be sure I understood the process before potentially crashing my production site. All went as planned. Dev site is now on Moodle 3.8
Next, do same process for production site and then run into the same issue -- admin/notifications does not see the changes for some reason and doesn't trigger the DB update. I still get the same notification screen showing that Moodle is running v3.6.1 even though I manually uploaded the 3.8 package, moved the config.php from the old install, renamed the old install folder to 'classroom_old', renamed the new install to match the config.php structure of 'classroom'. So, it's not a Softaculous issue. There's something else going on. Here's a screen shot of what admin/notifications shows me AFTER the 3.8 upgrade:
Both installs are completely separate: different DBs, different web addresses, different moodledata files.
The ONLY thing that I know was altered by my host is something with the CRON jobs that weren't running on the SSL site. A tech at the host (GreenGeeks) did some magic to point the CRON job to some corrected address in the root instead of the web address that the site is actually served from. Could that CRON job edit (which functions as it should) be messing with the upgrade? If I think back, it was sometime around the time they did the CRON edit that auto upgrades stopped working as expected. Unfortunately, my host hasn't been able to help with this upgrade issue.