This is dependent on #293318: Convert Aggregator feeds into entities
Aggregator keeps users from adding the same feed more than once. While this is sane behavior in a simple news aggregation scenario, it is a serious and unnecessary limitation in a multi user or a multi feed type scenario. Especially once #293318 lands.
E. g. a technique we use often with FeedAPI is to allow users of a certain role to add feeds to their profile. A relationship between a feed node and a user id keeps track of who added which feed. We allow adding feeds that are already in the system. The processor that creates feed items allows many feeds to one feed item relationships. Thus we create a many users to one feed relationship at the minimal cost of having duplicate feeds (provided there is good caching on the fetching and parsing level).
Per default, aggregator should continue to not allow duplicate feeds. It is a simple and straightforward behavior and alternatives quickly become complex - but contrib modules should be able to override this.
* Remove unique key from aggregator_feed.url and aggregator_feed.title field
* Make sure aggregator_form_feed_validate() checks are overridable.
Comments
Comment #1
Jody LynnComment #2
jhedstromProbably a feature request at this tim.e
Comment #15
quietone CreditAttribution: quietone at PreviousNext commentedThe
aggregator
module has been removed from Core in10.0.x-dev
and now lives on as a contrib module. Issues in the Core queue about theaggregator
module, like this one, have been moved to the contrib module queue.Comment #16
larowlanI would think something like flag would allow association between users and feeds