I was tossing up whether this issue should live on Profile2 issues or here. Hopefully I've got it right.

Had a hunt through the Issues forum here and on Profile2, but didn't find any post that details a solution for what I need.

I have multiple Profile types (Student, Instructor) and they share fields like Phone, Address etc. I have added these common fields to the core user, and only added fields specific to each user type in the Profile types.

What I'm struggling with is trying to show the User fields before the Profile type fields during user registration.

I have configured Profile2 Registration Path, but when I navigate to the rego page, the Profile2 fields display first, then the user fields.

If I select Show on all user account rego forms, I can position the Profile: Student fields in the Manage Fields so the User fields come first, but the Profile2 fields are wrapped in a fieldset, and I don't want that. I'll have to hide this wrapping using CSS.

If I deselect the above setting, the Profile2 fields always show first.

How do I stop the Profile2 fields being wrapped. Or how do I just position them before the Profile2 fields without having to show them on all rego pages?

Comments

Spanners’s picture

Any help with this? My email field now shows first and then the Profile2 fields, then the rest of the common user fields. And example can be seen here on my staging site:

http://fifthgear.com.au.103-23-153-221.simonolsen.com.au/student/register

Happy to PM login details so you can have a look at my config.

hockey2112’s picture

My user fields (such as "email" and "username/password") suddenly dropped below several Profile2 fields on the registration page. MY fix:

  1. Go to /admin/config/people/accounts/fields.
  2. Click "Show row weights" above and to the right of the fields.
  3. I then gave Email and Username/Password a weight of -999 and -998, respectively. They then moved to the top of the list on the registration page, since they have the lowest numbers.
StephanTeo’s picture

Thanks @hockey2112 - this fix worked for me. :-)