I currently have Feeds 6.x-1.0-beta9 working with Feeds XPath Parser 6.x-1.01
I am creating and updating node records from xml feeds from multiple sites (same format from all). These all come into one content type.
Each of my feed records indicate the url for the xml and show mapping fields for each of the source/target fields.

When I created this I had an earlier version of the Feeds Module. At this point I need change one of the fields target in the feed importer and add another. The edit UI for the feed importer is not showing any way to edit an existing field source or target values. The UI does provide a way to add a new field, however the legend does not list any of the source fields.

Thinking that something was broken, I tried to update Feeds XPath Parser to the latest version 6.x-1.10 and now I get a message "FeedsXPathParser: No mappings are defined.", my feeds are broken, and I don't see any of the field mappings in my feed records.

Where/How are the source fields identified to the parser?

And does anyone have any sage advice about how I might approach fixing the feed and re-identifying the mapping?

Please let me know what additional information would help clarify my issue.

Comments

bsnodgrass’s picture

bsnodgrass commented

My plan at this point is to:
First, restore from a backup at the point I had things working (a few months ago) and see if I can pick out the differences in operation.
Second, attempt to recreate the entire feed process with latest versions of the various modules.

if anyone has any other ideas they would be greatly appreciated.

twistor’s picture

twistor commented
Assigned: Unassigned » twistor
Status: Active » Fixed

I'm thinking this has been solved. Feel free to open it back up if you're still having problems.

bsnodgrass’s picture

bsnodgrass commented
Version: 6.x-1.10 » 6.x-1.x-dev
Status: Fixed » Active

twistor, thanks for the followup. Yes I got the mappings defined after a couple runs at it. I thought things were working fine, but it has come back to haunt me. My unique targets are missing.

I am now on feeds 6.x-beta10 and xpath parser 6.x-1.x from November 5, 2010. I've got the feeds components deployed into production using features 6.x-1.0.

I had it working but then started to get duplicates. On investigation I found the mapping did not identify any unique targets and it appeared this may have been stripped out when I created the feature set. I manually edited the xx.feeds_importer_default.inc file in the feature module to identify my unique targets.

The mapping still does not show any unique targets but I confirmed the code is there (export shows it). Where else can I look to make sure the unique targets are indeed set?

Still getting dups, any insight would be greatly appreciated.

Thanks!

twistor’s picture

twistor commented
Status: Active » Fixed

@bsnodgrass, Are you still having problems with this? Unique targets sounds like a feeds issue. Feel free to reopen if you're still having problems.

Also, we now have a link to the mappings page where it says "FeedsXPathParser: No mappings are defined." Thanks!

Status: Fixed » Closed (fixed)

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