Hi Rick,
Thak you for your answer.
We solved the problem. The vimeo link inserted in the Rise must contain "player".
Example: "https://player.vimeo.com/video/00000000"
Can re-call having issues with 2.x -> 3.0.x upgrades due to this.
fgrep 'dbcollation' ./moodle30/config-dist.php
returns nothing
note that's 3.0.x
Beginning 3.1 ...
fgrep 'dbcollation' ./moodle3?/config-dist.php
./moodle31/config-dist.php: 'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
./moodle32/config-dist.php: 'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
./moodle33/config-dist.php: 'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
./moodle34/config-dist.php: 'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
./moodle35/config-dist.php: 'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
./moodle36/config-dist.php: 'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
./moodle37/config-dist.php: 'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
./moodle38/config-dist.php: 'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
./moodle39/config-dist.php: 'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
So, as it was pointed out, it looks like utf8mb4_unicode_ci is correct and should be the 'standard' now.
Comments on that line in config-dist.php
"'dbcollation' => 'utf8mb4_unicode_ci', // MySQL has partial and full UTF-8
// support. If you wish to use partial UTF-8
// (three bytes) then set this option to
// 'utf8_unicode_ci', otherwise this option
// can be removed for MySQL (by default it will
// use 'utf8mb4_unicode_ci'. This option should
// be removed for all other databases.
Hmmmm ... is default for MySQL still latin and latin_swedish_ci?
https://dev.mysql.com/doc/refman/8.0/en/charset-applications.html
default MySQL character
set and collation (utf8mb4,
utf8mb4_0900_ai_ci)
https://dev.mysql.com/doc/refman/5.7/en/charset-applications.html
default MySQL character
set and collation (latin1,
latin1_swedish_ci)
'SoS', Ken
Dear,
We upgrade Moodle from 3.6 to 3.8.3 on August. However, we find the ser sometimes down and both attached error message is shown. Do you any hints. Is it related to Moodle 3.8 bug?. I find it can be resumed only after restart apache service.
Our server environment setting
OS: Redhat 7.8
PHP version: 7.3.19
MySQL: 5.7.22
Apache: 2.4.33
Moodle version 3.8.3
Hi, I hope someone will find this helpful to someone. I went to moodle/config.php and changed mysqli to mariadb and it worked. If you had issues with php extensions you must go to php.ini and remove comments on the extensions you want.
Hope this helps.
Note: you must have access to these files as administrator not on cpanel. If you are not adminstrator ask the adminstrator to do it for you.
Hi !
I want to run an external script using moodle/config.php. I included moodle/config.php in the external script as soon as I access the external script it sends 303 error code and redirects me to dashboard. What can be the possible issue
moodle version : 3.7
php version : 7.2.3
Hello,
I've been following this post, i'm runing moodle 3.9.2 and have the same problem! But still having it...
I folow all the steps that were mencioned here:
1. purge all caches
2. checked the database, and didn't found the line quizaccess_safebrowser
3. On my files under /mod/quiz/accessrule i have just this:
and under quiz / access rules have this
any ideas?
Kind Regards
Ricardo
For point 3., are you certain this is the correct folder for the Moodle site? E.g. if the site address is www.example.com/moodle what do you get if you go to www.example.com/moodle/mod/quiz/accessrule/safebrowser?
You should get 404 Not Found, but if you get 403 Forbidden – or a directory listing – then that indicates quizaccess_safebrowser is still present.
All
Until lately, I was unable to resolve an issue upgrading to latest moodle due to definition of admin account in config.php (see https://tracker.moodle.org/browse/MDL-69061)
Post upgrading (which was successful) I am getting duplicate entries in the database with errors on our site homepage:
Error: mdb->get_record() found more than one record!
This is very likely a result of some failure to merge
Anyone know how best to deal with these duplicate entries?
I have used Moodle as an instructor for an organization that hosted the moodle server. That organization is shifting away from the moodle platform, so I need to "park" my existing moodle class/back up on my own computer. I have a mac computer, and I have downloaded moodle from the link on the moodle.org site, and I have dropped the MMAP folder to my Applications folder as instructed here: https://docs.moodle.org/39/en/Installation_Package_for_OS_X , but when I proceed to the next step in the installation instructions, which is "Step 5: Double click the MAMP icon to start the server," I get the following error message: “MAMP” cannot be opened because the developer cannot be verified.
macOS cannot verify that this app is free from malware. Chrome downloaded this file today at 7:13 PM from download.moodle.org."
It is unclear to me how to proceed. (And again, the only reason I'm going through all of this is so that I can have a way to "park" the back up of my class site, so I don't lose all of the work I've put into building this class. I'm not currently planning to "run" a class from my own server, but I do want to visually check/verify that the backup that I've made is a functional backup that I could use in the future--via Moodle Cloud, or via another host organization that uses Moodle, etc). Thanks in advance for any help you can provide. Dawn Prochovnic
This reply may help. It looks like something which should never happen has happened.
I solved it by dumping the data separate from the structure and then did some awk magic to change the collation, reimported the new structure and then the data onto it.
This will ofc have the downside of forcing a downtime(in our case a few hours for a very large moodle site.
Take a backup of the database first.
Then run SELECT * FROM mdl_registration_hubs and save the results, e.g. using Notepad, as that's the easiest way to retrieve the data.
Then decide which entry you want to keep and note the id column of this. Maybe it's obvious that one is "correct" or maybe you'll just need to pick one at random. I don't think there are any serious repercussions to getting this wrong.
Then run the DELETE statement substituting the id number with the one you want to keep, e.g. if you want to keep id 1:
DELETE FROM mdl_registration_hubs WHERE id <> 1;
Hopefully the issue will now be resolved.
Hello,
When i try that i get a 404!