22 August 2013, 16:51

Who's affected: If you pulled the HEAD of the 1.6_STABLE or 1.7_STABLE branch between UTC 1:20am, 21 Aug and UTC 4:00am, 22 Aug, and deployed it on your Mahara site.

Affected sites will have a database version number of "2013081400". You can see the database version number by navigating to the Mahara Administration page. The version number will be displayed in the lower-right corner of the screen, like this: "Mahara version 1.7.3testing (2013081400)" or "Mahara version 1.6.7testing (2013081400)"

What happened: The fix for Bug 1207140 ("YouTube iframe filter doesn't support the //youtube.com URLs YouTube now provides in embed code") erroneously raised the database version number in these two branches much higher than it should be.

What problems can this cause: If you deployed this update to your site, your site may fail to detect and properly apply subsequent database upgrades.

How to fix it: If your site is affected, you can fix it by following these steps. Note! You only need to follow these steps if your site is affected. If you don't see version 2013081400 on your Administration page, then you're fine and don't need to do anything.

1. Pull the latest version of 1.6_STABLE or 1.7_STABLE and merge/deploy it to your site. (This will put the correct version number in htdocs/lib/version.php)

2. Manually correct the version number in your database by running one of these SQL queries:

If you are running 1.6_STABLE: UPDATE config SET value='2012080618' WHERE field='version' AND value='2013081400';

If you are running 1.7_STABLE: UPDATE config SET value='2013032211' WHERE field='version' AND value='2013081400';

3. Now if you go to the Mahara Administration page you should see "Mahara version 1.6.7testing (2012080618)" or "Mahara version 1.7.3testing (2013032211)"

I apologize for letting this error slip through code review. As always, if you have any difficultes, feel free to ask for help here on the community forums, or on the #mahara IRC channel on irc.freenode.net.

Cheers,

Aaron