by Alexander Urban.
Thank you very much for the hint with "noemailever=true"! This is very valueable!
I already use git for updating. But there is one quirk: "git pull" won't work but "git merge". I think this is the case since I upgraded from Moodle 3.x to Moodle 4.x
Do you have some hints for handling plugins during upgrades? I think I installed too much plugins on request for my users and now I see some plugins won't be ported to newer moodle versions by the maintainers any more.
One reason I set up the testing instance is checking the behavior of the plugins after the upgrade.
So my current moodle is 4.3.12 and I now want to upgrade to 4.5 and from now on stick to LTS-Versions. I chose 4.3 because we really wanted a plugin that was not available in the LTS back then.
I already use git for updating. But there is one quirk: "git pull" won't work but "git merge". I think this is the case since I upgraded from Moodle 3.x to Moodle 4.x
Do you have some hints for handling plugins during upgrades? I think I installed too much plugins on request for my users and now I see some plugins won't be ported to newer moodle versions by the maintainers any more.
One reason I set up the testing instance is checking the behavior of the plugins after the upgrade.
So my current moodle is 4.3.12 and I now want to upgrade to 4.5 and from now on stick to LTS-Versions. I chose 4.3 because we really wanted a plugin that was not available in the LTS back then.