I'm currently using Follow on my social network for filmmakers to allow users to link their profiles to Facebook/etc.
I'd like to add the ability to follow Nodes (enabled for all content of a given type) so that users can link their content on my site to the respective pages on other networks.
example:
User creates a Facebook page for their "film project".
User creates a "film project" Node on mysite.com.
User links their node to the facebook page via Follow module.
Any thoughts on this? I like Follow but is there another module that will accomplish these tasks? My only option right now is to add a "link" field and label it "Follow this project on XXXX" but that could get bulky...
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | allow-user-argument.patch | 771 bytes | dago.aceves |
Comments
Comment #1
q0rban commentedHmm.. interesting.. I think this has potential, but would need some rewriting to happen with follow module. Currently follow module uses a user id (uid) to store the different follow links, but this would need to be changed to have a namespace or object type column or something, so you could have it be a keyed accross both columns.
I'm open to patches.
Comment #2
dago.aceves commentedI think you have a similar issue to what I had. Eventually I just needed to be able to invoke the follow block where ever i wanted. Here's a patch that lets you invoke your follow block just knowing the uid.
// invoke block on advanced content node.
$block = module_invoke('follow', 'block', 'view', 'user', array('uid' => $node->uid));
print $block['content'];
Comment #3
dpatte commentedActually, i'm looking for something similiar, but I'd like to display the users follow block on any node the user has authored
Comment #4
dpatte commentedi modified the patch in #2. if you want what I wanted iin #3, the following works for me
Comment #5
grasmash commented@dpatte Your patch seems to be for a different issue. If I understand @scottmotion correctly, he'd like to be able to define different follow link values per node.
I'm also interested in this feature. It seems like the best way to accomplish this may be to actually create a Follow Field via the Field API. This way, you can define follow link values per node and per user. @q0rban, does that seem like a good idea?
The other path would probably involve adding a new 'type' field to the database schema. This could have the value node, user, or system. The uid column could then be changed simply to id. This would allow us to store values for node ids, user ids, and recognize the system wide settings.
Thoughts? I'd be happy to submit a patch once we decide the right development path.
Comment #6
astonvictor commentedI'm closing it because the issue was created a long time ago without any further steps.
if you still need it then raise a new one.
thanks