I recently updated from the Beta1 release to the RC2 release. I noticed my new users were getting username like "1" and "2". When I went to the configuration page (admin/config/people/realname_registration) I noticed that the field names had been emptied out. I tried to add them back, but nothing works. I've tried every combination and adjustment of the field name/token I can think of. But nothing will take.

Screenshot of profile page: http://snpr.cm/mb9nLt.png
Screenshot of configuration page rejecting fields: http://snpr.cm/TJoQ1p.png

Comments

bryancasler’s picture

bryancasler CreditAttribution: bryancasler commented
Title: After updating, tokens on configuration page are not being saved » After updating, field names on configuration page are not being saved

Title correction

bryancasler’s picture

bryancasler CreditAttribution: bryancasler commented
Title: After updating, field names on configuration page are not being saved » Module can not be configured

After playing around with this more, I'm thinking it's more than just the field names not saving.

bryancasler’s picture

bryancasler CreditAttribution: bryancasler commented

Alright, I've narrowed it down further. I was previously using the Beta 1 release of this module with an older version of Drupal Core. The fields I'm trying to add are from Core's (hidden by default) profile module. This module had been working for quite some time, so my guess updating core an this module has created some conflict/incompatibility. Anyone else have any insight as to what might be going on?

Here is a screen shot from the DB of the profile fields
http://www.diigo.com/item/image/1ks4o/tr5v?size=o

And here is a screenshot of the config page failing. (Using 7.x-2.0-rc2)
http://www.diigo.com/item/image/1ks4o/ernd?size=o

sgerbino’s picture

sgerbino CreditAttribution: sgerbino commented
Assigned: Unassigned » sgerbino

Have you tried disabling and uninstalling the module then re-enabling it? It won't delete any information from your database.

Otherwise, I could take a look at your site - maybe it will help me find the problem.

bryancasler’s picture

bryancasler CreditAttribution: bryancasler commented

Hi Sgerbino,

I have uninstalled and re-installed the module, no luck. I'd be happy to let you look at the site/database via some screen sharing. I suggest this because can't hand over a proper login without you first signing a privacy agreement with our office.

sgerbino’s picture

sgerbino CreditAttribution: sgerbino commented
Title: Module can not be configured » Does not support legacy profile module from D6 to D7 upgrade
Category: bug » feature
Priority: Critical » Normal

Discussing this issue further over Emails, we realized that the legacy profile module from a D6 upgrade was being used. Realname registration currently does not support these fields.

Changing this issue to a feature request.

bryancasler’s picture

bryancasler CreditAttribution: bryancasler commented

I found a sandbox D7 port of another username module that's able to handle the legacy profile module. Just wanted to post it for anyone else running into a similar situation.

http://drupal.org/sandbox/nouriassafi/1564376