Mapper to utilise FileField Sources? [#1090236]

On a recent project I needed to get images from a remote source on a feed import. The content type to be imported into already had filefield/imagefield/filefield sources set up and it's all working well.

When I started using feeds to update this, it became apparent that filefield sources couldn't be used with feeds, since it's purely a widget...nowhere to put a remote image reference. The filefield mapper with feeds uses FeedsEnclosure (using curl in my case) to download a remote file....but for some reason it is painfully slow.

I wrote a mapper to use filefield sources' curl download to get it working and since have extended the mapper to also support the filefield attach method (to add local files). I don't think this mapper would be necessary if the native filefield mapper wouldn't have serious performance issues.

For the sake of comparison, here's the mapper I'm currently using.

Comments

Comment #1

etibmw CreditAttribution: etibmw commented 9 May 2011 at 21:21

Hi NicolasH,

I too am working on a site that will need to upload many pages with images.
i am looking at node import as well and trying to see which will work better.

for now both don't work with file field sources, node import is now adding it.

do you know if any work is being done on feeds, in respect to file field sources?
how are you with this issue?

i would be very happy to hear from you and maybe look at what you did so far

lets talk
eti

Comment #2

NicolasH CreditAttribution: NicolasH commented 9 May 2011 at 23:42

I think your best bet is feeds, rather than node import (the maintainer kind of says that himself on the project page).

As I stated above, feeds is capable of importing images natively - I just found the mapper being faster. Maybe you could try both and let me know how you went? It's certainly working for me...

If you'd rather have a tarball of the mapper, instead of getting it via git, let me know.