Upgrading to enable M-Learning

During our research into mobile Apps – The Wanted List we discovered we needed to upgrade Moodle and Mahara.

The much awaited official Moodle Android App is due for release any moment and requires Moodle 2.1 or higher.  Additionally Moodle 2.2 onwards has the MyMobile theme especially designed for mobile devices.  The bad news was our Moodle was lagging behind on version 2.0.4.  At the time of our last upgrade Moodle 2.1.1 was available but would not work on our webserver because it requires PHP 5.3.2 and we were restricted to PHP 5.2.

Fortunately, our web host, United Hosting had announced they were due to upgrade the servers from 5.2 to 5.3 on 10th January, so we upgraded to the latest Moodle 2.2.1 on 16th January.

Twitter announcement - Upgrading Moodle

Mobile Moodle

Everything went smoothly with the upgrade 🙂  With a little bit of configuring the MyMobile theme also works very well – though we needed to adjust the fixed width of the Google Calender and will also need to redesign graphical navigation so all elements adapt well to various screen widths.

We also upgraded to the latest Mahara 1.4.1 which supports the MaharaDroid app. MaharaDroid enables Android phones to share or upload content to Mahara and requires a minimum of Mahara 1.4.

Unfortunately we are experiencing a few browser and operational inconsistencies with the latest version of Mahara, particularly with regard to editing uploaded files in Portfolio Pages.  We are investigating:

  • Firefox 9.0.1: On some PCs the edit buttons not working on File uploads (but inconsistency between alike versions)
  • Chrome 16.0.912.75: Edit and Select buttons not working in the File uploads
These 2 issues also trigger a set of PHP errors:
[18-Jan-2012 14:26:53] [WAR] 8d (lib/errors.php:464) An exception was thrown of class PieformException.
[18-Jan-2012 14:26:53] [WAR] 8d (lib/errors.php:464) THIS IS BAD and should be changed to something extending MaharaException,
[18-Jan-2012 14:26:53] [WAR] 8d (lib/errors.php:464) unless the exception is from a third party library.
[18-Jan-2012 14:26:53] [WAR] 8d (lib/errors.php:464) Original trace follows
[18-Jan-2012 14:26:53] [WAR] 8d (lib/pieforms/pieform.php:528) No function registered to handle form submission for form "files"
[18-Jan-2012 14:26:53] Call stack (most recent first):
[18-Jan-2012 14:26:53] * Pieform->__construct(array(size 12)) at /home/administrator2/public_html/mahara/lib/pieforms/pieform.php:161
[18-Jan-2012 14:26:53] * Pieform::process(array(size 12)) at /home/administrator2/public_html/mahara/lib/pieforms/pieform.php:71
[18-Jan-2012 14:26:53] * pieform(array(size 12)) at /home/administrator2/public_html/mahara/artefact/file/index.php:38
[18-Jan-2012 14:26:53]

The Mahara Bugtracker does not list these issues – the closest bug being Bug #891436 which mentions the same PHP errors.  I have made small customised changes to the Resume artefact as documented here, but I do not think it is at all related, so I will submit our own bug report.

Out of interest the demo Mahara site http://demo.mahara.org/ does not have the same issue using the same browsers, but I am not unable to confirm if the Mahara version is exactly the same version 1.4.1.

Also identified this bug:

  • Internet Explorer 7 to 9: Hyperlinks to uploaded content on portfolio pages only click-able on baseline of text.

And this is replicable on the demo Mahara website – this bug also needs submitting to Mahara Bugtracker.

Update

Reported to Bugtracker 🙂

Summary Importance Status Heat
918262 Clicking links to uploaded files in Page view using Internet Explorer Undecided New 0 out of 4 heat flames
918259 Select and Edit files in Chrome and sometimes Firefox – different to Bug #819102? Undecided New 0 out of 4 heat flames

Further Troubleshooting

I updated Bug #918259 to reflect the fact that it wasn’t a bug after all.  The problem was caused by missing or corrupt files in the folder mahara/lib/pieforms.  🙂

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s