Best practice forum (Archived)

该论坛讨论已删除

 
该论坛帖子已被删除
2012年08月19日 Sunday 23:43
该论坛帖子的内容已被删除,无法再访问。
CogginsSimon
Re: Totara 2.2 Upgrade
CogginsSimon 发表于 2012年08月20日 Monday 14:07
小组 Totara

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

该论坛帖子已被删除
2012年08月20日 Monday 20:27
该论坛帖子的内容已被删除,无法再访问。
CogginsSimon
Re: Totara 2.2 Upgrade
CogginsSimon 发表于 2012年08月20日 Monday 20:56
小组 Totara

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

Thanks,

Simon

该论坛帖子已被删除
2012年08月20日 Monday 21:23
该论坛帖子的内容已被删除,无法再访问。
该论坛帖子已被删除
2012年08月21日 Tuesday 11:57
该论坛帖子的内容已被删除,无法再访问。
CogginsSimon
Re: Totara 2.2 Upgrade
CogginsSimon 发表于 2012年08月21日 Tuesday 16:07
小组 Totara

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

该论坛帖子已被删除
2012年08月28日 Tuesday 03:01
该论坛帖子的内容已被删除,无法再访问。
该论坛帖子已被删除
2012年08月28日 Tuesday 07:59
该论坛帖子的内容已被删除,无法再访问。
CogginsSimon
Re: Totara 2.2 Upgrade
CogginsSimon 发表于 2012年08月28日 Tuesday 13:28
小组 Totara

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

Simon

CogginsSimon
Re: Totara 2.2 Upgrade
CogginsSimon 发表于 2012年08月28日 Tuesday 13:27
小组 Totara

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