Note:

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

Moodle 2.3.7 release notes: Difference between revisions

From MoodleDocs
(Created page with "Releases > {{FULLPAGENAME}} Release date: Not yet released Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+res...")
 
m (Protected "Moodle 2.3.7 release notes": Developer Docs Migration ([Edit=Allow only administrators] (indefinite)))
 
(10 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Template:Migrated|newDocId=/general/releases/2.3/2.3.7}}
[[Releases]] > {{FULLPAGENAME}}
[[Releases]] > {{FULLPAGENAME}}
   
   
Release date: Not yet released
Release date: 14 May 2013
   
   
Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%222.3.7%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in 2.3.7].
Here is [https://tracker.moodle.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+%3D+mdl+AND+resolution+%3D+fixed+AND+fixVersion+in+%28%222.3.7%22%29+ORDER+BY+priority+DESC&runQuery=true&clear=true the full list of fixed issues in 2.3.7].
Line 7: Line 8:
===Highlights===
===Highlights===
   
   
* ...
* MDL-38702 - CSS Optimizer now works with MyMobile theme
* MDL-39203 - Connection to Dropbox repositories is now working
===Functional changes===
* ...
===API changes===
* ...
   
   
===Security issues===
===Security issues===
   
   
A number of security related issues were resolved. Details of these issues will be released after a period of approximately one week to allow system administrators to safely update to the latest version.
* [https://moodle.org/mod/forum/discuss.php?d=228930 MSA-13-0020] Capability issue in Assignment
* [https://moodle.org/mod/forum/discuss.php?d=228931 MSA-13-0021] Potential information leak in Gradebook
* [https://moodle.org/mod/forum/discuss.php?d=228933 MSA-13-0022] Information leak in hub registration
* [https://moodle.org/mod/forum/discuss.php?d=228934 MSA-13-0023] Permission issue in blog comments
* [https://moodle.org/mod/forum/discuss.php?d=228935 MSA-13-0024] Form filtering issue
 
===Fixes and improvements===
===Fixes and improvements===
   
   
* ...
* MDL-38541 - Rebuilding the course cache no longer causes problems during upgrade
* MDL-39398 - Notice while sending Jabber notifications fixed
* MDL-39365 - SCORM questions are counted correctly
* MDL-35364 - Shortened text no longer causes invalid HTML
   
   
=== Known Bugs ===
These issues were discovered at the last minute before there was time to fix it in this release.  They will be fixed in the next weekly release.
*  MDL-39641 - "Updating a repository instance configuration requires a change of instance name"  - The work-around is simply to change the name slightly.
==See also==
==See also==
*[[Moodle 2.3.6 release notes]]
*[[Moodle 2.3.6 release notes]]

Latest revision as of 09:07, 25 May 2022

Important:

This content of this page has been updated and migrated to the new Moodle Developer Resources. The information contained on the page should no longer be seen up-to-date.

Why not view this page on the new site and help us to migrate more content to the new site!

Releases > Moodle 2.3.7 release notes

Release date: 14 May 2013

Here is the full list of fixed issues in 2.3.7.

Highlights

  • MDL-38702 - CSS Optimizer now works with MyMobile theme
  • MDL-39203 - Connection to Dropbox repositories is now working

Security issues

Fixes and improvements

  • MDL-38541 - Rebuilding the course cache no longer causes problems during upgrade
  • MDL-39398 - Notice while sending Jabber notifications fixed
  • MDL-39365 - SCORM questions are counted correctly
  • MDL-35364 - Shortened text no longer causes invalid HTML

Known Bugs

These issues were discovered at the last minute before there was time to fix it in this release. They will be fixed in the next weekly release.

  • MDL-39641 - "Updating a repository instance configuration requires a change of instance name" - The work-around is simply to change the name slightly.

See also