Closed (fixed)
Project:
FeedAPI Extensible Parser
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Apr 2009 at 21:53 UTC
Updated:
5 Sep 2009 at 17:40 UTC
Is there are some compatibility issues between FeedAPI Mapper and the Extensible Parser? Received the error:
Call to a member function init() on a non-object /sites/all/modules/feedapi_eparser/feedapi_eparser.plugins.inc on line 298
When tried clicking the "mapping" tab after enabling the parser.
Comments
Comment #1
neclimdulThis should have been fixed. What is the version string at the top of feedapi_eparser/feedapi_eparser.plugins.inc?
Also, what options did you set on the feed?
Comment #2
neclimdulThere have been so many code changes and bug fixes surrounding the code in question here that I'm going to mark this fixed. If it comes up again please reopen.
Comment #3
vgarvardt commentedThe same happened after update.
Fatal error: Call to a member function init() on a non-object in sites/all/modules/feedapi_eparser/feedapi_eparser.plugins.inc on line 444
I found why this happened, but still can't solve this.
This happened because of API changes - I have namespace plugin implemeted for my project and FeedapiEparserPluginBase::ensureNamespace does not load information about my namespace plugin.
I updated plugin code and updated hook_eparse_namespace_plugins() implementationfor my module, but still get this error.
I'm sure that I should call something or implement some hooks, but I can't find what. I implemented and then updated namespace plugin "by-example" because I did not find any docs.
Comment #4
vgarvardt commentedSorry, looks like it was my fault - this error seems to disappear after I cleared cache. Now plugin is loaded and almost works - problem with parseDate method, that calls parse_w3c_dtf method, that is not implemented anywhere. But this does not relate to this issue.
Comment #5
neclimdulThanks, I generally would prefer different errors to be in new issues so its easier to track credit for changes though. Makes making commit message confusing when you reference an unrelated issue.
Committed a fix.