Missing Feeds plugin FeedsExJsonPath (or FeedsExJsonPathLines)

Did you download the library and place it in sites/all/libraries/jsonpath?

Probably, if you can see the fetcher. I'm also guessing you've tried clearing the cache.

Are you using the latest dev version?

same issue here

After cleaning cache sometimes it keep not working.
I opened file feeds_ex.module and added some debug to function feeds_ex_jsonpath_library_path()
I reloaded and error message disapeared. I deleted debugs and it works now. Not sure why not worked after first time i cleaned cache.

[edit]I saw Json parser at admin panel before install the library. After first error, i checked module website and installed the library. Then i cleaned cache as described at module page and error message did not hide until 3 or 4 times cache cleaned and manual edited the module[edited]

I also had this issue, but for the JSON JMESPath parser. I had to clear the cache about 8 times before the error went away.

Feeds uses the ctools plugin api which has file mappings that live in the file registry rather than in a proper cache. That basically means that even when you clear cache (or "drush cc all"), this won't get resolved.

The best way I can suggest to get this resolved is to use registry_rebuild via drush:

drush dl registry_rebuild
drush rr

You can also try forcing a file registry rebuild by hitting save from the modules page, or the themes page. if you are UI centric.

(I'm pretty stoked to have been able to help two of the greats! @jenlampton and @dublindrupaller )

As far as this module is concerned here are my thoughts:

This is only kind of a problem with feeds_ex. The two ideal solutions here would be to fully implement the libraries api for the various libs that this needs, so that when this module is downloaded and installed via drush, the dependencies (those libraries) are installed before the module is enabled. That would at least prevent a portion of new installs from accidentally doing the process backwards (which causes this problem).

Additionally, including a drush makefile so that dependencies could be pre-loaded during a code build should be done as well.

+1 for using drush registry_rebuild. I had the same problem with the XML Xpath parser.

drush registry_rebuild did the trick for me as well. Thanks!

drush rr, and drush cc all may have helped, but it turns out my PHP 5.3.x apc shared memory was 100% fragmented. Calling http://php.net/manual/en/function.apc-clear-cache.php fixed the problem.

I am not using JSON, so I didn't download the library and got this message anyway when I tried enabling this module.

Then, I went to the library path listed in the main feeds_ex page:

https://jsonpath.googlecode.com/svn/trunk/src/php/jsonpath.php

and, it seems the link is broken.

No problem, I can find it. Just letting you know.

I did notice that the parent feeds module registers all their plugin files in the .info file.
I had the same notice as here when I created my own plugin, but once I stored it in my .info file as well, those notices disappeared, so I suggest adding these files in the .info file as a patch.

I can confirm michel.g his patch uses the same approach for this module as the mother module Feeds does. See #1201638: Plugins should be listed in info file

The tests fail but that's probably because of the JsonPath project changed location. See #2835666: JSONPath parser download no longer works
And there have been no test runs on this module since latest commit on 7.x-1.x-dev at 2 May 2016 at 20:03 UTC

I suggest to wait until that other issue fixes that test failure before merging this issue in dev. Setting the issue its status to Postponed accordingly.

Committed #11 anyway, because I'm hoping that it can help with fixing the test failures I encounter in #2835666-13: JSONPath parser download no longer works.

Re-submit patch to match the commit 8457944

With the new Drupal installation , Latest dev of feed_ex (committed #11 patch) JSONPath parser is still missing. File is placed properly as /libraries/jsonpath/jsonpath.php (all in lowercase)

I won't reopen the issue. It is just that this is the first Google result that I got and for future reference I want to answer the last comment: @nithinkolekar did you downloaded and enabled xautoload? This worked for me.

@joco_sp
Thanks for answering an old question! Do note that the dependency on X Autoload is quite new, but there had been several issues with getting JSONPath parsers to show up. I hope all of these issues are fixed now in the latest release.

@MegaChriz yes, I noticed it in the README ;) Always read it :D hehe. Tnx for keeping Feeds going on! Really appreciate it ;)

Enabling xautoload worked for me.Thanks.