Hi, I'm the maintainer of the following modules:
Block reference - Inserts blocks into a node.
View reference - Inserts/links Views displays in a node. Viewfield has become a lot like View reference now, but with a slightly different set of features - so that is another project that might be worth thinking about now too.

I have also contributed to:
Revision reference - Like node reference but does it by the revision.

And I've done work towards Field reference which I have not completed, and I tried to make an "Any reference" consolidation module a couple years back which wound up being a massive failure at the time that I intended to revisit, and I think you guys have a better idea with the Relation module.

I also maintain a couple of Node access modules which give access depending on values in CCK reference fields, and I know of at least one other module that does a similar thing based on any relationships a node might have to something else the user is permitted to see.

People have been asking about D7 ports, and I've held off knowing that things might change quite a bit for D7.

Now my questions are:
Is Relations an API module that I would create plugins for?
Or will the information about entities come from another source?
Are 'blocks', 'views/views displays', 'revisions', and 'fields' supported with the new infrastructure?
In general: how can I move away from maintaining or contributing to separate reference modules and move the users over to the new system?

I know it might be early days for Revisions, but I'd like to think ahead a little and see if I need to make any considerations in the meantime?

I have various features in this modules, other than the 'entities' they reference, which would need to be supported by this module if I were to provide an upgrade-path for users, or at least a way given so I can hook in and provide these features. I will compile a list once I have a better understanding of the Relations module. One of the struggles I've had is that when a particular feature was added to one of these reference modules, it had to implemented seperately for the others - or sometimes forgot to do it at all, and I've always dreamed of a common way to add features to all reference modules, which is another reason I'm excited about the idea of Relations.

So I'd appreciate some feedback, and guidance about how I can learn more.

Comments

naught101’s picture

Hi danielb,
The module is pretty basic at the moment. It creates unidirectional relations between entities. Since revisions, blocks, views and fields (usually) aren't entities, this module isn't going to be able to form the basis for any replacements for the module you're talking about.

- API: none planned so far, but possible. I haven't thought of any use cases yet. got any?
- Sorry, information about which entities?
- nope (see above). Any fieldable entity will be supported, and of course relations will be accessible to views.
- damn good question, for which I have no answer. Perhaps you should abtract all the common stuff from those modules you mention into an API? Also the http://drupal.org/project/references module is probably looking for collaborators, and might be open to adding some of this stuff.

Where it's headed in the long run is a but up in the air, but you're definitely welcome to join in the discussions that are currently happening. Check out the other issues on the queue, and download a copy and play around with it.

Interested to see your features list!

sun’s picture

Status: Active » Fixed
quazardous’s picture

hi,

is this module linked with entity (metadata) module ?

'cause i use search api and search api is based on entity (the module) and so i can browse from parent bundle to related bundles ...

will relation provide bundle wrapers ?

danielb’s picture

OK naught101, maybe I've got the wrong idea about this module. I was under the impression it was gearing towards a replacement for http://drupal.org/project/references, except I suspected it would generalize the functionality away from node/user. References appears to suggest it is a temporary project until Relation can replace it.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.