Hello I have posted this same question on the realname registration issues thread but after reviewing more of the issue I feel it might be the AAR module causing my issue.

Post from other thread: https://www.drupal.org/node/2312931

I had used the realname registration with logintobbogan and auto assign role modules to allow new users to register and get auto assigned into a role so I can control the users dashboard as well as access to an employment application (webform) with the ability to save the form as a draft.. I have the need to use it again and although I did what I could to disable the registration process a year ago all of the settings I have reviewed to re-enable this functionality look correct however my registration page both /user/register as well as my auto assign role url of /user/register/applicant both only display the email address field and the only thing I can seem to get to change is the confirm email address field. None of the profile fields are appearing.

I have viewed the page here with install notes but everything looks ok. Anyone have an idea of what I am missing.

Thanks,
Paul

UPDATE:

I have made some interesting observations. It seems the default user/register page is displaying the first, middle, last name, street, city, state and zip input fields but ONLY in Internet Explorer. Viewing the same url user/register in both chrome or firefox removes these fields and just the email fields are visible. This is not true for the auto assigned role urls though (user/register/applicant) regardless of which browser I use the email fields are the only exposed fields. I am guessing it is a css issue but it may be beyond my knowledge to debug.

Another strange observation is the url /user/register does display all of the fields now I am noticing in both chrome and IE but not in firefox and if a / is added such as user/register/ the name and address fields disappear again and just the email fields are visible.

It is strange because aside from the regular module updates nothing has changed with the site theme.

Comments

mike.davis’s picture

Hi Paul,

So am I right in thinking that you had this working about a year ago, but you disabled it and are now trying to enable it again?
Have you been using the 6.x-2.0 version all this time or have you upgraded from the 6.x-1.0 version in the last year?

Sounds strange that fields would show in IE but not Firefox or Chrome, which does seem to sound like a CSS issue. Are the fields in the HTML on the all the pages but has been hidden with CSS at all?

Thanks
Mike

modiphier’s picture

Hello mike,

Yes, I had enabled the modules to offer an application for employment once the acceptance period was over I disabled all the functions of the various modules in play and now I need to re-enable the application process again and as I explained the profile fields are not showing up on the aar reg page.

This is only happening when I go to the AAR url I am entering in the AAR settings page for auto assign path I set it to user/register/abc just as I was using last time and just the email fields are appearing. I have done a couple of drupal core updates in the past year as well as any other module updates that may have been released.

I have figured out a way around this issue. I downloaded a module that forces new registrations to a certain role and since I only use the registration process for this one application process I can get away with using this module.

But the flexibility of being able to offer multiple roles user reg per url was definitely a better method.

mike.davis’s picture

Thanks for the info Paul. I'll have a go at setting up a test site with the set up that you have and see if I can replicate the issue.

What version of core are you currently using?
What versions of contrib modules are you currently using for realname registration and logintobbogan?

modiphier’s picture

Hi Mike,

I have a test site of my production site set up if you would like to PM me I can create a login so you can see what I am using.

mike.davis’s picture

Status: Active » Closed (cannot reproduce)

After some time working with Paul on this, I was unable to identify what as causing this and was most likely something to do with other modules that were also running on the site as well.