Hi

I've noticed that if I remove a mapping element from an existing feed importer, it no longer imports properly.

For example:

I have an importer with 4 mapped source elements (using XPath XML Parser):

xpathparser:0 Title
xpathparser:1 Body
xpathparser:2 Code
xpathparser:3 GUID

I do an import, everything working fine.

Then I decide to remove one of the elements:

xpathparser:0 Title
xpathparser:2 Code
xpathparser:3 GUID

The next time I import, only the first element will get mapped to source data. In the debug view, the second and third elements don't get mapped to anything. It's as if Feeds hits the deleted entry and can't process any further.

I think this is a Feeds issue rather than Xpath XML Parser..?

Comments

adamharms’s picture

adamharms commented

same issue - subscribe

extexan’s picture

extexan commented

I clicked "Follow" on this issue because I ran into the same problem so I'd like to know if/when it gets fixed. But then I realized that simply following the issue doesn't let you (the maintainer) know how many others are encountering this bug. So here's a plus one on this issue.

twistor’s picture

twistor commented
Project: Feeds » Feeds XPath Parser
Version: 7.x-2.x-dev » 7.x-1.x-dev
twistor’s picture

twistor commented
Status: Active » Postponed (maintainer needs more info)

I just tested this out and I cannot reproduce it. What versions of things are you using?

extexan’s picture

extexan commented

In my case...

Feeds - 7.x-2.0-alpha7
Feeds XPath Parser - 7.x-1.0-beta3

I, and my main client, who is a web development shop with *many* clients, tend to stick with recommended releases - not the latest dev copy.

I removed mapping(s) from the middle of the list... not always the last item. Perhaps that will help you reproduce it.

twistor’s picture

twistor commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (fixed)

This was fixed a long time ago.