Profiles as nodes

I decided to go with the Bio module, since I have one type of profile, and fairly simple needs.

• When registering, people enter some basic contact info First Name, Last name and some info that will remain private, like phone number.
• When their application is accepted, they can create their "profile"... But I want to be able to keep the First Name and Last Name they originally entered on their registration form.
• I don't want them to use the "title" field for their name.

I really love this new module idea. Right now i am using Drupal 5,7. So,i can't use this module. I would like to use most likely Bio module or Node profile and collect the user information using CCK fields. Is it OK ? I mean i would like to use this module after my site code upgraded to 6.X. is that right approach ? or should i wieght ? My guess, once if i have this module, i just need to re-assain CCK fiels to content type related to this module. Am i right ...or too much imaginations ? Please advise me

Hi Everyone,

I'm trying to install http://www.drupal.org/project/phplist, but for it to update in the external php installation, have to replace profile.module fields (which we don't use) with our nodeprofile fields ..

Would you be so kind to point me in the right direction in replacing the fields for my phplist please?

Hi,

I'm trying to get my head around this and somehow just don't get it.

I have 2 roles, the normal 'authenticated' and a 'platinum' profile.

Both fill in the authenticated profile where they can select 1 listing (select list) in the business directory from a content type called 'directory'.

I would like the 'platinum role' to be able to choose 3 listings for the directory. How would I do that please?

Do I create a separate content type just for platinum users where they can choose their 3 listings in the directory or is there perhaps an easier way to do this?

Like many, I'm creating a networking site. While I'm new to Drupal, I've worked with PHP, HTML, CSS, etc. My question is what is the best way to allow a user to add multiple items to their profile? For example we'd like our users to add their work history to their profile. Since we can't tell how many jobs someone's had, we'd like the option for adding, editing and deleting each job individually (similar to LinkedIn). So do we create CCK modules to enter the information? Use nodes for each job and add a view for them on the profile page?

I'm creating a new thread for continuing the discussion of http://groups.drupal.org/node/8261.

I've just done some work and implemented a first prototype of the possible base module (variant 2) --> http://drupal.org/project/content_profile -> Test it!

This prototype allows to mark multiple content types as content profile, but tries to keep the code clean and simple. As nodeprofile had already the multiple content type stuff, I found it easier to start with it, and so I took the ongoing nodeprofile 6.x port, scraped features out of it, simplified the code and made it more extensible.

Recently I contacted the bio maintainers - I wondered if they are interested in joining efforts with drupal 6.x.

We 'd like to get input from the community, so I post my ideas here:

Is it possible to have a different cck node as a node profile for different roles? I have installed rolesignup - but my understanding is that it only helps decide which CCK nodeprofile edit form to display during registration.

In my case after registration and login all my users still end up having multiple "click here" to create profile links on their user pages one for each of the CCK nodes I enabled for "node profiles".

thank you for any help.

An interesting thing is occurring on my development site. basically a blank node (without a node type) is being created whenever a user visits his or her own profile.

I have not really found the complete source of the problem but I do know when I set the user to not be able to edit their own profile then it stops doing this.

Does anyone have ideas on the best way to find out how this is happening? I'm reluctant to set my site live like this as it could really grow the database out of control in no time.