Pretty self explanatory. Either a mini-module are just some pointers as to how compatible the data structure is would be grand.

Comments

wmostrey’s picture

wmostrey commented
Assigned: Unassigned » wmostrey

Catch, did you try using the asset_import module? Configure it to whatever location the imagefield stored the files (might even by /files) and like that you can import them. Let me know what you think of that solution.

catch’s picture

catch
he/him
Primary language English
commented
Category: feature » support

wmostrey: I'll give it a go, haven't taken a proper look yet. I have shared imagefields, multiple imagefields and all kinds of stuff so not sure if it'll help, but will have a proper look in a bit.

wmostrey’s picture

wmostrey commented
Title: migration path from imagefield » migration path from imagefield, image, IMCE, ...
Category: support » feature

Marking this as the generic "migration path" issue. The next version of asset_import will feature this.

wmostrey’s picture

wmostrey commented

The new version is now in cvs and will be included in the new dev version once it is automatically generated. It features two new options:

  • copy the files instead of moving them
  • creating a destination subdirectory

Do more options need to be added as a migration path? I'm trying to make this as easy as possible.

catch’s picture

catch
he/him
Primary language English
commented

wmostrey: it'd be nice to have db migration scripts for image and imagefield (ideally storage should be unified eventually so you can just slap a different ui on, but that's not your job). Note I've not looked at how asset handles files at all to know whether this is trivial or not.

wmostrey’s picture

wmostrey commented
Component: Code » Asset Import

Catch, that would indeed be good but I'm not sure if it's asset's job to provide a migration path on that level for each of the file handling modules out there. It's not really hard to do, but I do need to check each module to see how and where they store their data and then load it with the asset_import module. With image being a core module, I'll be sure to include a migration path for it.

catch’s picture

catch
he/him
Primary language English
commented

image isn't a core module, but otherwise yeah I agree - could maybe be put as a standalone thing in the handbook? To do this with custom sql would still need to deal with the files/images path validation issue. Thanks for the attention to this by the way. When I can get the actual import working on my system I'll have a look at the sql - had a similar issue getting some 4.7 cck fake 'body' fields back into the core body field, which worked fine with a pretty simple subselect in the end.

wmostrey’s picture

wmostrey commented
Status: Active » Fixed

Exciting news: this has been fixed on dev: http://drupal.org/cvs?commit=129523.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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