Hi,
I ask kindly to implement a new simply feature to "Put in Standby a Feed Node".

I also report a strange behavior by Feed Nodes.
It is not possible to stop the future scheduling for a single Feed Node, so I try to change rss url inside Feed Node, using a fake rss url. So, if I import feeds item manually I get error 404 (of course), but Feed Importer schedules always the import on cron, and this works properly importing Feed Item.

Is it possible to stop scheduling for every single Feed Node?
is there something to fix about the strange behavior reported?

jscm
Milan (Italy)

Comments

alex_b’s picture

Status: Active » Closed (duplicate)

#662110: Pause single feed nodes

but Feed Importer schedules always the import on cron, and this works properly importing Feed Item.

Hard to say what's going on here. I would review the feeds_source table to find out.

jscm’s picture

Title: Feed Node Strange Behavior about Scheduling when you change correct RSS Url with Faked Url » Put in standby a Feed Node and Strange Behavior about Scheduling
Status: Active » Closed (duplicate)

Hi,
2 days ago I changed RSS Feed http://feeds.feedburner.com/Blogmotori with faked http://feeds.feedburner.com/BlogXXXXXXXXXmotori

You see that I don't insert a new RSS URL Feed but I changed URL already inserted.

In feed Source table for specified Feed Node there are these settings:

id
feed1

feed1_need
6378

config:
a:1:{s:16:"FeedsHTTPFetcher";a:1:{s:6:"source";s:47:"http://feeds.feedburner.com/BlogXXXXXXXXXmotori";}}

source:
http://feeds.feedburner.com/BlogXXXXXXXXXmotori

batch:
b:0;

So, In these 2 days Feed Node has created Feed Node Items from correct RSS Feed http://feeds.feedburner.com/Blogmotori but RSS URL inserted is faked.

I don't know what's wrong! I know that this strange behavior there is since first alpha release.

Have you an idea to correct this?

jscm’s picture

Title: Put in standby a Feed Node and Strange Behavior about Scheduling » Feed Node Strange Behavior about Scheduling when you change correct RSS Url with Faked Url
Status: Closed (duplicate) » Active
jscm’s picture

Title: Put in standby a Feed Node and Strange Behavior about Scheduling » Feed Node Strange Behavior about Scheduling when you change correct RSS Url with Faked Url
Status: Closed (duplicate) » Active

Hi,
are you able to reproduce the problem?
Do you want more details, DB export, etc etc ?

alex_b’s picture

Category: feature » support
Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)

You must find that feed in the feeds_source table, otherwise we're looking at a miracle here. Have you looked at all sources and made sure that the 'phantom' feed in question does not exist?

jscm’s picture

Status: Needs review » Postponed (maintainer needs more info)

I done a new test...

In feed_source table there isn't phantom and i have:

id 2704
with this faked url http://feeds.blogo.it/calcioblog/it-XXXXXXXXXXXXXX

BUT.. In feed_pub_subscription table there is this:

subscriber_id: 2704
hub: http://pubsubhubbub.appspot.com/
topic: http://calcioblog.it/rss2.xml

This topic http://calcioblog.it/rss2.xml is equal at url http://feeds.blogo.it/calcioblog/it

So Maybe I found the PHANTOM in the feed_pub_subscription table.

Is it possibile? Can you verify?

jscm’s picture

Status: Postponed (maintainer needs more info) » Needs review
jscm’s picture

Status: Postponed (maintainer needs more info) » Active
alex_b’s picture

Title: Feed Node Strange Behavior about Scheduling when you change correct RSS Url with Faked Url » PubSubHubbub: Update subscription when URL changes
Version: 6.x-1.0-beta9 » 6.x-1.x-dev
Category: support » bug
Issue tags: +PubSubHubbub

#6: you found the problem.

What should happen is that the PubSubHubbub subscription is updated if a feed URL changes. Apparently that does not happen.

This is a bug. I won't be able to work on this atm, though.

I have also made a note on #662110-11: Pause single feed nodes that we need to ignore PubSubHubbub notifications if a subscription is paused.

jscm’s picture

Great!...
I am very happy to give my help.

kenorb’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

Closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.