Development:Migrating contrib code to 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...
- Development:DB_layer_2.0_migration_docs
- Development:Using the File API in Moodle forms
- Development:Output_renderers
- Development:Migrating_your_code_to_the_2.0_rendering_API (n.b., some info outdated and may need updating)
- Development:Themes_2.0
Some details of how to re-design image CSS for plugin code ar in the main themes documentation: Development: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: Development:JavaScript_guidelines
