Hi Alain
It is good to keep an eye on bugs in the coming 4.5 LTS. Since it is expected only in October 2024, what you get from git.moodle.org is a 'dev' version. So massive bugs are normal. I don't think they have individual issues in the tracker.
Weeks before the release date there'll be a call for testers. That is where your contribution is needed.
Hi
I know this is a bit late, but will share it anyway. I may help the next person.
I upgraded from 4.3 to 4.4 using PHP 8.1 and received the error:
Exception - Failed opening required '[dirroot]/question/category_class.php' (include_path='[dirroot]/lib/pear:.:/usr/local/lib/php/')
I enabled full debugging and received the following:
Warning: require_once(/usr/www/users/dynale/question/category_class.php): Failed to open stream: No such file or directory in /usr/www/users/dynale/mod/booking/lib.php on line 30
Error
Exception - Failed opening required '[dirroot]/question/category_class.php' (include_path='[dirroot]/lib/pear:.:/usr/local/lib/php/')
Debug info:
Error code: generalexceptionmessage
Stack trace:
line 30 of /mod/booking/lib.php: Error thrown
line 974 of /lib/classes/component.php: call to include_once()
line 7555 of /lib/moodlelib.php: call to core_component::get_plugin_list_with_file()
line 865 of /lib/setup.php: call to get_plugins_with_function()
line 30 of /config.php: call to require_once()
line 94 of /admin/index.php: call to require()
As we were not using the Booking plugin, I simply removed it and completed the upgrade to 4.4 without further issues. I then switched to PHP 8.2 and everything is working perfectly.
@Kate
Just tested a 4.4 sandbox server: 4.4.1+ (Build: 20240802)
The command suggested to you, run from command line an in code/admin/cli/
php cfg.php --component=tool_mfa --name=enabled --set=0
Does work in setting MFA off.
and the check that it does:
php cfg.php --component=tool_mfa
debugmode 0
** enabled 0
guidance 0
guidancecontent
guidancefiles
lockout 10
redir_exclusions
version 2024042200
@All
One does not have to be logged onto the moodle GUI to update/upgrade.
php admin/cli/maintenance.php --enable
puts site in maintenance mode
php admin/cli/upgrade.php
After that completes one can turn off maint mode:
php admin/cli/maintenance.php --disable
'SoS', Ken
I know, you've "SOLVED" the issue by reinstalling. Here are a hint or two for the next time and for the others:
From your previous post, it doesn't appear you have aversion to using command line (docker - etc) but you might not yet have discovered the command line way to update/upgrade a moodle ... which I assume one can do with a docker install of the stack.
https://docs.moodle.org/404/en/Git_for_Administrators
There are some preliminary things an OP must do before pulling the trigger on any update or upgrade .. use the GUI environment check and update the component. Then use the moodle version drop down pick list for any version of moodle higher than what is installed. The resulting screens will tell you if you have the version of PHP + php extensions, DB version necessary to upgrade to that version ... not only that but PHP tweaks.
The thing moodle does NOT have is a built in plugins check - for plugins acquired from moodle.org plugins and 3rd party (which moodle can't do).
But that can be done using moosh - command line only. But there is a catch22 ... moosh will lookup plugins in the moodle.org plugins site and show the highest version available. It will not have references to 3rd party plugins ... but at least one can be reminded of the need to check those with provider before updating/upgrading.
In the case of H5P ... started as an addon ... then became part of core. Thus confusion.
The 'traditional' method of updating or upgrading a moodle has too many moving parts. Best to use git versioning as that allows one to leave the moodle code directory in place and git pulls in what is needed - makes changes to files that need changing - etc.
Plus, as long as one is at the CLI, one can finish the upgrade via command line ... thus taking any potential issues with config of web server that sits atop ... or any WAF that sits in front. It's just your compatible php-cli talking to the DB server then.
So when building your Docker, could you acquire the moodle code via git? If so, updating/upgrading becomes much easier.
'SoS', Ken
'weekends' ... ya know, perhaps the worst time to have issues ... forums are delayed anyway ... and most folks are sane and do take time off and away from 'moodle madness'!
Other thread ... this one?
https://moodle.org/mod/forum/discuss.php?d=460859#p1850739
And another link:
https://docs.moodle.org/404/en/Administration_via_command_line
Section on "List and uninstall Moodle plugins"
'SoS', Ken
Devils are in details!
Just making sure ... closed or not closed:
https://moodle.org/mod/forum/discuss.php?d=460957#p1851013
Also on 12 August 2024 as part of the master-to-main migration initiative, the master branch is planned to be removed from all Moodle repositories and mirrors after the next minor release, which is scheduled for 12 August 2024. Please make sure to move any dependability on the master branch to the main branch.
Noticed in your posting:
https://moodle.org/mod/forum/discuss.php?d=460827#p1850746
It showed 'master'.
'SoS', Ken
Well, it is Monday morning where Moodle grows. So I ran a sync in a copy. Nothing dangerous happened. Maybe the origin/MOODLE_XYZ_STABLE notation isolates us from the master's name change.
$ git pull
remote: Enumerating objects: 2564, done.
remote: Counting objects: 100% (1689/1689), done.
remote: Compressing objects: 100% (46/46), done.
remote: Total 2564 (delta 1623), reused 1684 (delta 1623), pack-reused 875
Receiving objects: 100% (2564/2564), 702.87 KiB | 4.23 MiB/s, done.
Resolving deltas: 100% (1862/1862), completed with 608 local objects.
From git://git.moodle.org/moodle
7f450dcea36..aea9770cfc7 MOODLE_401_STABLE -> origin/MOODLE_401_STABLE
efce12bb63d..62c1f37d409 MOODLE_402_STABLE -> origin/MOODLE_402_STABLE
431f27e7bfc..fcf23db6be0 MOODLE_403_STABLE -> origin/MOODLE_403_STABLE
e0381615aa0..cc2edf3b8cc MOODLE_404_STABLE -> origin/MOODLE_404_STABLE
8a6e8563fdc..a75365f2e47 main -> origin/main
8a6e8563fdc..a75365f2e47 master -> origin/master
* [new tag] v4.1.12 -> v4.1.12
* [new tag] v4.2.9 -> v4.2.9
* [new tag] v4.3.6 -> v4.3.6
* [new tag] v4.4.2 -> v4.4.2
Updating 7f450dcea36..aea9770cfc7
Fast-forward
admin/settings/security.php | 3 +-
.../new_table_from_mysql.class.php | 30 ++++++-----
backup/moodle2/backup_block_task.class.php | 2 +-
backup/util/ui/renderer.php | 20 ++++----
badges/index.php | 3 +-
filter/tex/lib.php | 2 +-
filter/tex/tests/lib_test.php | 1 +
.../get_enrolled_users_for_search_widget.php | 10 +++-
grade/report/singleview/renderer.php | 11 +++-
grade/report/user/renderer.php | 15 ++++--
grade/report/user/tests/behat/usersearch.feature | 19 +++++++
h5p/templates/h5perror.mustache | 6 +--
lib/accesslib.php | 9 ++--
lib/amd/build/localstorage.min.js | Bin 590 -> 631 bytes
lib/amd/build/localstorage.min.js.map | Bin 2578 -> 2787 bytes
lib/amd/build/storage_validation.min.js | Bin 0 -> 788 bytes
lib/amd/build/storage_validation.min.js.map | Bin 0 -> 1734 bytes
lib/amd/build/storagewrapper.min.js | Bin 1775 -> 1832 bytes
lib/amd/build/storagewrapper.min.js.map | Bin 6992 -> 7203 bytes
lib/amd/src/localstorage.js | 9 ++++
lib/amd/src/storage_validation.js | 37 +++++++++++++
lib/amd/src/storagewrapper.js | 9 ++++
lib/blocklib.php | 3 +-
lib/classes/plugininfo/block.php | 8 ++-
lib/db/upgrade.php | 16 ++++++
lib/filelib.php | 15 +++++-
lib/outputrequirementslib.php | 5 +-
mod/feedback/show_nonrespondents.php | 38 +++++---------
.../tests/behat/forum_one_discussion_type.feature | 57 +++++++++++++++++++++
.../backup/moodle2/restore_glossary_stepslib.php | 3 ++
.../report/grading/tests/behat/grading.feature | 9 ++--
question/type/calculated/questiontype.php | 11 ++--
version.php | 4 +-
33 files changed, 267 insertions(+), 88 deletions(-)
create mode 100644 lib/amd/build/storage_validation.min.js
create mode 100644 lib/amd/build/storage_validation.min.js.map
create mode 100644 lib/amd/src/storage_validation.js
create mode 100644 mod/forum/tests/behat/forum_one_discussion_type.feature
Now $release = '4.1.12 (Build: 20240812)'.
Could be ...
the master branch is planned to be removed from all Moodle repositories and mirrors after the next minor release, which is scheduled for 12 August 2024. Please make sure to move any dependability on the master branch to the main branch.
Today is Aug. 11 US Central Daylight ...
Above says Aug. 12 - Switzerland it's about 2 AM now.
In your git pull on a copy:
8a6e8563fdc..a75365f2e47 main -> origin/main
8a6e8563fdc..a75365f2e47 master -> origin/master
That looks the same.
What does git branch -a
show at the top?
Just checkin'
Did updates yesterday ... Aug. 10 .... and the update to a 4.1.x shows 4.1.12 (Build: 20240812)
'SoS', Ken
'SoS', Ken
$ grep release version.php
$release = '4.1.11+ (Build: 20240802)';
$ git branch
MOODLE_31_STABLE
MOODLE_32_STABLE
MOODLE_33_STABLE
MOODLE_35_STABLE
MOODLE_38_STABLE
MOODLE_39_STABLE
* MOODLE_401_STABLE
master
$ git pull
[output as posted in my previous post]
$ grep release version.php
$release = '4.1.12 (Build: 20240812)';
$ git branch
MOODLE_31_STABLE
MOODLE_32_STABLE
MOODLE_33_STABLE
MOODLE_35_STABLE
MOODLE_38_STABLE
MOODLE_39_STABLE
* MOODLE_401_STABLE
master