I just had a quick look at the code involved. That string is named 'notmigrated' and comes from the 'resource' language file. Its used in 3 places.

$resoruce_old = $DB->get_record('resource_old', array('oldid'=>$this->current->instance));
$mform->addElement('static', 'warning', '', get_string('notmigrated', 'resource', $resoruce_old->type));

All 3 have a variable called $resoruce_old which is presumably meant to be $resource_old. This same typo exists in all 3 places indicating copying and pasting. That may well mean that whatever problem exists has to be fixed in all 3 places.

If nothing else, the misnamed variable should have its name corrected for the sake of readability.

In mod/resource/locallib.php resource_print_tobemigrated() and resource_print_filenotfound() contain exactly the same code. Code that prints this not migrated error. I dont think thats correct. Probably resource_print_tobemigrated() is meant to be doing something else.

if we're lucky theres no problem with the file migration and this function is simply outputting the wrong message.

Hi, Daniel.

Thanks for reporting this.

It would help us if you could add more information, such as screenshots, replication instructions, fix test instructions, a workaround or even a code solution.

Michael,
Attached are some screen-shots. These courses have been obtained from the Genesse County ISD in Michigan. Unfortunately I cannot post the specific course but would be willing to work with some one else and give them access to an instance of moodle to see the specific issues.

The general replication instructions are pretty much just to restore the course from the backup zip file and when you try and click a topic the second screenshot appears. Also Forums / submission forms / exams seem to have migrated correctly.

Let me know if there is anything else that could be of help.
-Daniel

Image of the initial page: http://puu.sh/38St
Image of the error: http://puu.sh/38Sw
Image of the legacy files directory: http://puu.sh/38S9

Daniel, can you please send me the original course backup (without user data) to my email david@moodle.com ? I would analyse it and used for debugging this. Of course I would not provide any part of the course to any 3rd party and would remove it immediately after fixing this.

If that is not possible, can you please contact me at that email so we could arrange my access to the site to explore details there?

David,
I just sent you that course.
-Daniel

Thanks Daniel for the course. It helped a lot. The issue here is buggy conversion of legacy mod/resource/. In your case, you have a resource in 1.9 of type "Link to a file or URL" with URLs pointing to local course_files area. In moodle.xml such information is then stored as

  <MOD>
    <ID>3226</ID>
    <MODTYPE>resource</MODTYPE>
    <NAME>Blah blah blah</NAME>
    <TYPE>file</TYPE>
    <REFERENCE>$@FILEPHP@$$@SLASH@$flvs$@SLASH@$educator_webdes1_v7_gs$@SLASH@$module5$@SLASH@$lesmo5$@SLASH@$5_04_i.htm</REFERENCE>
    <SUMMARY></SUMMARY>
    <ALLTEXT></ALLTEXT>
    <POPUP></POPUP>
    <OPTIONS></OPTIONS>
    <TIMEMODIFIED>1262756060</TIMEMODIFIED>
  </MOD>

but our current code does not expect @$FILEPHP$@ in the reference field (that is the bug).

I have this partially fixed on my machine and will continue on that next week. Stay tuned.

Retriaging and increasing the priority.

Submitting a patch for integration.

@Daniel, I am able to restore your course now. Some images in the linked HTML files are not displayed because of the way how they referenced:

<img src="../../genimage/images/temimage/header.jpg" />

This can't work properly in the restored course because of the changes in File API and the way how Moodle embeds images now.

David,
Sounds great. Let me know when the patch is about so I can apply it to my instances. The images I can work on fixing myself. Thanks for all your work.

Integrated, thanks!

Tested with 1.9 resource having full-path file.php url and embed image and they were perfectly migrated (the html and the image) to resource (file) files. Passed!

Since this is integrated... Where would be the best place to pick up the patch for this?

Hi Daniel,

you still will have to wait some hours until this fix, together with the rest, land to our git/cvs servers. Then, you will be able to get the fix from them.

And < 24h after the fixes are available in the servers, a new battery of packages will be built and available @ download.moodle.org.

The plan uses to be:

• EU Wednesday evening: the patches arrive to git/cvs servers
• EU Thursday morning: the new packages are available @ download.moodle.org

Ciao

PS: You will know when the changes have arrived to git/cvs servers because then, and only then, this issue will be closed, so you will receive one email about that.

Congratulations - this fix has just been released in the weeklies.