Local plugins: Difference between revisions
Helen Foster (talk | contribs) (see also link, category) |
Penny Leach (talk | contribs) No edit summary |
||
| Line 11: | Line 11: | ||
The local folder has some of the plug-in points available which are available to other modules. Perhaps most useful the local/db/ folder can be used to make database schema changes and custom role permissions. | The local folder has some of the plug-in points available which are available to other modules. Perhaps most useful the local/db/ folder can be used to make database schema changes and custom role permissions. | ||
However, using the local folder should be absolutely the last resort. Long term, you will almost certainly find it easier to maintain your changes if you can package them up as one of the standard types of plugins. | However, using the local folder should be absolutely the last resort. Long term, you will almost certainly find it easier to maintain your changes if you can package them up as one of the standard types of plugins. | ||
=== Local database changes and version === | |||
=== Local post-installation data insertion === | |||
=== Local capabilities === | |||
=== Local event subscriptions === | |||
=== Local admin menu items and settings === | |||
=== Local backup and restore hooks === | |||
=== Local course deletion hook === | |||
=== Local my moodle overrides === | |||
=== Local stickyblocks targets === | |||
=== Local user profile view hook === | |||
==See also== | ==See also== | ||
Revision as of 14:35, 1 December 2008
General customisations
Moodle has been designed with extensibility in mind. There are many plug-in points available though out Moodle to allow developers add new functionality to Moodle without modifying core code.
See the make a new plugin section of the Developer documentation page for the different plugin types available, and documentation on how to develop for them.
local/ folder for 'hacky' customisations
Sometimes it is not possible to use the available plug-in points to make your change. In situations like this then the local folder is for you. The idea is that instead of scattering your changes throughout the code base, you put them all in a folder called 'local'. Using this folder means you won't have to deal with merging problems when you upgrade the rest of your Moodle installation.
The local folder has some of the plug-in points available which are available to other modules. Perhaps most useful the local/db/ folder can be used to make database schema changes and custom role permissions.
However, using the local folder should be absolutely the last resort. Long term, you will almost certainly find it easier to maintain your changes if you can package them up as one of the standard types of plugins.
Local database changes and version
Local post-installation data insertion
Local capabilities
Local event subscriptions
Local backup and restore hooks
Local course deletion hook
Local my moodle overrides
Local stickyblocks targets
Local user profile view hook
See also
- CVS:moodle/lib/locallib.php
- Using Moodle Local Customisations forum discussion
