I took a quick look at the .install file. Someting seems to be seriously wrong. Maybe some intermediate updates are missing? I don't see where settings and origname are supposed to be migrated...

Comments

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented
Priority: Normal » Major

Yes, you're right, it's likely I would have written the upgrade path from D7 version something onwards, at a point where the FFP settings where already stored both in the custom table as well as in the Field settings, so at that point removing the custom table was fine, but coming for D6 this would not be the case.

Have started on a proper D6 upgrade path.

Take into account, that there is some stuff that can not be done in the upgrade path, such as updating the D6 style tokens to D7 style tokens, as there is no upgrade path possible for them.

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented
Status: Active » Fixed

Updated upgrade path has been committed.

Take into account that I just refactored the original upgrade path, which you have already run, and that you would need to do the upgrade from your D6 database again to take advantage of the changes.

Let me know how you go, if you get a chance to test this, as I don't really have any D6 sites to easily test from.

morenstrat’s picture

morenstrat
he/him
Primary language German
Location Bochum, Germany
commented

Thank you!

I have two more sites with filefield paths that need to be upgraded to D7. Upgrades won't happen before the second half of the year, though. I'll report back then.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.