Note:

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

Developer FAQ: Difference between revisions

From MoodleDocs
(→‎Help for new coders: I can't use one of the available plug-in points to make my change. What alternative is there?)
Line 15: Line 15:
===Is there any information on creating a new module or plugin?===
===Is there any information on creating a new module or plugin?===


See [[Modules]], [[Blocks]] and [[Authentication plugins]].
See [[Modules]], [[Blocks]] and [[Authentication plugins]], or the [[Developer_documentation#Make_a_new_plugin|full list of plugin types]].


===Is there any information on backup and restore?===
===Is there any information on backup and restore?===

Revision as of 09:03, 14 April 2009

Help for new coders

Where can I start?

See Finding your way into the Moodle code.

Where can "newbies" to Moodle get help?

The General developer forum! Feel free to ask any question, no matter how basic or advanced. Many people ask different levels of question every day, and the community is generally welcoming and quick to respond.

How do I create a patch?

See How to create a patch.

Is there any information on creating a new module or plugin?

See Modules, Blocks and Authentication plugins, or the full list of plugin types.

Is there any information on backup and restore?

See Backup.

I can't use one of the available plug-in points to make my change. What alternative is there?

See Local customisation.

Moodle's database

Where can I see a schema for the structure of the Moodle database?

When installing Moodle, the database tables are generated and updated by various db-handling scripts located in various places. There is no canonical schema representation, although the coding guidelines for database structure give an outline of the general approach.

The reason that the database information isn't stored in one place is because of Moodle's modular structure. Each activity module, for example, comes as a folder with script files inside. If the module needs to store information in the database, it must include scripts in a "db" subfolder which define and update the database structure.

How to get/set information when writing new Moodle code

How do I find out the currently-logged-on user?

The global object $USER, which contains the numeric $USER->id among other things.

How do I find out the current course?

The global object $COURSE, which contains the numeric $COURSE->id

How do I insert/retrieve records in the database, without creating my own database connections?

Always use the "datalib" functions, such as insert_record() or get_record(). Since Moodle 1.7 these are found in lib/dmllib.php. Using these functions helps with database abstraction (e.g. running on either MySQL or Postgres) as well as maintaining a single database connection. Moodle uses ADODB for database abstraction.

Look at the documentation for datalib.php for the list of functions and details of use.

How do I get/set configuration settings?

To get config values you would typically access the global $CFG object directly, which is automatically created by the core Moodle scripts. To set these "main" config values use set_config($name, $value). The values are stored in the Moodle "config" database table, but these functions take care of cacheing on your behalf, so you should always use these rather than fetching the records directly.

There is also a second table of config settings specifically for plugins ("config_plugin"). These are not automatically loaded into the $CFG object, so to fetch these you would use get_config($plugin, $name). To set them use set_config($name, $value, $plugin).

See also

pl:Developer FAQ