Postponed (maintainer needs more info)
Project:
FeedAPI
Version:
6.x-1.6
Component:
Code feedapi_node
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Apr 2009 at 14:59 UTC
Updated:
4 Jul 2011 at 12:13 UTC
After running cron, the feeds create new nodes. When I try to edit one of these nodes, I get this error:
warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'feeditem_node_form' was given in /nfs/c04/h01/mnt/60648/domains/###.com/html/includes/form.inc on line 366.
Comments
Comment #1
febbraro commentedThis looks like an error in FeedAPI, so moving it over there.
Comment #2
alex_b commentedThe argument for call_user_func_array() on line 366 in form.inc at this point should be 'node_form' - can't think of a reason why it's feeditem_node_form at this point.
Can't confirm the bug with 6.x-dev. Can you confirm this bug on a fresh installation of feedapi?
Comment #3
rovoHello,
I am actually using 6.x-1.6 instead of 6.x-dev. Do you think that would make a difference?
Thanks
Comment #4
r13ose commentedI know this is a 2 year old ticket, but I am getting the exactly same error message.
I have upgraded a FeedAPI 6.x-1.9 to 6.x-1.x-dev and I still have the empty nodes in there. Should I delete the empty nodes, and see if they appear again or just wait a bit and see what happens?
Here is the error I get when I edit the nodes: warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'feed_item_node_form' was given in /home/cdnd3026/public_html/includes/form.inc on line 377.
I asked someone to look into this and got this: feed_item_node_form exists as a 'node callback' from somewhere. It requested the function but cuoldn't find it, for whatever reason.
Update:
I just upgraded to Feeds Module and this solves the problem for me.
Comment #5
thomasmurphy commentedI have exactly this error (only matching result from google search), but I'm getting it on a CCK image field node?
Comment #6
thomasmurphy commentedI've made some progress on this. It looks like it's spitting that error out on nodes which were created with a different database configuration, e.g. when there were different modules enabled.