SimplePie Not installed
SimplePie library is required for Feeds SimplePie Parser. Download the compiled version of the library from SimplePie download page.
Woke up this morning to find the above request on a site running Feeds with the JSON path parser and image grabber installed. As far as I can tell neither feeds core, JSON Path parser or Feeds Image Grabber require this library to run. I did do an update via drush a few days ago to feeds but at this point have never installed the Simple Pie module for feeds.
Any idea why this would be showing up now? I've cleared caches etc and I don't even have the Libraries module installed right now so have no idea where the system even wants me to put the library!
thanks
| Comment | File | Size | Author |
|---|---|---|---|
| #26 | feeds-simplepie-requirements-1981504-26.patch | 3.26 KB | twistor |
Comments
Comment #1
donSchoe commentedhaving the same issue. no idea why feeds is suddenly requirering simplepie.
in addition, it's totally unclear how to install simplepie.
any ideas?
see also #1803140: Simple Pie library Not installed.
Comment #2
pancho#1:
This has nothing to do with the legacy SimplePie module. Feeds doesn't need it to leverage SimplePie.
#2:
feeds_library_exists() wil be looking for SimplePie in both 'sites/all/libraries' (if libraries module is installed) and 'site/all/modules/feeds/libraries'. If you use libraries module anyway, then 'sites/all/libraries' is the recommended place.
Either way:
Just create a subfolder 'simplepie' and download the compiled, single-file version into it.
Now unfortunately you need to rename the file to 'simplepie.compiled.php' because that is what Apps is looking for.
Works.
Comment #3
panchoUntil here, this is a support request.
We should work on some followups, though:
Comment #4
Dale Baldwin commentedOk so can someone tell me why all of a sudden simplepie is requried? My feeds work fine without it and I haven't seen it listed as a dependency on any page related to the feeds module.
Comment #5
twistor commentedIt's not required at all unless you're using the simplepie parser.
Comment #6
Dale Baldwin commentedAbsolutely, which is why it is odd that it even shows up in the status report.
Comment #7
islalobo commentedI agree that it is a strange notification to have when not using the simplepie module. Is there a reason why this appears now? It has never appeared before (that I remember)
Comment #8
grahamvalue commentedCan "Feeds SimplePie Parser" be made into a submodule and the status-page warning be shown only when the submodule is enabled?
It's confusing to have a warning in the status-page for a feature that is not being used.
If more modules start adding their own warning messages for unused features, the system status-page will become impossible to use.
Thank you for a great module!
Comment #9
boabjohn commentedSorry to clutter this queue, but until a more sensible approach is applied to Feeds, and for those (like me) that find it hard to put all the pieces together, here you go:
1. The "compiled version" of simplepie is available under a little link below the main download link:
SimplePie download site: http://simplepie.org/downloads
Direct link to compiled version (at the time of writing): http://simplepie.org/downloads/simplepie_1.3.1.compiled.php
2. Upload this to your sites/all/libraries folder (assuming you have the libraries module running, which is always a good idea)
3. Create a new folder in /libraries/ root called simplepie, and shift the uploaded file into place.
4. Rename the uploaded file to simplepie.compiled.php, so now you should have: /sites/all/libraries/simplepie/simplepie.compiled.php
5. Clear caches, and you should be good to go.
Comment #10
grahamvalue commentedThank you for the instructions, boabjohn.
They work great!
It seems to work just as well if the file is directly uploaded to the sites/all/libraries/simplepie folder though.
Is there any specific reason to first upload it to sites/all/libraries and then move it?
Would still be a good idea if the module maintainers could make "Feeds SimplePie Parser" an optional submodule.
Thanks all!
Comment #11
boabjohn commentedNot at all...after I hit the [publish] button the same thought occurred to me. It's just that I had first tried to just run the file direclty...only later to *RTFM* again and realise I needed to create a directory too. So the indirect upload thing was just an artefact of my own exploratory process.
I'm sure these guys will track down a solution in good time: it always amazes me how much generosity they show in the first place. We all have a big debt of appreciation to "the community" who keep this Drupal afloat.
Comment #12
grahamvalue commentedAbsolutely, boabjohn.
A big Thanks to the Drupal community and the Module maintainers!
Comment #13
theohawse commentedOkay, so basically what you guys are saying is that the simplepie portion of the libraries in the makefile should look like this?:
Comment #14
boabjohn commentedHmmm...you got me. That seems a bit outside the issue thread which is essentially about why simplepie is showing as a dependency even when it is not being used.
Your makefile above seems to simply force simplepie into the libraries module come what may...I wouldn't mind, but some people would.
Or maybe I've got the wrong idea.
Anyway...installing simplepie does silence the error.
Comment #15
ey commentedThis is not a support request, instead a bug report, since it gives a notice about a library which is neither installed nor needed. So a workaround like to download an unnecessary library to get rid of the notice is not a solution.
Comment #16
theohawse commentedSuppose the solution then, would be to move the simplepie parser, along with it's libraries api dependency to a new submodule; either bundled with feeds or on it's own.
Comment #17
Chris CharltonA newer, nicer link to the compiled include file is: http://dev.simplepie.org/SimplePie.compiled.php
This link is mentioned on the Github page for the project.
I noticed the status message went away when I added the file to
sites/all/libraries/simpliepie; file needs to be renamed to 'simplepie.inc', but other modules are looking for 'simplepie.compiled.php'... fun.Comment #18
achtonI agree that this is a bug - I can use the Feeds module without adding SimplePie to my system, so it can't be a requirement. And I like my status reports green :-)
Bug instead of moving code to a submodule, perhaps another way to solve this could be to add a check to feeds_library_exists() that detects whether any SimplePie parsers even exist? That way, the requirement would only be triggered (probably as REQUIREMENT_ERROR now) if the library is actually supposed to be there.
Another approach would be to simply remove it from hook_requirements() altogether and instead present a drupal_set_message() on the Feeds admin page if SimplePie is missing and you are about to create SimplePie feed.
Comment #19
scrm000 commentedsolution #9 did not clear the the status board.
This did not work for me
/var/www/html/drupal/sites/all/modules/libraries/simplepie
-rw-r--r--. 1 root root 446731 Oct 30 2012 simplepie.compiled.php
-rw-r--r--. 1 root root 446731 Oct 30 2012 simplepie.inc
Comment #20
scrm000 commentedhold on-let me play with permissions for a sec
Comment #21
scrm000 commentedA) README.txt in feeds cleared board
B) creating the .inc file
mv simplepie_1.3.1.compiled.php simplepie.inc
and a clearing of cache
http://www.inmotionhosting.com/support/edu/drupal-7/configure-caching/cl...
/var/www/html/drupal/sites/all/modules/feeds/libraries
-rw-r--r--. 1 root root 446731 Oct 30 2012 simplepie.compiled.php
-rw-r--r--. 1 root root 446731 Oct 30 2012 simplepie.inc
showed the new parser options
Comment #22
nancydruI followed the instruction in #9, mostly. I do not put such things in sites/all; I put it in sites/example.com/libraries. I still get the message.
Comment #23
boabjohn commentedHey @NancyDru: I have not read the module'ss code, but look at #2 up there...the module is probably hardwired to find the library in exactly one spot, named exactly one way.
So: if you can get to your web server with a shell or if your FTP client allows you to, one idea is to create a virtual link between the path that is required and your actual location.
If you're normally running multisite installs (I assume that's why you put the /example.com/ in your modules path?) then wouldn't you still benefit from having a single common insstall directory for your modules?
Cheers,
JB
Comment #24
nancydruThanks, Josh. I briefly looked at the code and there were several possible locations. I did not track them all down.
I develop on a Windoze PC, so symlinks are not an option. I do not put Feeds on many of my sites and it is only on this site so someone else can import node data.
No, I do not like the single modules directory because I am often on the bleeding edge (especially when mucking with Fields) and don't want things affecting more than one site. I've just really gotten to prefer site-specific directories and usually use them even for single domain sites.
Comment #25
drupalsat commentedsolution #9 did not clear the the status board. I had to leave the subfolder simplepie away and put the renamed file directly in the libraries folder, for me: 'sites/all/modules/feeds/libraries'
Comment #26
twistor commentedHow about this?
We only make the note about SimplePie REQUIREMENT_INFO, rather than REQUIREMENT_WARNING. But, if you have a simplepie parser enabled, it becomes an error.
I'm tempted to remove the notice all together, and only show the error, but then there's a problem with discovery, because the plugin will be hidden until the library exists. This could be solved with documentation.
Who has an opinion?
Comment #27
nancydruMy opinion is to remove it.
Comment #28
fgjohnson@lojoh.ca commented#21 was my solution.
/sites/all/modules/feeds/libraries/simplepei.compiled.php
Comment #29
ThePeach commentedgiven the fact that simplepie has ceased development, I'd suggest to remove its support altogether.
Haven't tested the patch, just stumbled on this issue as I was getting the same warning.
Comment #30
basvredeling#26 is a nice approach.
I'd say the most reliable option is to move the library to /sites/all/libraries/simplepie/simplepie.compiled.php and updating module documentation or requirements info accordingly.
Comment #31
enorniel commentedMy opinion is that the Status report must represent the real status of the installation.
It is a need if you use an external monitoring. If the external monitoring finds a warning, it will display it and flood your monitoring system with irrelevant datas.
So, the warning has not to be displayed if SimplePie is not used.
Comment #32
jenlamptonThank you so much for this patch :) The simple-pie nag message on my site has been bothering me for some time, and needlessly. After applying the patch this problem is solved :)
Comment #34
twistor commentedComment #36
kebz commentedI was getting the same status report notification to install SimplePie library when SimplePie module isn't even installed.
I had just installed the module recently (14JAN2015).
I reviewed this page and the workarounds for it and I agree with many who say that we shouldn't have to do workarounds nor install SimplePie.
So today, I disabled and uninstalled everything "FEEDS" (Feeds_tamper, Feeds_xpathparser, etc.) ... and then I re-installed them all. For whatever reason, the status notification is no longer showing up.
One additional "new thing" I did today was update my PHP from 5.5 to 5.6.4 --- would that have anything to do with it?
Anyhoo... I didn't have to use the patch nor install SimplePie ... hope that helps anyone else getting this notification.
Comment #37
fmantov commentedI've solved the SimplePie issue in Statur Report in two steps:
1) upload simplepie llibrari in site/all/libraries/simplepie
2) disable SimplePie core module (that apparently is useless)
Comment #38
alauddin commented#9 still works great
Comment #39
ad0nai commented#9 work for me.