Limit on number of xpath queries

Can you be more specific, are you getting any kind of error?

I was looking for information about this very same issue and found this page.

You can add more mappings for your node processor, but they do not show up in the XPath XML parser settings.
Luckily, I can just discard one mapping that isn't that important and replace it with something that I really need.
But the problem still persists, and I will most likely need a few more mappings in the future as the feed I'm fetching is most likely to grow with more information.

[Edit]
My bad, looking at my mappings I saw that they had source as "XPath Expression" rather than "xpathparser:N".
This happened after I've added my 18'nth xpathparser mapping.
Was something changed since drushinka had issues with only 12 mappings? Increase to 18 ?

I'm having the same issue. When I try to map a new field the source is no longer "xpathparser:X" but insted "XPath Expression" and the new mapping fields does not show up under Settings for XPath XML parser.

I'm having the same issue. I'll try rolling back to 7.x-1.0-beta3 from .dev and see if that fixes it.

That seems to have fixed it for now. I'm using it with Feeds 7.x-2.0-alpha7+18-dev.

For me still the problem for more than 17 mappings with the 7.x-1.0-beta3 version ...

I also have the same problem:

- The first 10 Xpathparsers are fine - each becomes xpathparser:n;
- For more than 10 - each new Xpath Expression shows as "XPath Expression" and doesn't allow for the expression to be different for each new target

Using 7.x-1.0-beta3

Steps to reproduce?

I ran into the same problem when I tried to introduce another field, and I moved it to the top of the mapping list. It showed up as "Xpath Expression". When I checked the record in the feeds_importer table, it was listed as "xpathparser:25". Each new mapping I added (or attempted to) was listed as "Xpath Expresssion" and the new mapping was the only one to appear.

I moved the original mapping to the bottom of the list, and it was listed as "xpathparser:25". Problem solved. New mappings added normally at the end of the list.

I played with another parser with 24 fields. Moving no 23 to the top of the list resulted in no displayed name change. Then I moved no 24 up the list (just after 20) and number 23 was shown as "Xpath Expression". Proper naming was restored when I moved no 24 back to the bottom of the list. With the order of the list restored, moving no 24 up caused it to be displayed as "XPath Expression".

It all seems to depend on the highest numbered mapping being at the end of the mapping list. The order of mappings before the last position can be changed at will, until that last mapping is moved, then the problems begin.

Hope this helps someone to track this down. In the meantime, the work around would seem to be to not change the order of the latest mapping added.

I have the same issue. #8 works for me. Dragging the offending XPath Expression to the top of the list, then saving, then dragging to the bottom allows you to carry to adding xpathparser:N

I have the same issue. #8 is not working for me. My last Xpath Expression is numbered #10 (there are ten total). If I move things around I one does change to Xpath Expression (with no number), but there it does not affect whether or not I can add a new one.

If I add something new, nothing happens, the page just reloads.

Had same/similar problem here using bata4.

This was after importing the feed as a feature and reorganizing some fields.

Something like #8 worked for me though not at first. First I ended up with several items with the same id but eventually after moving things around back to what I thought was the original order and deleting and re-adding some fields I got it working.

Go, testbot.

Go, community.

Thanks for this - this was perplexing behavior.

Tested patch in #12 and it resolves the issue.

Thanks

What an annoying bug! Took me too long to find this issue. I would have expected this fix to results in a new release ( 7.x-1.0-beta5).