Note:

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

Migrating contrib code to 2.0: Difference between revisions

From MoodleDocs
mNo edit summary
No edit summary
Line 10: Line 10:
* [[Using the File API in Moodle forms]]
* [[Using the File API in Moodle forms]]
* [[Output_renderers]]
* [[Output_renderers]]
* [[Text formats 2.0|Text formats 2.0]] how user-entered content is handled.
* [[Migrating_your_code_to_the_2.0_rendering_API]] (n.b., some info outdated and may need updating)
* [[Migrating_your_code_to_the_2.0_rendering_API]] (n.b., some info outdated and may need updating)
* [[Themes_2.0]]
* [[Themes_2.0]]

Revision as of 09:42, 11 November 2010

Moodle 2.0


WARNING: Under construction RIGHT NOW!

The goal of this page is to provide a checklist of tasks to be considered to upgrade CONTRIB code to Moodle 2.0. Several significant changes have taken place including the File API, DB Layer, Navigation, Output renderer, etc. It would be good if we had a list that contributors could follow to help move them toward being able to migrate the code. Any help in building up this list is greatly appreciated.

Please add useful links...

Some details of how to re-design image CSS for plugin code are in the main themes documentation: Themes_2.0_creating_your_first_theme#Using_images_within_CSS

Be aware that themes are now cached on the server and so emptying your browser cache will not refresh the CSS. This can only be done by going to the site administration->appearance->themes->theme selector page and clicking the 'invalidate theme caches' button.

Javascript is included in different ways now and will need to be migrated, see the PHPDoc comments in /lib/outputrequirements.lib and some (slightly outdated) advice here: JavaScript_guidelines

There are other coding changes such as:

  • MDL-24063 which eliminates PARAM_CLEAN
  • MDL-24058 about no longer using stripslashes or addslashes

Please feel free to add others that come to mind. CONTRIB maintainers should check their 2.0 versions for these and make sure that they are appropriately handled.

See also