New profile fields added to registration form show above Account Information.

For more information, reference the following topic: http://drupal.org/node/114083

When a solution is found or a bug is fixed, is it possible to offer the completepatched module file(s) in addition to the patches ?

It would be nice if you can also offer in addition to the patches, the complete updated module files with the patches already applied. Some of us users are not PHP programmers and find it difficult to edit code. It is also confusing when multiple patches are offered, which ones to apply, 1, 2, or all of them.

I just want to introduce some simplicity to this process so that all users can benefit.

Thanks

Sam308

Yes, this is VERY confusing to new users, because all my general instructions for what fields to fill in is presented AFTER the form fields themselves.

I tried adding different categories of profile fields, and _sometimes_ they will appear BELOW the account information fields, but there are always some that remain above it. Very strange behavior. I am trying to see a pattern....

--Neil

I've just encountered this bug in the new security release of 4.7.6 as well. It's the profile module, which is now setting it's weight in the user registration/edit form. In 4.7.6, you'll see the line

$w = 0

was added. I fixed mine by setting it to 1 instead. You could also fix it within your theme using the forms api, but I think I'd call this a bug siince this default behaviour is clearly not desirable.

Ahd here's a patch.

Changed the version and status.

applied to the 4.7 branch.

Does not apply cleanly.

patching file profile.module
Hunk #1 FAILED at 619.
1 out of 1 hunk FAILED -- saving rejects to file profile.module.rej

I can verify the patch does work in drupal 4.7.6.

I did not patch the profile module using the patch method. I manually made the changes to the profile module file and then uploaded it to the web server.

Sam Raheb (sam308)

Okay, and here's the patch ported to 5.1 for your attention. It's the same one, the patch just applies to a different line because of some code refactoring between version 4.7 and 5.

If you want to fix it yourself, just edit line 626 and change w = 0 to w = 1.

Committed to 5.

It would be great to get some testing reports of this patch with Drupal 6. Does it still solve the problem. Although profile module was largely untouched, the user module, profile module and form API interaction could have changed. Please test against Drupal 6!

Confirmed that the problem still exists in 6, and patch solves the issue. To reproduce, create profile field "Gender" or something and check the box to display on registration form. When you visit the registration form, the "Gender" selectbox will appear above username/password.

Thanks for the testing and the updated patch. I also though it would be great to rename $w to $weight, to reflect what it means, so went ahead and done this. Committed!

Dear all,
I am new to Drupal.
I want to design a customized user -registration form. In the front pages there are three images, based on the IMAGES a value is passed in /user/register?cat=category1. I want to display this category in the user/register form. I have written a custom module to included a fieldelement 'textfield' with default value %get[cat] but it is not displaying the value in the textfield.

$fields['user_info']['cat_type']=array(
'#type'=>'textfield',
'#description'=>t('Displays the category /Rold played by the user'),
'#default_value'=>'%get[cat_name]',
'#disabled'=>'true',
);

and also is there a way to change the order of elements in the user/register form ( including the username and email )