I just tried to use the latest stable AND development releases of FeedAPI. They are not functional as nothing is being stored in ANY FeedAPI database tables. Only node specific information is saved on Node creation, the tables feedapi, feedapi_node_item, feedapi_node_item_feed, feedapi_stat remain row free.

I'm using SimplePie 1.1.3 but can't see how that would be related.

Comments

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Status: Active » Postponed (maintainer needs more info)

Do you see any error messages after creating the node?

matt_harrold’s picture

matt_harrold commented

No, it saves the node without errors, adds any taxonomy terms and CCK fields, the Node Title and Body, but the information specific to FeedAPI does not "stick".

Chris Johnson’s picture

Chris Johnson commented

There appear to be a couple general problems causing this behavior in concert:

1. FeedAPI creates the node in the node table, even if an error results in the feed NOT being created in the feedapi table.

2. FeedAPI does not log nor report errors in a reasonable way. If a feed is not valid, the user should get some sort of feedback immediately upon saving the feed node, via, e.g. drupal_set_message() or form_set_error().

This is easy to duplicate. Simply create a new feed node, use the common syndication parser, and provide the URL of a feed which does not strictly follow the specifications, e.g. a Views generated feed with a leading whitespace before the clause. The node will be created, but the feed will not. There will be no message and nothing logged to watchdog.

Chris Johnson’s picture

Chris Johnson commented
Status: Postponed (maintainer needs more info) » Active
matt_harrold’s picture

matt_harrold commented

I've tried numerous feed sources (known to be valid) and all fail. I've had to sideline the whole idea for now .... as I have heaps of other stuff to do. I don't think it is as simple as a "bad feed" crash.

Feel free to ask me details ... but be specific ... I don't know where else to "hunt" a solution.

fxarte’s picture

fxarte commented

The same thing happened to me. And it happend after I made the core update to 6.14
I'm using core 6.14 and FeedAPI 6.x-1.7-beta1
I made a test in my local PC with the 6.x-1.x-dev version and it was solved. But other issues happened.
I think it might be related to the core update to 6.14.

bertboerland’s picture

bertboerland commented

#6, got the same setup and I do think as well that this is related to 6.14

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Status: Active » Fixed

"I'm using core 6.14 and FeedAPI 6.x-1.7-beta1"

http://drupal.org/project/feedapi
Note: FeedAPI versions lower than 1.9 are not compatible with Drupal 6.14 or higher (see #580508 for details).

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Status: Fixed » Closed (duplicate)

sorry, it's dupe actually