Ability to attach a feeds source to any entity, not only nodes [#1257314]

It should be possible to attach a feed to any entity, not only nodes.
This can enable many use cases where non-node content has to be created that should trigger new imports.

This is related but not identical to #1033202: [Meta] Generic entity processor.

Original Summary

This is the first time, when I'm working with feeds in a D7 project, so I don't know, is this right:

In some case we don't need to create a new content type for feed sources. Now, I don't need a full node, to store this feeds. I don't use path, comment, fields, views, etc. I only wan't to store 4-5 feeds, but it should be expandable, without cloning an importer, that uses standalone form to store the feed url.

As I know, in this case the perfect way should be to create own entity, and use this as import source. Isn't it?

If it is, it would be nice, to expand "Attach to content types" on basic settings to use any entity type. (Another usecase should be, that a user may add a blog to import)

Comments

Comment #1

geek-merlin

they/omg

German

Freiburg, Germany

CreditAttribution: geek-merlin commented 17 April 2012 at 09:13

Title:	Using entity instead of attach to content type	» Ability to attach a feeds source to any entity, not only nodes
Component:	Miscellaneous	» Code
Priority:	Normal	» Major

another use case: import a tree of terms from a web page.
would be easy and elegant if we can attach the source to a term that will import its children then.
when only nodes can be feeds sources, like it is, its a major PITA.

daring to clarify title and raise prio as this is clearly "the D7 way" to do it.

next step might be an implementation plan.

Comment #1.0

geek-merlin

they/omg

German

Freiburg, Germany

CreditAttribution: geek-merlin commented 17 April 2012 at 09:22

Issue summary:

View changes

clarified

Comment #2

tassaf CreditAttribution: tassaf commented 28 April 2012 at 08:51

Thanks .. is there any solution to import tree of terms?

Comment #3

steinmb CreditAttribution: steinmb commented 5 June 2012 at 12:59

A big +1 from me to. Any ide how we should move this along?

Settings form configForm() uses node_type_get_names() but should be swapped out with the entity eq. function perhaps entity_get_info() or field_info_bundles(). I'm just guessing here and have now clue how hard this can be to change.

Comment #4

geek-merlin

they/omg

German

Freiburg, Germany

CreditAttribution: geek-merlin commented 8 June 2012 at 15:27

this change would imply changing the database schema, so that any entity can be referenced.
so this should be a new major feeds version.
and if we put our hands on it we might want to make feeds fullblown entities and use entityreference fields.
which would make the whole party much more configurable.

in daily business i work my way around this issue, but if there is serious interest in having this implemented as a paid job, i might love to dig into this and work out a plan.