Best practice forum (Archived)

Issue upgrading from 2.4.14 to 2.5.3 (and 2.5.4)

Hello,

We were trying to upgrade from 2.4.14 to 2.5.3 and were recieving a message at the plugins attention screen about the Totara Core needing to be downgraded.

Attached is the screenshot.

When we click on Upgrade Moodle Database now, it tries to go through the process and we get the following screen

If we click on Continue at that screen, it sends us back to the first message. We do alter totara.php, we were wondering if that could have anything to do with this, however we have tried replacing the totara.php file with the stock totara.php file and there was no change. Users are able to logon to the portal however, we can't get in as administrators to modify anything.

Thanks for your help.

Permalink | Reply

Hi Scott,

At some point either the upgrade got half-way through and then failed, or you may have implemented a custom change to totara_core and changed the number on the totara/core/version.php.

From 2.4.14 the proper totara_core version number should be 2013070805 so you should run the following query on the database

UPDATE mdl_config_plugins SET value='2013070805' WHERE plugin='totara_core' and name='version'

This will reset the version of totara_core to the 2.4.14 version number and should allow the upgrade to proceed normally.

Permalink | Show parent | Reply

The content of this forum post has been removed and can no longer be accessed.

Permalink | Show parent | Reply

Hi Alan,

The upgrade screen error is showing that the registered version of totara_core in mdl_config_plugins is 2013120300. The way the upgrade works is by comparing the registered number of the plugin in mdl_config_plugins with the number in the plugins version.php, in this case totara/core/version.php. The 2.4.14 version should be 2013070805.

So normally the only way this could have happened is if the 2.5.3 version of the /totara/core folder was present at some point and the upgrade process was run while the rest of the code was still on 2.4.14. Each plugin is essentially standalone and there's no way I can think of that adding or changing a theme would cause a version bump in a completely unrelated component like this.

Maybe the customtotara theme calls functions in totara_core and so someone accidentally dropped in the 2.5 version of that code? Resetting the value in mdl_config_plugins should allow the upgrade to proceed.

Permalink | Show parent | Reply

Apologies Alan, on further investigation there is indeed an issue with the totara_core plugin. A patch in 2.5.3 updates the version number in the database, but leaves the version.php number as 2013102900.

This would then cause an issue when trying to install or update any third-party plugins (like your theme).

There's an easy fix, just change the line in totara/core/version.php to

$plugin->version = 2013120300;

I'll make sure this is fixed for the next 2.5 release. Apologies again for the crossed wires!

Permalink | Show parent | Reply

The content of this forum post has been removed and can no longer be accessed.

Permalink | Show parent | Reply

A fix for this issue was included in today's (7th January 2014) release of Totara 2.5.5

Permalink | Show parent | Reply