Hi
I have been thinking of this for a long time . Instead of associating a user type account with a profile wouldn't it be wise to associate it to nodes . It gives us much more flexibility to create content types using cck and there are various options and different cck helper modules which are available .
eg if I want to associate a gmap and location on the profile to capture user location it would be difficult on user registeration using profiles .
I have started working on it and I would like to work with u as well .
Pls provide me with ideas because it is still in the early development stage and i would need ur help and i would love to see it be part of user type module .
pls let me know wht do u think of it .
Eagerly waiting for the 6.x release . I hope it will be on friday .
Thanks
Juned
Comments
Comment #1
vijaythummar CreditAttribution: vijaythummar commentedYes i was also thinking this. If we use some thing like node profile, use profile or bio module then we can easily maintain and manage user profile.
Vijay
Comment #2
swentel CreditAttribution: swentel commentedMy first reaction was to set this to won't fix, on the other hand, I think it shouldn't be that difficult to implement. I'd split out the user types module in 3 big pieces:
I'll be working on a 6 release this friday - and I'll think about cck support as well a bit.
Comment #3
junedkazi CreditAttribution: junedkazi commentedswentel
I subscribe to ur suggestion . I think content profile (http://drupal.org/project/content_profile) is the one we should be looking at .
Let me know what do u think .
Comment #4
swentel CreditAttribution: swentel commented@junedkazi: I think we should focus on
a) node module
b) cck
and let user types know which node type it should act on. Once we have that working, every module out there that tries to create nodes from users can benefit from this.
The way I see it in the ui is simple:
a) on the user types settings page you define which node type is for the user.
b) every (cck)field has a fieldset with checkboxes of all existing user types to associate that field with one or more user types.
It's a simple brainstorm right now, but I think I can pull this off in one morning I think :)
Comment #5
vijaythummar CreditAttribution: vijaythummar commentedYes, If we use content profile then also we can use cck module for content profile and it will create profile as a node.
Comment #6
junedkazi CreditAttribution: junedkazi commented@swentel
The other day i was having a look at content profile and it satisfies most of ur comments in (http://drupal.org/node/316084#comment-1040460).
So i believe why should u do the same functionality again .
The only thing we should think of is
1) How to integrate the content profile with user types
2) Make sure the node is not submitted untill the email verification is done .
Let me know ur thoughts
Thanks for all the good work . Looking forward for much more amazing features . :)
thanks
Juned Kazi
Comment #7
swentel CreditAttribution: swentel commented@junedkazi
It seems that content profile now supports following features:
- autoassing of role
- different profile types also based on path
I haven't tested it yet, I will soon, so I think I might skip integrating that in this module. If you have time, please test out (might be the dev version, I'll do that also as soon I find some time)
*if* content profile supports that, I don't think I'll support it for D5 honestly, I think we should move forward from now on :)
Comment #8
swentel CreditAttribution: swentel commentedOk, I won't go on supporting CCK for this module.
For D6, there is a patch in content profile (http://drupal.org/node/313341) which handles this problem and nodeprofile for D5 allready has this feature too it seems (might be some tweaking to it though)