Moodle has many text filters for replacing text, some are built in (Site Admin > Plugins > Filters) and others are available as plugins: https://moodle.org/plugins/?q=type:filter
I suspect the Generico filter might do what you mention.
Additionally, the URL resource allows you to add variables to a web address.
I'm trying to modify the functionality of the existing auth_email plugin (email based self registration) The only change in functionality is to send an additional email to users who are based in a certain area based off their IP Addresses. We made these modifications and then when tested it on our local MAMPserver it passes the checks. But when we upgrade the database it breaks the site administration completely. Could something be wrong with the settings.php? Does anyone know what could have caused this? Also not happy with this approach, it would be better if we could build on top of the plugin, does anyone know a better route to take?
yes I still want to keep the original one running, with a different URL, but I have to duplicate another directory for archived access in the local server, because the index.php in the primitive directory is now used to redirect URL to the one on the cloud (different URL definitely). Thing is, now I have 2 folder of Moodle web content, but using the same moodledata and database, the second one throws the above exception, not sure if this happens on Linux too.
The way you have 2 setups sharing DB and moodledata would also make Linux confused.
My guess is moodledata is very large and that's why both instances are using same moodledata (a no-no). Only way to avoid issues, 2 separate/unique FQDN's.
The only way to keep old site accessible with no issues in production site is to separate completely ... each has own code, own moodledata and own DB. DNS comes into play.
If my guess was correct, attach a drive to the server with enough room to old the data directory for the old moodle site. Plus use a different DB for each.
'spirit of sharing', Ken
Enter the Product Key for Office Setup, after purchasing Office sign into your www.office.com/setup account. It is the best service provieding in 24 * 7 hours support. For more information visit us.
Hello again,
I dug our Moodle installations and I think that for some reason (Installatron) update did not update Course overview-block.
I did a clean new install and version 3.62 Course overview-block works ok BUT, on our other 3.62 Moodle setups the Course overview is not working. (And it is "the old model". One can tell it from the Timeline/Courses Tabs.)
I have checked enrollments and completion progress but the situation continues...
I can not see course listing on the (new) Course Overview. -Timeline-tab works, but only if "Sort by Dates". "Timeline Sort by courses" does not show anything.
We have two separate Moodle-setups ( Moodle 3.6.2 (Build: 20190114)) and the problem is on both. (I have not really used older version of the course overview-block, but I did remember that I have seen the doughnut-icon for the completion %, so it probably worked before recent update(s). )
- Courses-block shows the course listing OK
- My Courses (lw_courses) shows courses OK
- New Course Overview -block...NO COURSES ???
Anyone else have the same problem after recent updates?
Regards,
-Antti P-
you must make a dump, modify the sql (replace latin ou utf8 by utf8mb4 with notepad++ by example) then restore the base with bigdump
upgrading from 3.6.1 to Moodle 3.6.2+
message to modify in utf8 :
ok, I do it.
All my tables are in uft8mb4 :
Table  | Action | Lignes | Type | Interclassement | Taille | Perte | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| mdl_analytics_indicator_calc | | Afficher | Structure | Rechercher | Insérer | Vider | Supprimer | 61 | InnoDB | utf8mb4_general_ci | 48 Kio | - | |
| mdl_analytics_models | | Afficher | Structure | Rechercher | Insérer | Vider | Supprimer | 2 | InnoDB | utf8mb4_general_ci | |||
The message stay and impossible to continue the upgrade
Any idea ?
Thank's
Switch from general to unicode...
ok
I do it
thank's
moodle 3.6.2+
A new problem.
Impossible to save or restore a curse :
message : "Erreur d'exécution DDL sql"
Any idea ?
Thank's for your help
Hello Friends,
I am trying to switch my Moodle web front-end server from Windows to RedHat. During the configuration of Apache, by default, it loads all the Apache modules when Apache starting up. I would like to only load the Apache modules that I need to support the Moodle v3.5 application. I did ask Mr. Google, but I have not found any useful information.
Would you please let me know what Apache modules are needed to be loaded to support Moodle v3.5?
BTW, I am running RedHat v7.5, PHP 7.1 & Apache v2.4.34
Thank you for your assistances!
Cal
Turn on full developer debugging and see what the full error message says...
Purpose is to reduce the footprint?
How much memory does your server have?
Is your server an 'all-in-one' where DB server to be on same physical server? If so, install mysqltuner.pl.
https://docs.moodle.org/36/en/Apache
Slasharguments ... Acceptpath Info which is on by default.
And mod_ssl
IF using Solr search then solr.
In this:
https://haydenjames.io/strip-apache-improve-performance-memory-efficiency/
comments one can see others who have shared minimals.
All will say ... depends ... sooooooo ... ditto! which relates to questions asked above.
'spirit of sharing', Ken
no change...
But the problem was in the config.php file.
I let the old one : 'dbcollation' => 'utf8mb4',
instead of the new one :
'dbcollation' => 'utf8mb4_unicode_ci',
So problem solved.
Thank's for your help
here the message :
Erreur d'exécution DDL sql
any idea about the error ?
Hi Team,
We have recently upgrade the moodle server 3.6.but we found vulnerability in moodle server.
Please find the below vulnerability for your reference.
1.
| Cross-site
request forgery (CSRF) vulnerability in report/overview/report.php in the
quiz module in Moodle before 1.8.13 and 1.9.x before 1.9.9 allows remote attackers to hijack the authentication of arbitrary users for requests that delete quiz attempts via the attemptid parameter. |
2.
| Cross-site
scripting (XSS) vulnerability in Moodle before 1.6.8, 1.7 before 1.7.6, 1.8
before 1.8.7, and 1.9 before 1.9.3 allows remote attackers to inject arbitrary web script or HTML via a Wiki page name (aka page title). |
| 3. Cross-site scripting (XSS) vulnerability in the MNET access-control interface in Moodle before 1.8.13 and 1.9.x before 1.9.9 allows remote attackers to inject arbitrary web script or HTML via vectors involving extended characters in a username. |
| 4. Multiple cross-site scripting (XSS) vulnerabilities in blog/index.php in Moodle before 1.8.13 and 1.9.x before 1.9.9 allow remote attackers to inject arbitrary web script or HTML via unspecified parameters. |
Please suggest the solution for resolve the issue
Did you read the Moodle versions these reports apply to?
Why do you assume that reports from ancient versions of Moodle would still apply to 3.6?
Check your directory conf.modules.d in your Apache root folder, there you'll find a file like 00-base.conf where you can find the modules that are loaded by Apache. You'll probably see some more conf files that load other modules that are needed. The modules itself you can find in the modules folder.
