Closed (fixed)
Project:
Ooyala
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
26 Aug 2011 at 19:42 UTC
Updated:
19 Jun 2013 at 21:20 UTC
Right now, we have stable releases of both versions of the module. However, there's no upgrade path between them.
Comments
Comment #1
torgospizzaAny chance of an easy Migrate class for this? We use nodereference in D6 as our means of connecting "Sample" nodes to Product nodes. (That way, Samples can be voted on and rated, etc.) This should make it easy in D7 since every item is now an entity. Obviously a clear upgrade path is best, but a Migrate class (or helper module) would be a close second.
Comment #2
deviantintegral commentedYeah, a migrate class would be a good way to do it. I don't expect to be doing any site upgrades that use this module for the next few months, but would be glad to review patches (either as update hooks or a migrate class).
Comment #3
torgospizzaFWIW, I was able to get our Migrations working pretty smoothly, but it's obviously written for our site specifically (due to the fields we've used). I'll see if there's a way I can make it more flexible for others. Also, we used the nodereference field for attaching Sample nodes (containing Ooyala fields) to our Product nodes; migrated the Ooyala nodes; then migrated the Product nodes (with their nodereferences intact). It worked swimmingly, as long as you are keeping nids the same from D6 to D7. Obviously, the other way around is not something I have accounted for, either, since doing so would break a lot of things on our site.
I will post back if I'm able to make something that works for more people!
Comment #4
quicksketchWe did an upgrade of a site from 6.x-1.x to 7.x-2.x with surprisingly little difficulty. Because our column names don't change from CCK in D6 to Field in D7, the migration can be done almost entirely through the D7 branch of CCK (which provides the field_migrate module). Because we have no field settings to speak of, the field configuration itself doesn't matter. Since the content comes over fine, I'm not sure we need to do any further work.
Comment #5
deviantintegral commentedSounds good to me.