I have a multi-language site that I recently moved from a development folder to a public folder and all seemed well, at first.

The user registration forms that were previously working just fine no longer display any of the custom profile fields; they will only display the account fields (email and username).

What's even odder is that this behaviour only occurs when the URL includes a language prefix. For example...

http://www.encuentramascota.com/es/user/register
http://www.encuentramascota.com/en/user/register

... fail to show the profile fields. However,...

http://www.encuentramascota.com/user/register

... shows the registration form with the profile fields just fine. Since the default language is in English and I need the Spanish version for most of the users, this is a major problem for me.

I've spent hours trying to figure it out. I have a custom form template called user_register.tpl.php that constructs the form using form construction items as in ...

print drupal_render($form['Contact']['profile_address_1']) ;

When I output the $form variable at the user_register.tpl.php file, it shows no sign of the profiles sections (Contact, Information 1, etc.)

I've checked the modules against a similar site I have working properly on a different server and everything checks out. All the profile fields are set to display in the registration form and all the permissions are correct.

Any ideas?

Cheers
Roland Combes

Comments

bear_beavis’s picture

Seems you find a way to get it working now.
Can you tell us how you manage to fix that issue ?

Thanks

rcombes’s picture

I've been so busy I have not been able to get back and comment on my "solution."

After an exhaustive search, it turned out the culprit was version 6.x-1.3 of the profile-role module. Since I didn't have enough time to go into the code to figure out what part was causing the problem, I simply reverted to the 6.x-1.2 version of the module and everything went back to working properly.

Hope that helps

- Roland Combes

bear_beavis’s picture

Thanks for the quick answer !

I reverted to 6.x-1.2 and it solved my problems too.

I suggest you to apply the security fix on 1.2 (http://drupal.org/node/559630)