When saving a Feed API node that refers to a feed that can't be accessed, or is invalid, the node gets saved and there is no alert to the user that the parser hasn't been able to parse the content. Further, when going back into that node, the Feed URL is not saved. It only seems to be saved when there is a valid feed URL entered, and feed items are retrieved from it.

I am using the Common syndication parser when seeing this issue, so I don't think this is related to #260670: Feed URL is discarded, feed items not saved. I'm seeing it when trying to access a feed at http://example.com/feed (i.e. where one doesn't exist) and on an https site that has an invalid certificate (which is likely making it inaccessible).

I consider it a bug that the feed URL isn't saved, but it's more of a feature request that it doesn't alert you to the problem of having an invalid feed.

Comments

geerlingguy’s picture

geerlingguy commented
Version: 6.x-1.2 » 6.x-1.7-beta3
Component: Code » Code feedapi (core module)

Seconded - I was about ready to give up on this module altogether and write my own system until I found this issue; I only then realized that since the feed was on a secure connection (https) and the server's security certificate was invalid, the feed wasn't working. (Still an issue with 1.7-beta3)

After I figured that out, I moved the feed off the secure connection, and it's working great!

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented

Well, to keep an eye on how your feeds behave, maybe a new submodule will land in feedapi. So yeah, a method is definitely needed to know what's happening inside feedapi.