Closed (fixed)
Project:
FeedAPI Extensible Parser
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Sep 2009 at 15:56 UTC
Updated:
13 Oct 2009 at 16:30 UTC
Jump to comment: Most recent file
Comments
Comment #1
eterps commentedSame here.
Fresh Install of Drupal 6.13
php 5.2.9
Extensible parser is the only parser enabled. Only a handful of Core modules enabled, along with CCK, views, administration menu, ImageCache, Panels, Pathauto, Token.
Processor: FeedAPI Node
Example feeds:
http://feeds.gawker.com/lifehacker/full
http://news.google.com/news/section?pz=1&topic=t&ict=ln
Comment #2
neclimdulThis means that ctools wasn't able to find your parsing plugin. What version of ctools are you using and what options have you setup in the EParse tab?
Comment #3
eterps commentedI'm using CTools 1.0 released on Aug 19.
Eparse settings:
Download Type: Drupal HTTP Request
Feed Type: RSS 2.0
Comment #4
stian commentedI get the same problem.
I did some further digging though.
It seems like the ctools settings form doesn't proceed to the next form when you press next, resulting in no settings get stored to the database.
Then in feedapi_eparser_load_type_plugin() when you try to load settings, there is no such thing as $efeed->eparse->type.
This whole function then ends up returning false, which naturally has no parse() method ;)
Would it be possible to throw Exceptions at the plases you just return nothing from the function? Or are we still bound to php4?
I see some other scenarios where this error could show up, where you in line 79 presumes you get a class back, when you in several fault cases don't return anything.
I'm using ctools 1.0 Aug 19 and eparser 1.0 8 Sep on Drupal 6.12.
Edit: Some typos
Comment #5
emTque commentedI get the same error, using:
- ctools 6.x-1.0
- eparser 6.x-1.0
I also no other parsers installed.
Comment #6
summit commentedSame problem, newest feedapi, newest ctools, greetings, Martijn
Comment #7
b-prod commentedHi!
I work with the dev version. For this version the problem is the same, but with method fetch() instead of parse(). Actually the method is called without checking before if the object has been instanciated.
So I have added a simple check which returns FALSE (so feedAPI module will display an error message too) and displays an error message with a link to the settings tab.
The patch below works for DEV version, but for the released version the only thing to change is the name of the method as explained above.
Comment #8
killes@www.drop.org commentedThe error message doesn't make proper use of the t() function. The proper way is to include the html tags inthe message.
This review is powered by Dreditor.
Comment #9
b-prod commentedHere is a new patch with a valid use of t() function (thanks to killes).
I also changed the type of message displayed to warning instead of error, which seems to be more appropriate.
Comment #10
neclimdulLooks good to me. You could have probably update the issue it to needs review with your last patch though :-D
Thanks! Committed.