This has been reported for news feed Aggregator 5.6, and I'm having it in Aggregator 5.7. (which I confirmed in another post)
The feed that was working perfectly for many months, suddenly stopped updating three weeks ago. I
t's not a cron problem. Running cron manually does not update the feed. Instead, Aggregator declares: The feed from New in DataBased Advisor ... seems to be broken, because of error "0 0".
"0 0" is the error stated by Aggregator. What the heck does it mean?
I haven't changed the feed URL in Aggregator, and if I open it directly in a browser such as Firefox I get a nice list of all the items in the feed.
The feed itself hasn't changed -- the XML and contents are still the same (it comes from an in-house system).
What's broken seems to be Aggregator, not the feed.
However... While the feed's DNS URL has not changed, the IP of the feed possibly changed around the time Aggregator broke. Is it possible that Aggregator is caching the IP of the feed, even though it "uses" the DNS of the feed? If so, where would this be, and how could it be reset?
Aggregator is a key component of Drupal, so it's rather disturbing that it has 100% failed. Others have been reporting this problem in Aggregator 5.6, and I have the problem in 5.7. There hasn't been a response, and no explanation of what error "0 0" means.
Comments
News Aggregator worked in 5.5, stopped working as of 5.6/5.7
What changed in Drupal 5.6 News Aggregator module, and is still broken in 5.7?
=-=
that can easily be learned by doing a diff or side by side comparion of the 5.5 version and the 5.7 version if anything changed.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
is there something wrong with my aggregator
hello
I am trying to get my aggregator to register the feed url that i put into the configuring box but when i submit it it always coming up with a url blank and an updated never...
I wondered what i could have done wrong if perhaps it could be something to do with the aggregator module 5.5 which I am using?
Chris
subscribing
subscribing