Closed (outdated)
Project:
Feeds
Version:
6.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 May 2010 at 18:52 UTC
Updated:
16 Jun 2016 at 21:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
alex_b commentedThis shouldn't happen. Maybe at the time when the feed nodes were deleted, the importer was not configured for that particular content type?
Comment #2
boogsbobo commentedsame happened to me. I deleted a feed when the feed type was disabled. Had to delete the records from the database, but I only found them in feeds_source.
Comment #3
acb commentedExact same thing happened to me, creating all sorts of hard-to-track down phantom feeds.
Comment #4
alex_b commentedI follow now. Stuff's not properly deleted when importer is disabled before deletion. Attached patch solves this issue for the feeds_node_item table. feeds_source and feeds_schedule (job_schedule) is unresolved.
Comment #5
Vayira commentedSubscribing... when feeds nodes are deleted they are not removed from Job Scheduler. This seems to be the same issue.
Would it be safe to delete the offending rows from the Job Scheduler table by hand?
Acually I'm using 6.x-1.0-beta10
Comment #6
XiaN Vizjereij commentedSubscribing
Comment #7
dave reidCommitted #3 to Git: http://drupalcode.org/project/feeds.git/commit/1d60ac1.
This is also not a critical bug. Please do not abuse the priority field.
Comment #8
EvanDonovan commented@Dave Reid: It was actually alex_b who set it to critical :)
Comment #9
dave reidYeah, it's still an abuse of the priority field. :)
Comment #10
XiaN Vizjereij commentedShould be fixed now?
Comment #11
EvanDonovan commentedNo. alex_b said "feeds_source and feeds_schedule (job_schedule) is unresolved."
Comment #12
jamesgrobertson commentedI'm having the same problem. Just adding my two cents to watch the issue.
Comment #13
twistor commented