>Three months into our upgrade from Moodle 2.3.1 to 2.5 and everything in all honesty has been excellent.

As I’ve previously mentioned in my blog that I always thought that 2.3 codebase was very immature and there were lots of bugs that had yet to be resolved. Thankfully, I can say now that *most* of these have been worked out. The Moodle devs claim that things should also be a bit faster, and they are, but in reality your users will be hard pressed to notice any real world difference even when I’m running Moodle on relatively high end hardware.

More importantly than anything, the old ‘INVALID JSON STRING’ error that crept up randomly in 2.3 seems to have disappeared completely and although there have been one or two minor issues that I’ve fixed myself, none of these are anything worth blogging about in the slightest.

The UI is definitely the strength of 2.5 where consistency has been maintained to a better extent with the use of things like collapsed menus by default to stop your pages becoming too long and cluttered.

I would highly suggest to anyone running Moodle 2.0 to 2.4 to upgrade for the reasons above, not only that but because those code branches are no longer supported properly or maintained (other than for 2.4).

The little issue now that I have is that two days ago, Moodle 2.6 was released to the world. The main benefits that I can see from skipping through the release notes are:

  • Restoring of very large courses possible
  • Database reads and writes are reduced by 12.2% and 25.3% respectively (desperately needed)
  • Automatic temp directory cleanup (never properly worked in my opinion)