Notice : Undefined index: xpathparser:30 dans FeedsXPathParserBase->parse() (line 68..

Removing the mappings in the Processor is not enough. After you save the new mappings, go back to the Parser. Although you cannot see them, the parser record is unchanged. Click on save to update the parser. Then go to Tamper, and again click on save to remove the tamper entries for the items you removed.

Three screens for what should be accomplished on one. But it works.

This doesnt work for me. I am still getting the damn undefined index messages on removed mappings!

I had this same issue. I resolved it by deleting my Feed Importer content node and recreating it. So essentially restarting the feed.

I'm going to keep this active. We should do a better job of cleaning things up.

It might be a Feeds Tamper issue, actually checking...

@twistor, did you come up with anything?

having the same issue

I have this issue as well.

Hello,

I had this issue as well and it was fixed byt deleting the mapping along with the field of the content type it was connected to. Afterwards I re-created the field and it works ok for me!

I have this issue also. I deleted three fields from a content type and also deleted the mappings etc and still cannot get the error to stop. I am loathed to delete the entire content type and rebuild it as it has a huge amount of fields. I will keep trying to figure it out i guess.

You shouldn't need to delete anything.

The latest dev has had this fixed for a long time. We'll try to get a new release out soon.

I am working with Drupal 7.34.
I still have the same issue with 7.x-1.0 (2014-Dec-11).
I tried to switch to the development version 7.x-1.x-dev (2014-Oct-15) as suggested in the comment #9. Still have the annoying notice covering the whole page.

I can't remove all the mapping and build them again since I have hundreds of fields in my content type. So I built this patch to perform a check on the array and remove the notice. Although maybe the problem should be solved with a better cleaning of the db during the removal of the feeds.

None of the above solutions worked for me, only way to fix it was to export it. Delete the feed and import node. Modified the exported feed so the index numbers would be secuential and only then did an import (even though I deleted first, I had to overwrite the old one). Re-created the import node, and problem solved.

Actually import is still not working (at least for me). Export looks ok, but import does not fully populate options.
Deleted manually the fields after first deleted one, recreated them, got rid of the DB error I was getting. So in terms of this issue, that was my (very convoluted and involved) way to solve it.

@ibonelli, I don't know if your issue is related. This is not causing a db error.

Thanks for the feedback @twistor. It's been long, but I recall having two distintive issues. You are right, they might be unrelated. Cheers!