I have tried this module but find it lacks anything of use for my purpose. I work for a company with thousands upon thousands of records. We use xpath to build imports because csv's will remove all the body formatting. With xpath or csv it would be almost impossible with ten domains and thousands of records to build out a spreadsheet to import. This makes it useless for my purpose which is sad because it is so needed in the community. Have you thought of a mapping by name instead and one field called domain? I know that will not resolve the multi domain issue as easily, but a comma separated list that is expanded with feeds tamper should resolve that issue. Then any sort of import export can be built with views only instead of needing to manually tweak a csv file.

Comments

eric_a’s picture

Version: 7.x-1.1 » 7.x-1.2
Component: Miscellaneous » Code
Status: Active » Needs work
Related issues: +#2240163: Make domain_feeds work with the latest release of feeds
StatusFileSize
new1.17 KB

Perhaps something like the attached patch. Note that this is untested and in its current form depends on #2240163: Make domain_feeds work with the latest release of feeds.

eric_a’s picture

StatusFileSize
new1.16 KB

Oops, my last-minute target name change from "domains" to "domains:multiple" wasn't fully implemented.

eric_a’s picture

StatusFileSize
new1.2 KB

Now only processing existing domains.

eric_a’s picture

StatusFileSize
new1.23 KB

Now both explicitly setting and unsetting domains.

eric_a’s picture

StatusFileSize
new1.24 KB

Oops.

eric_a’s picture

Here's a version that adds support for mapping to users as well.

  • Jim.M committed 176a143 on 7.x-1.x
    Issue #2300331 by Eric_A: Map to multiple domains in a single column
    

  • Jim.M committed 007b88a on 7.x-1.x
    Issue #2300331 by Eric_A: Map users to multiple domains in a single...
jim.m’s picture

Status: Needs work » Fixed

@Eric_A thanks for the patch. I've rewritten it a little, but generally your idea isn't touched. I've also noted that we don't check for entity type in our hook_feeds_processor_targets_alter implementation and in case of both user and node targets it would bring some confusion, so I've refactored the method a little bit and added checking code for it.

eric_a’s picture

Status: Fixed » Closed (fixed)

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