Extensible field types in Profile.module.

Whats the chances of getting this to work in the HEAD version (5.x)? I had a look using winmerge but unfortunatly, the code isn't commented to say what you have added and removed and I don't just want to start merging code if you have used the old API.

This patch will be very handy for me, as I am looking at building a hCard generator from the profile fields, and this feature is exactly what I need before I start going off and building it myself.

I've looked through the code and compare with the core profile.module.
It is very clever idea to use hooks in profile. This will give everybody an ability to create specific fields. I think now that if even CCK fields won't be supported by profile module we can base profile field modules on CCK modules without any problems, or create patches for CCK module which will implement new profile API.

I have updated my old profile module in the current project and am going to test your one and study it. I'll report you about my results shortly.

Thanks a lot.
I'm eager to take part and help with this module.

no new features in 4.7

Hello,

I'm testing new profile module. It looks good. Create/Edit/Save operations look working correctly.

I have one question for now: why did you decide to reorder form fields? I noticed Page title field and Selection options (for List field) were moved on the top of the form. Were there any special reason or you just missed the Order attribute?

Thanks.

By the way, I did some propositions concerning profile.module but looks like its original author don't care too much or very busy with other work.
You may find them useful for the new version you create ... and they are extremely easy to implement :).

1. The first one is an ability to customize keys for lists described here http://drupal.org/node/89468.
2. The second very small and a simple issue is a small range for profile fields Weight attribute http://drupal.org/node/92343. Just change delta to 50 instead of 5.

If you are developing a new profile module you may include all useful features to improve it.
Thanks.

Looks like a bug with list selection field.
1. Create a list with two items 0 and 1.
2. Save this field.
3. Edit this field.
ISSUE: Selection options text area is empty dispite the fact that options were saved into the database.

how are these hooks better/different form the ones already provided within hook_user(). just wondering.