If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Plugin files

From MoodleDocs

This content of this page has been updated and migrated to the new Moodle Developer Resources. The information contained on the page should no longer be seen up-to-date.

Why not view this page on the new site and help us to migrate more content to the new site!

The following is a list of files that work the same in all plugin types (if they are present).


Meta-data about the plugin (like the version number, dependencies or the maturity level) are defined here.

  • version.php page provides detailed description of the file contents


English strings for the plugin are defined here. At least $string['pluginname'] must be present. There is an exception for the Activity modules, their expected file name is just pluginname.php (without the mod_ prefix).

  • String API provides information about the string files


The interface between the Moodle core and the plugin is defined here for the most plugin types. The expected contents of the file depends on the particular plugin type.

Moodle core often (but not always) loads all the lib.php files of the given plugin types. For the performance reasons, it is strongly recommended to keep this file as small as possible and have just required code implemented in it. All the plugin's internal logic should be implemented in the auto-loaded classes.

All functions defined in this file must meet the requirements set out in the relevant section of the Coding style


The use of this file is no longer recommended, and will not be permitted in core code. Rather than creating global function in a global namespace in a locallib.php file, you should make use of autoloaded classes which are located in the classes/ directory.

No new additions to this file will be permitted in Moodle core.

Where this file is in use, all functions must meet the requirements set out in the relevant section of the Coding style

Existing functions which have been incorreclty named will not be accepted as an example of an existing convention. Existing functions which are incorrectly named should be converted to use a namespaced class.


The plugin's database scheme (tables, fields, indexes and keys) are defined here. You should always use the in-built XMLDB editor to generate this file.


Upgrade steps (such as database scheme changes and other things that must happen when the plugin is being upgraded) are defined here. The in-built XMLDB editor can be used to generate the code to change the database scheme.


Plugin capabilities are defined here.


Allows you to execute a PHP code right after the plugin's database scheme has been installed.


Allows you to execute a PHP code before the plugin's database tables and data are dropped during the plugin uninstallation.


Event handlers (subscriptions) are defined here. It lists all the events that your plugin want to observe and be notified about.


Allow to declare your plugin as the messaging provider.


External functions and web services provided by your plugin are described here.


Details of classes that have been renamed to fit in with autoloading. See forum discussion for details.

Please note that the new classname must exist and should not be prefixed with a leading backslash.


defined('MOODLE_INTERNAL') || die;

$renamedclasses = [
    // Format:
    'old_class_name' => 'fully_qualified\\new\\name',

    // Examples:
    'assign_header' => 'mod_assign\\output\\header',
    '\assign_header' => 'mod_assign\\output\\header',
    '\assign' => 'mod_assign\\assignment',

    // Bad:
    'assign_header' => '\\mod_assign\\output\\header',



It is a convention in the Moodle code that all CLI scripts are put into the cli/ folder inside the plugin directory. Make sure all these files declare themselves as CLI scripts properly (the constant must be defined prior to loading the config.php):

define('CLI_SCRIPT', true);


Describes the administration configuration for your plugin.

The setting names are supposed to be plugintype_pluginname/settingname (note the slash) and not plugintype_pluginname_settingname or even just settingname. This makes them to be stored in the config_plugins table without polluting the global $CFG object.


Plugin's Javascript modules written using AMD or ES6 format. (AMD, supported since Moodle 2.9, ES6 since Moodle 3.8).

Note: Since Moodle 3.9, all files must be in an ES6 format for acceptance into core.


Plugin's YUI modules (recommended way to include Javascript in Moodle 2.8 and older).

Note: The inclusion of new YUI modules will not be accepted to Moodle core from Moodle 3.8 onwards with the exception of Atto Editor plugins.


Plugin's jQuery modules (Moodle 2.8 and older)

Note: The inclusion of jQuery modules will not be accepted to Moodle core from Moodle 2.9 onwards.


The plugin's CSS are stored here.


The plugin's icon. Activity modules should provide 24 x 24 px colour icons. All other plugin files should be represented by 16 x 16 px monochrome icon. There should be a fallback pix/icon.png version of the icon for legacy browsers.


The file should list all 3rd party libraries bundled with a plugin.

<?xml version="1.0"?>

The location is a path to the library directory or file, relative to the plugin's root directory. Please note that license must be always compatible with the GNU GPLv3.

Locations defined in this file are excluded from the coding style prechecks that are executed during the Plugin validation.

More information about 3rd party libraries can be found at:


The file should contain detailed instructions on how to import 3rd party libraries into Moodle. This should list:

  • Download URLs
  • Build instructions

More information about 3rd party libraries can be found at:


Plugin can declare its additional environment requirements via this file - such as compulsory presence of some otherwise optional PHP extension. See Environment checking#Configuration file overview for details of the syntax.

<?xml version="1.0" encoding="UTF-8" ?>
  <PLUGIN name="plugintype_pluginname">
      <PHP_EXTENSION name="soap" level="required">


The file or README.txt should contain useful information about the plugin. Ideally, it should act as an offline version of all the informations that are available at the plugin's page in the Plugins directory.


If the file (or CHANGES.txt, CHANGES.html or just CHANGES alternatively) is found when uploading a new plugin version into the Plugins directory, then the contents of this file is used to pre-fill the release notes field for the new version.

See also