customscripts: Difference between revisions
From MoodleDocs
(Created page with "==Custom Scripts Mechanism== Any scripts that are called directly via a url (eg index.php, user/view.php) can now be customised by placing a file with the same name (includin...") |
Dani Ureña (talk | contribs) mNo edit summary |
||
Line 14: | Line 14: | ||
* it seems to have been used extensively only by the [[Moodle_for_Mobiles]] project | * it seems to have been used extensively only by the [[Moodle_for_Mobiles]] project | ||
* to enable Custom Scripts, add $CFG-> | * to enable Custom Scripts, add $CFG->customscripts=path/to/customscript/folder (see [[Configuration_file]]) | ||
==References== | ==References== | ||
* http://moodle.org/mod/forum/discuss.php?d=31895 | * http://moodle.org/mod/forum/discuss.php?d=31895 | ||
* http://tracker.moodle.org/secure/QuickSearch.jspa and type "customscripts" | * http://tracker.moodle.org/secure/QuickSearch.jspa and type "customscripts" |
Revision as of 10:18, 6 July 2011
Custom Scripts Mechanism
Any scripts that are called directly via a url (eg index.php, user/view.php) can now be customised by placing a file with the same name (including directories) in my_moodle_data_dir/customscripts For example: my_moodle_data_dir/customscripts/index.php; my_moodle_data_dir/customscripts/user/view.php
- this is for people making short term changes to VISIBLE web pages in the moodle source code
- need to check relative links ; for example: never require ../config.php
- cannot add new files to customscripts folder because they are not accessible directly via web.
- better to use cvs or cogito for long term management of customisations to moodle code
- it seems to have been used extensively only by the Moodle_for_Mobiles project
- to enable Custom Scripts, add $CFG->customscripts=path/to/customscript/folder (see Configuration_file)
References
- http://moodle.org/mod/forum/discuss.php?d=31895
- http://tracker.moodle.org/secure/QuickSearch.jspa and type "customscripts"