Greetings,

A big lack of profile module is that it doesn't allow to extend its profile fields (as CCK does with node fields for instance). It is not possible to add a new profile field such as Category (Taxonomy reference) or any other type of a field with its own specifics.

Also, it will make profile.module source code to look much better because currently it has lots of field hardcodings...

Please, consider to implement some kind of such functionality because it is difficult to extend users' profiles now - to bind taxonomy to a user we need to use a bundle of modules such as usernode, nodeprofile and nodefamily which is a bad practice because profile fields will be distributed between profile and nodes, or we should not use profile.module at all in favour of nodeprofile.module

Thanks.

Comments

wundo’s picture

wundo commented
Assigned: Unassigned » wundo

+1
I'm working in this issue ;)

ardas’s picture

ardas commented

I wonder, how are you going to implement this?
I've got a crazy idea to make profile.module support CCK fields - this will help to avoid another bundle of fields needed for profile.module and their duplication with already existing CCK fields. For instance, CCK date field is quite big one ... so, will it be possible to use it for profile as well or we will need to create another profile date field?

I don't know is it possible to support CCK fields for profile at all .....

What is your opinion?

Thanks.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Version: 5.0-beta1 » 6.x-dev

Features go against 6.x-dev.

wundo’s picture

wundo commented

1I've got a crazy idea to make profile.module support CCK fields - this will help to avoid another bundle of fields needed for profile.module and their duplication with already existing CCK fields. For instance, CCK date field is quite big one ... so, will it be possible to use it for profile as well or we will need to create another profile date field?

I don't know is it possible to support CCK fields for profile at all .....

What is your opinion?

For now I'm rewriting profile.module adding a hook_profile, this would allow anyone (and any module) to implements new profiles types. This solves my problem allowing me to integrated my Drupal Profiles with another third party database and extract information from my users profiles in both sites.

I didn't studied CCK too much yet, but I guess maybe it can be integrated with profile using this hook.

wundo’s picture

wundo commented

Here is an version for drupal 4.7 ..
http://drupal.org/node/99355
Duke, please test it..

ardas’s picture

ardas commented

Greetings,

Wundo and me did some work to develop an extensible profile module http://drupal.org/project/profile-ng which allows to create profile fields for it.
Please, review this thread http://drupal.org/node/112706.

I've attached an archive with new profile module for Drupal 5.0 and two profile field modules. All of them are still not perfect but they work.

Profile authors, please give some feedback about this work and your plans - are you working on something like that or will users be inherited from nodes in Drupal 6.0 or later and you consider this work to be superfluous?
May be you can suggest another approach to extend profile fields and help us to move on in a proper direction.

Thank you.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Version: 6.x-dev » 7.x-dev
Assigned: wundo » Unassigned
Status: Active » Postponed (maintainer needs more info)

I think profile fields are quite extensible.. please specify the list of requested features against 7.x-dev..

sun.core’s picture

sun.core commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Users are fieldable in D7 already.