Best practice forum (Archived)

This forum discussion has been removed

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

Hi Jo,

It sounds like maybe you copied the new code over the top of the old 1.1 code, rather than removing the old code completely. The enrol_devplan it mentions was renamed to totara_learningplan so doesn't exist in the 2.2 codebase.

Typically when upgrading I would create a new folder alongside the existing wwwroot:

wwwroot/[contains code]

newwwwroot/[new code]

Then copy the config.php from the old to the new directory then do:

move wwwroot -> oldwwwroot

move newwwroot -> wwwroot

That way you have still got a copy of the old code that you can switch back to if necessary.

Simon

Permalink | Show parent | Reply

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

Permalink | Show parent | Reply

No you're right the documentation in UPGRADE.txt isn't very clear. We'll update it in the next release.

Thanks,

Simon

Permalink | Show parent | Reply

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

Permalink | Show parent | Reply

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

Permalink | Show parent | Reply

Hi,

Was that a fresh install, or an upgrade from Totara 1.1?

If it was an upgrade, can you turn on developer debugging and try again - you should get some more messages.

If it was a fresh install, try adding this line to your config.php file:

$CFG->debug = 38911;

and try again and post any additional messages you get.

Finally can you let me know what operating system and database you are using?

Simon

Permalink | Show parent | Reply

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

Permalink | Show parent | Reply

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

Permalink | Show parent | Reply

No you have to upgrade to at least 1.1.17 or higher before you can move to 2.2.

Simon

Permalink | Show parent | Reply

Hi Dani,

Thanks the error message helped - I think I know what's causing that - we'll get it fixed in today's release (2.2.2).

Simon

Permalink | Show parent | Reply