Note:

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

Required code upgrades

From MoodleDocs
Revision as of 10:01, 16 August 2008 by Petr Škoda (škoďák) (talk | contribs) (New page: This page lists all changes that may be needed to be done in 3rd party modules and other integration code. =Moodle 2.0= Note to developrs: please keep adding more info here ;-) ==Mandat...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page lists all changes that may be needed to be done in 3rd party modules and other integration code.

Moodle 2.0

Note to developrs: please keep adding more info here ;-)

Mandatory

New Data Manipulation Layer (DML)

  • All database calls must be updated - new bound parameters syntax, magic quotes not used any more [1]

File API

It consists of three parts [2]:

  1. file storage - modules can not access the course files anymore, they must store alll files in own area
  2. file browsing - each module/plugin defines what files are browsable and acessible
  3. file serving - each plugin/module is responsible for file sending though pluginfile.php
  • Handling of files in backup/restore needs to be fully rewritten too.
  • File uploading in formslib fully rewritten - old API should not be used

Upgrade code

  • Upgrade allowed only from 1.9.x (upgrade of contrib modules does not do version tests yet)
  • Backup/restore must use new DDL API.
  • Concurrent upgrades are now prevented.

Messaging reimplemented

Mailing and notifications from modules needs to be updated (not finished yet)

Optional

  • Portfolio integration [3]
  • Conditional activities [4]


Other changes

These changes might affect some unsupported core code customisations. Modules and other plugins should not be affected.

  • rewritten course category sorting