Moodle 2.7 release notes
Releases > Moodle 2.7 release notes
Release date: Expected in May 2014
- 1 Server requirements
- 2 Browser and Screen reader requirements
- 3 Before you upgrade
- 4 Headline core features
- 5 Details
- 6 Developer Notes
- 7 See also
These are minimums - we recommend keeping all of your software up-to-date.
- Moodle upgrade: Moodle 2.2 or later (if upgrading from earlier versions, you must upgrade to 2.2.11 as a first step)
- Minimum PHP version: PHP 5.4.4 (always use latest PHP 5.4.x or 5.5.x on Windows - http://windows.php.net/download/)
- Ghostscript should be installed for pdf annotation.
Moodle supports the following database servers. We recommend keeping all of your software up-to-date.
|Microsoft SQL Server||2008|
Browser and Screen reader requirements
|Browser||Minimum version||Recommended version||Notes|
|Microsoft Internet Explorer||9||Latest||Version 10 is required for drag-and-drop upload of content from outside the browser into Moodle|
We now support and test on two screen reader configurations (MDL-44002).
|Browser||Screen reader||Minimum version||Recommended version|
|Microsoft Internet Explorer||Jaws||15||Latest|
Before you upgrade
Questions engine upgrade
When upgrading to Moodle 2.1 or 2.2 it was possible to delay part of the Question engine upgrade. You must complete this upgrade before upgrading to Moodle 2.7. You can check if this was completed at the bottom of the Environment page.
For further information, see the upgrading notes to complete the Question engine upgrade before Moodle 2.7.
All standard themes present in earlier versions, except the Clean theme, have been removed from Moodle 2.7. If you wish to continue using one of these themes then you will need to reinstall it explicitly *BEFORE* running the upgrade.
See the upgrading notes for theme upgrades in Moodle 2.7 for further information.
Headline core features
- MDL-43841 - New text editor: Atto - Tightly integrated in Moodle and focussing on usability and accessibility (TinyMCE still available as an option).
- MDL-43855 - New equation editor for Atto.
- MDL-42964 - Themes clean-up - Moodle is focussed on Bootstrap and improved responsive design. Clean is now the default theme and most other old themes have been removed from core (still available from Plugins directory). Many small improvements have been made all through the interface.
- MDL-43786 - More theme - A completely new theme called More that provides easy configuration though the UI, while retaining the efficiency of LESS and the responsiveness of Bootstrap.
- MDL-44070 - Improved conditional activities - Complex boolean combinations are now supported, with a conditions plugin API and a better interface...and it's faster!
- MDL-43682, MDL-43681 Log reports - User interfaces for the Live logs and Log reports have been improved, with more information and filtering support.
- MDL-43856 - New MathJax filter
- MDL-26680 - My Moodle reset to default button
- MDL-42932 - Calendar type choice at system level
- MDL-43497 - New capability moodle/site:forcelanguage to allow the course language to be overridden
- MDL-43526 - Option to restore a course from the course management pages
- MDL-18633 - New capability moodle/user:viewlastip for viewing a last IP field on user profile pages
- MDL-36141 - New moodle/course:reviewotherusers capability for restricting access to the other users page
- MDL-44505 - Subject line of forum notifications is configurable
- MDL-37658 - Logging - a new logging subsystem with plugins allowing Moodle logs to be very detailed and external. Many new events have been added which developers can take advantage of. These advancements will support better analytics as well as things like TinCan.
- Tasks - an improved scheduling system (like Unix cron) that allows precise scheduling of tasks even on complex clustered servers.
- Performance - With improvements to logging and scheduled tasks, as well as many other small improvements, overall performance will be improved, particularly on large sites.
Long-term support (LTS) until May 2017
Most of our releases receive 1 year of backported general bug fixes and 1.5 years of security and dataloss fixes from Moodle HQ.
Due to popular demand, we are committing to giving Moodle 2.7 extended support for security and dataloss fixes for 3 years (that's an extra 1.5 years support for this version).
If you are stuck on an old version then this might be the perfect time to upgrade!
Quiz & Question bank
- MDL-41727 - Quiz reports improved.
- Responses from all tries are available for analysis when using or "Adaptive", "Interactive with multiple tries" or similar behaviours.
- Break-down by question variant, for question types like Calculated, STACK and Variable-numeric, which one question can have different random variants.
- Progress bar during long calculations to prevent time-outs.
- Low-level calculation code moved into the question component, where it could potentially be reused by other activities.
- Much more automated testing of this complex area of code.
- Some minor improvements to the usability of the question bank - Some of MDL-40987
- MDL-33653 - To duplicate a question, you now start by clicking the x2 icon, like for activities.
- MDL-33839 - The various different ways to move questions in the question bank have been rationalised.
- MDL-33653 - There is now a 'Save changes and continue editing' button when editing questions. Useful when you are working on a complex question with the preview open in another window.
- MDL-40313 & MDL-40457 - New plugin point, so that plugins can add columns to the question bank, or new search conditions.
- MDL-39756 - Essay questions can now require an attachment, with the text optional, rather than the other way around.
- MDL-27414 - Random short-answer matching question type brought back from the dead. (This was in stable branches, but worth mentioning again.)
- MDL-33952 - The old Assignment (2.2) module has been removed from core. It has been replaced by a stub to support transparently remapping urls and restoring course backups from the old module to the new one. If you are still using the old assignment module - all instances of the old assignment module will be hidden after upgrading to Moodle 2.7. Once the upgrade tool is run on those assignments they will become visible again. It is recommended to upgrade, and then convert any remaining assignments because logic has been added to the assignment upgrade code for Moodle 2.7 to transparently map urls from the old assignment module to the new one. If you really, really need to keep using the old module, you should update the code to Moodle 2.7, and then replace the "mod/assignment" folder with the one from https://github.com/moodlehq/moodle-mod_assignment/releases before completing the upgrade.
- MDL-28448 - A new capability mod/assign:editothersubmission can be given to teachers to allow them to edit or delete student submissions.
- A checkbox 'Notify students' is available to control when to send feedback during the grading process.
- MDL-34432 - Teachers can comment directly on student's work on online text assignments
- MDL-42585 - New capability mod/assign:viewgrades to allow grades to be viewed but not changed
- MDL-44268 - Assignment grading table filters
- MDL-25499 - Cron has received a major update and now has support for both scheduled and adhoc tasks.
The benefits of these changes are:
- The schedule for every task can be configured by the admin
- Tasks can run in parallel
- Cron processes use locking to prevent the same task running at the same time by different processes
A result of this is that cron can be run much more often, which means (for example) forum posts can be sent out sooner. Admins can keep cron running at the same schedule as before, but it is strongly recommended that they increase the frequency of running cron to at least once per minute.
- MDL-42816 -Manual account authentication can now have password expiry enabled.
- MDL-41115 - A new setting allows users to log in with both their username and their email address.
- Reports: Reports that use log table, should be updated to use the new logging frame work. Old reports will continue to work as before as long as legacy logging is enabled in the site. See Migrating log access in reports for details.