Difference from Content_profile?
ezra-g - July 3, 2008 - 17:18
| Project: | Rolespecific Node |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Lapino |
| Status: | active |
Jump to:
Description
What is the difference between this module and content_profile? Perhaps the two modules could be merged to avoid competing modules with duplicate functionality.
#1
Actually, I originally made this module as an addon for contentprofile, but I made it more general now.
Content profile defines a new type of node, namely the profile, while this module does no such thing, it only enables you to automatically create a content profile (or any other node) for all users with a certain role. This enables an administrator to create a content_profile (or any other type of node) for a specific role. This way, whenever a user is assigned this role, a content_profile (or other...) is automatically created for this user. If this user already has a profile, nothing happens, unless this node is unpublished, then it is published. If a user "loses" a role, his content_profile (or etc...) is unpublished.
So, this module does nothing that content_profile does, it just adds some extra functionality that makes life easier for an administrator.
Maybe the purpose will get a bit more clear with this example (and actually the reason I wrote this module): I am maintaining a website for a student's organisation and I wanted to have a special profile for the "board members". Now, some of those people don't login on our website very often, but I needed them to have a profile. Because I couldn't find an easy way for an admin to create a content_profile for other users and I can't expect the board members to login and create a profile themselves in appropriate time, I decided to create this module. So now, when I assign the "board member" rule to a user, a content_profile is automatically created for him/her and I can add some information in if I want to.
#2
>Because I couldn't find an easy way for an admin to create a content_profile
There is patch for this in the queue now. :)
Perhaps it would make sense to state on the project page the differences? So people are not confused and think this is another profiles as nodes solution.
Note: There is an simple API in content profile, that allows you to add further settings to its page. You could use that for adding a checkbox "automatically create this node for user with sufficient permissions" or so.
#3
Yup, I'll add something about the differences on the project page.
And for the api: I'll look into it, but I don't know yet if I'll add that, because, although it was originally intended to be an "add-on" for content_profile, it is more general now (and other uses are possible), so I'd like the configuration to be the same for all kinds of nodes. But if it really enhances usability or something, I'll think about it.
#4
Keep watching!!
#5
Automatically closed -- issue fixed for two weeks with no activity.
#6
Very interesting explanation and comparision..
I've found myself thinking about the whole relationship between content_profile and this rolespecific_node and still there's much similarity.
Wouldn't the inverse dependency make more sense?
To provide general api and functionality for rolespecific nodes and extend this with the special cases and tools for the content profile?
Thus making content_profile dependent of rolespecific_node as an addon...
A perfect combination and focus on genericity and extended functionality would make it a killer solution with no similar parts.
BTW: Does someone know exactly what Content Profile does and what's missing here? How would the specs change? What's missing in rolespecific_node's internals for this step?