Importing Feeds configuration through the UI

I am also looking for this feature. I have a feed importer working in testing that I would like to migrate to multiple sites. Being able to simply import the content types and the importer would really be great.

You can follow the instructions @ The site builder's guide to Feeds under "Exportables and default hook", but you need to know how to knock up a module.

Importing the content types is a matter of enabling content copy in CCK...

You never actually import on another site but export to code with a tool like Features http:/drupal.org/project/features

Features works fine, if you don't want install a new modules you can copy data on feed_importer table config in row.

Thank you to everyone for the reply. I have been using the features module for this with great success.

I'm looking for this capability, too, but I'm not seeing how to export the importer definition in the Features UI. When I select the Feeds option, I just get a message that says"All components of this type are exported by other features or modules.". Do I need to write a hook implementation?

Changing issue title back.
@wonder95: see if #1094848: Can't select which View should be exported. or #1102686: Can't export node types that modules invoke with hook_node_info(): blog, forum, poll, panel, product, product_kit help, or open a new issue.

Doing a quick import is a valid feature request imho.

I second that.

Um, yeah. Completely inexplicable to have an "export" option with no corresponding import option.

Agree with #10, really confuse while we have export but not import.

here is a quick-and-dirty way to import.

* take the export and copy the code block
* enable devel.module and paste that block into devel/php
* at the bottom add this code
* submit and enjoy your import

// $feeds_importer is the importer configuration
// see feeds_importer() and FeedsImporter::load()
$importer = feeds_importer($feeds_importer->id);
$importer->setConfig($feeds_importer->config);
foreach (array('fetcher', 'parser', 'processor') as $type) {
  $importer->$type->setConfig($feeds_importer->config[$type]['config']);
}
$importer->save();

WARNING: just mocked it up in case this makes someone happy, did NOT test it thoroughly.

writing an import function might be easy now.

Wouldn't this be great in a small feeds import importer module?
EDIT: #12 worked for me now!

Greetings, Martijn

contrib module or patch - it's about the same amount of work.
a contrib module might be a quick fix if feeds maintainers are busy.
but a patch i would prefer said yoda.

I was also confused that the definition of a Feeds importer can be exported through the UI, but not imported; for "normal" users (= non developers, non site builders), this feature is pretty much useless.

For a site builder, the requirement to have additional modules like 'devel' or 'features' running on a production server to get 'Feeds' exports from development/staging to production is not too cool, also.

I strongly second a quick mechanism to exchange (and/or update) 'Feeds' defintions, and I definitly don't want to rely on features for that.

#12 worked like a charm, thanks a lot for this.

Thanks so much, axel.rutz! #12 worked beautifully and saved me a ton of time.

#12 FTW - thank you!

#12 worked well for me (thank you!) with one exception. When I went to import/ and clicked through to the new importer, the standalone form would not load (the path was correct, but it just displayed the list of importers as on the index screen).

To resolve this I cloned the new importer, and the standalone import form of the cloned importer worked well.

Closed #1425702: Add ability to import a feeds configuration export through the UI as a duplicate of this issue, re-titling this one.

This is definitely a valid feature request. I will get to this at some point. Unless someone beats me to it ;)

#12 worked for me too, thx

Import via UI is an important feature, it would be great to have it soon.

Perhaps, it is possible to clone module bundle_copy for this feature

you can use bulk_export module (that is part of ctools) to build a custom module automatically.

+1 for solution in #12. Thanks!

There's an older issue I found first, with a patch attached: #777888: UI to import views-style exportable (a.k.a. How to import importers?).

Post #12 is working fine.

Thank you for your solution :) Cheers !

Working with Drupal 6 - #12 Worked fantastically well! Thank-you! Awesome!