Moodle 2.0 release notes: Difference between revisions
From MoodleDocs
No edit summary |
|||
Line 21: | Line 21: | ||
===API Changes=== | ===API Changes=== | ||
See [[Development:Migrating_contrib_code_to_2.0]] | |||
* [[Development:DB_layer_2.0_migration_docs|Database layer changes]] - you will need to update your code. | * [[Development:DB_layer_2.0_migration_docs|Database layer changes]] - you will need to update your code. |
Revision as of 22:07, 29 April 2010
Note: This page is a work-in-progress. Feedback and suggested improvements are welcome. Please join the discussion on moodle.org or use the page comments.
Release date: Not yet released
We're aiming to release a Moodle 2.0 preview release on Monday 3rd May 2010, followed by a testing period of 2.5 months before releasing 2.0 stable in the second half of July.
Please check the Roadmap and Moodle 2.0 Planning document for the most up-to-date information about our progress.
Here is the full list of fixed issues in 2.0.
Highlights
See Roadmap to follow the ongoing Moodle 2.0 development.
- MDL-11501 New SCORM module settings - display attempt status, display course structure, force completed, force new attempt, lock after final attempt - allowing the behaviour dictated to the SCORM object by the authoring package to be changed
Security issues
Known problems and regressions
API Changes
See Development:Migrating_contrib_code_to_2.0
- Database layer changes - you will need to update your code.
- File handling changes - you will need to update your code.
- Rendering layer changes - should be mostly backwards compatible, but you are advised to upgrade your code.
- Require capability used to do an automatic require_login. It no longer does so. All pages must explicitly call require_login if they need it. MDL-19882
- Changes to the question type API