Legacy Files issue. Upgrade Moodle 1.9 -> 2.03.

Legacy Files issue. Upgrade Moodle 1.9 -> 2.03.

Donovan Del Valle -
回帖数:2

Hi everyone!

I'm having a problem with the upgrade process. We're trying to recover our courses with all the documents inside them.

We did the upgrade, enable Legacy course files in plugins-> repositores. But something happen because when i check the course, im trying to see the files, but i see this message: This legacy resource type (file) was not yet migrated, sorry. When i try to check on 'Legacy course files' option, this is empty.

I'm lost right now, we checked all options about it but anything worked. I appreciate your help.

Thanks in advance!

回复Donovan Del Valle

Re: Legacy Files issue. Upgrade Moodle 1.9 -> 2.03.

Howard Miller -
Core developers的头像 Documentation writers的头像 Particularly helpful Moodlers的头像 Peer reviewers的头像 Plugin developers的头像
I'm not sure but I did a Google search on that error message and there's a few interesting threads and one (fixed) bug report...

http://tracker.moodle.org/browse/MDL-26580

One thing to check, does your site work at all? If your config.php file is wrong or the permissions on your data directory are wrong then you are bound to have problems. Can you upload files and get them back at all?

I hope you have a backup of your 1.9 site...
回复Donovan Del Valle

Re: Legacy Files issue. Upgrade Moodle 1.9 -> 2.03.

Helge Opedal -

Hi,

Did you find a solution to your problem? If so, please let me know how you did it.

We have the exact same problem. We upgraded from 1.9.16 to 2.2.1, and after that, all files seems missing. You click on them, and the message:

"This legacy resource type (file) was not yet migrated, sorry" comes.

We are pretty sure the upgrade process completed, and didn't stop in the middle.

What is funny though is that this problem seem to be present only for some Moodle instances we have, for others the upgrade went well.

We have put php.ini max execution time to 1800 as recommended, and we have also tried the CLI php upgrade. It didn't help.

Please help if anyone has the solution. So far we are still on 1.9.16

Thanks

regards