Différences

Ci-dessous, les différences entre deux révisions de la page.

--- start:overrides [2026/02/08 19:27] – [Customcripts] admin
+++ start:overrides [2026/02/08 21:23] (Version actuelle) – [Customcripts] admin
@@ Ligne 36: / Ligne 36: @@
    $CFG->customscripts = '<moodlepath>/customscripts';
-In your config file, then any request to a php script say: ''https://<mymoodle>/a/b/c.php'' that encounters an existing file names '/customscripts/a/b/c.php' will be derouted at end of the ''setup.php'' initialisation to that file, includes the file, then continue normal processing.
+In your config file, then any request to a php script say: ''https:<nowiki>//</nowiki><mymoodle>/a/b/c.php'' that encounters an existing file named ''/customscripts/a/b/c.php'' will be derouted at end of the ''setup.php'' initialisation to that file, includes the file, then continue normal processing.
+Customscripts MUST NOT include ''config.php'', because it has already be done before routing to customscript.
+By ending the customscript by a ''die()'' or ''exit()'', the customscripted script REPLACES the standard behaviour.
+Customscripts MUST NOT redefine classes, functions or any "compilation time definitions", as the standard version has already be loaded into memory.
+===Good cases===
+Customscripts work fine when the change is very superficial, and resides in the moodle page itself (vs. a deeper library).
+===Less good cases===
+When the change is deeper, customscripting will force you to deroute deeper calls to derouted APIs, so the code path may need a lot of work to reach the changing point.
+Too complicated derouting will lead to replacing a LOT of standard code. As the standard code is occulted in your Moodle, it will not reveal upgrades or bugfixes, so your replaced code will diverge slowly from moodle standard state of the art. this can be problematic.
 ====Core patchs====