by Rodrigo Antonio Meléndez Morales.
Works! Thank you!
↧
Re: Students can see "Add an activity or resource" after upgrading 3.11+
↧
Re: Fatal error during Moodle upgrade
by John Chan.
It works! Thank you very much.
↧
↧
Re: Fatal error during Moodle upgrade
by John Chan.
The config-dist.php of our Moodle ver. 3.8.9 includes this statement 'dbhandlesoptions'=>false .I haven't changed anything.
↧
Re: 3.11 upgrade and activity completion not working
by Steph Dickinson.
Hi,
Thanks Howard, yes tried that, all running well. All system checks are saying there are no errors but the activity completions are just not generating when everything previously was working in 3.9.7 and no changes made post upgrade. Do you have any suggestions or has anyone heard of any similar issues?
Thanks Steph
↧
An appropriate representation of the requested resource could not be found on this server. This error was generated by Mod_Security.
by Karlo Ian Cabanal.
Good day,
I would like to ask regarding the
An appropriate representation of the requested resource could not be found on this server. This error was generated by Mod_Security.
This error appears in my user page. every time I click the add or edit the user.
Thank your very much. Looking forward if someone have already resolve this problem.
↧
↧
Re: 3.11 upgrade and activity completion not working
by Howard Miller.
Sometimes I have seen completion get "stuck". Go to the completion settings screen and 'clear' the current completions. My suspicion would still be on cron after that. I would run the completion task manually and very carefully check the output.
↧
Re: An appropriate representation of the requested resource could not be found on this server. This error was generated by Mod_Security.
by Howard Miller.
Sounds like you had quite a comprehensive answer?
↧
Re: Fatal error during Moodle upgrade
by Leon Stringer.
Ken: Re 'dbhandlesoptions': This looks like a PostgreSQL-specific option where some database options are stored by the database server. The external database logstore also makes use of this functionality:
Possible bug: searching admin settings doesn't show this option (on 3.9 at least).
↧
Re: Moodle 3.8 Installation Error for PHP has not been properly configured with the MySQLi extension
by Tien Do.
Thank you for your answer! You save my time a lot
↧
↧
Re: 3.11 upgrade and activity completion not working
by Rick Jerz.
In Moodle 3.11, Activity Completion changed a little. Steph, you say activity "completion is not working" but I am not exactly sure what you are seeing that makes you say "is not working." I have been making and following some posts about the newer Activity Completion, (this one post provides links to some of my others,) and I wonder if your problem might have something to do with your theme, possibly a plugin, or maybe just some settings that 3.11 changed or added. I might be far off from the problem, but I just wanted to mention the changes just in case it helps you.
↧
upgrading moodle from 3.7 to 3.11
by murugan m.
moodle 3.7
My site is running on moodle 3.7, Can I straightly upgrade to moodle 3.11?
My thanks in advance.
Murugan.M
↧
Re: upgrading moodle from 3.7 to 3.11
by Howard Miller.
Take a look at the release notes...
https://docs.moodle.org/dev/Moodle_3.11_release_notes#Server_requirements
Minimum Moodle version is 3.6, so you're fine. Keep reading and make sure you meet all the other requirements!
https://docs.moodle.org/dev/Moodle_3.11_release_notes#Server_requirements
Minimum Moodle version is 3.6, so you're fine. Keep reading and make sure you meet all the other requirements!
↧
Re: 3.11 upgrade and activity completion not working
by Steph Dickinson.
Thanks Rick, I think we may have found the problem, I think the default settings for the activity completion changed in the upgrade. Our SCORMs activity completion settings were locked (to protect data retention) so we were unable to open and see the settings in the LMS.
Thanks for your advice.
↧
↧
Upgrade 3.10 to 3.11 why are there changes to commit?
by Michael Knichel.
I am trying to upgrade to 3.11 from 3.10. I have a script that I use and it returned the following:
error: Your local changes to the following files would be overwritten by merge:
.eslintignore
.stylelintignore
.travis.yml
Gruntfile.js
admin/tool/oauth2/issuers.php
admin/tool/oauth2/lang/en/tool_oauth2.php
config-dist.php
Please commit your changes or stash them before you merge.
Aborting
So .eslintignore and the other files seem to have changes that need to be committed? Not sure why/how as I never edited these files.
Can I simply do a git add * then git commit and then restart the upgrade?
MK
↧
Re: Upgrade 3.10 to 3.11 why are there changes to commit?
by Ken Task.
?? your script looks like?
best to do a git pull and update prior to upgrading.
in a 3.10 git pull
Updating 2d7386420cb..10daae7ab70
Fast-forward
.eslintignore | 95 -------------
.gitignore | 2 +
.stylelintignore | 96 -------------
.travis.yml | 2 +-
Gruntfile.js | 5 +-
admin/category.php | 5 +
admin/tool/oauth2/issuers.php | 6 +
admin/tool/oauth2/lang/en/tool_oauth2.php | 1 +
config-dist.php
in a git pull of 311
Updating 70f99ddd9a6..0e64d1d00d0
Fast-forward
.eslintignore | 96 ----------------------------------------------
.gitignore | 2 +
.grunt/tasks/javascript.js | 5 ++-
.grunt/tasks/style.js | 3 ++
.grunt/tasks/stylelint.js | 3 +-
.stylelintignore | 96 ----------------------------------------------
.travis.yml | 2 +-
config-dist.php | 2 +-
course/renderer.php | 6 +++
install/stringnames.txt | 1 +
repository/filepicker.js | 6 +++
version.php | 4 +-
12 files changed, 28 insertions(+), 198 deletions(-)
delete mode 100644 .eslintignore
delete mode 100644 .stylelintignore
'sos' ken
↧
Re: Upgrade 3.10 to 3.11 why are there changes to commit?
by Michael Knichel.
Thanks for the reply. Here is what a git pull does...
git pull
Updating 237f4ccada7..10daae7ab70
error: Your local changes to the following files would be overwritten by merge:
.eslintignore
.stylelintignore
.travis.yml
Gruntfile.js
admin/tool/oauth2/issuers.php
admin/tool/oauth2/lang/en/tool_oauth2.php
config-dist.php
Please commit your changes or stash them before you merge.
Aborting
My question still remains, why are there changes in the files on my system? I didn't edit them...
MK
git pull
Updating 237f4ccada7..10daae7ab70
error: Your local changes to the following files would be overwritten by merge:
.eslintignore
.stylelintignore
.travis.yml
Gruntfile.js
admin/tool/oauth2/issuers.php
admin/tool/oauth2/lang/en/tool_oauth2.php
config-dist.php
Please commit your changes or stash them before you merge.
Aborting
My question still remains, why are there changes in the files on my system? I didn't edit them...
MK
↧
Re: Upgrade 3.10 to 3.11 why are there changes to commit?
by Ken Task.
Been my experience that files do not change themselves.
My response was to show that git does remove files and updates some on a git pull in test directories of a 3.10 and a 3.11. Please look again as those did show some of the files your system is reporting as changed in your 3.10 and suggesting a merge should have already been there - like config-dist.php
./moodle310/version.php:$release = '3.10.4+ (Build: 20210617)';// Human-friendly version name
./moodle311/version.php:$release = '3.11+ (Build: 20210617)';// Human-friendly version name
Asked if we could see your script?
The original installation of your 3.10.x was done with what git commands? Did you use a -b?
So what version do you have at present?
fgrep '$release' version.php
SoS, Ken
↧
↧
Re: Topics bulk upload with date and time
by Luis Alford.
↧
Re: Upgrade 3.10 to 3.11 why are there changes to commit?
by Ken Task.
in a 3.10 git pull (mine)
Updating 2d7386420cb..10daae7ab70
git log --oneline |grep 2d7386420cb
git log --oneline |grep 2d7386420cb
2d7386420cb weekly release 3.10.4+
Yours
git pull
Updating 237f4ccada7..10daae7ab70
git log --oneline |grep 237f4ccada7
237f4ccada7 Moodle release 3.10.4
see the difference .. its suttle
sos, ken
↧
Admin cannot login after migrating to new server
by Karishma Tiwari.
I am using Moodle 3.5 and earlier today we had just migrated our Moodle from IP A to IP B in a new server.
Our DNS pointing is setup, I have done search & replace of the DB.
My login page looks perfect but I cannot login! I changed the password on CLI & verified the user exists in DB.
Then out of curiosity I opened the config.php and enabled these lines (originally they are commented out):
@error_reporting(E_ALL | E_STRICT); // NOT FOR PRODUCTION SERVERS!
@ini_set('display_errors', '1'); // NOT FOR PRODUCTION SERVERS!
$CFG->debug = (E_ALL | E_STRICT); // === DEBUG_DEVELOPER - NOT FOR PRODUCTION SERVERS!
$CFG->debugdisplay = 1; // NOT FOR PRODUCTION SERVERS!
To my surprise I am able to login now!
What is the issue here and how can I fix this? Every time I comment these lines I lose login access to my Moodle site!
I have another working Moodle site, and through the browser developer tools I see that every time login, there is a token generated in the back-end.
However through this login (debug enabled), there is not token generated.
Please someone help!!
↧