Content Profile on Registration won't let other module(s) save to DB [#951284]

When Content Profile on Registration is enabled the Location module cannot save a user's location on registration. To recreate the issue do the following:
-Enable location module and Location User module
-Set it to collect a user's location on registration
At this point you can enter a user's location during the registration process
-Enable the Content Profile on Registration module
-Setup some fields to be collected on registration
-Create a new account
You'll find that the CCK fields will be saved, but the location will no longer be saved to the DB.

I've been battling with this for a week now and can't find a solution. I thought maybe it was something in the systems table in terms of module weight, but haven't come up with a combination that works there. I couldn't find any other issues relating to this so if they exist already I apologize.

Comments

Comment #1

johnnybgoode CreditAttribution: johnnybgoode commented 25 October 2010 at 15:37

check where the location modules expects its values to be during the submit process.

most modules look for data in $form_state['values'], but the content_profile registration module keeps all node_form data in $form_state['content_profile_registration'].

If this is in fact the cause of your problem, it is a simple task to write a sub-module for content_profile that copies the necessary data into $form_state['values'] upon form submission.

for more info on creating a sub-module see: http://drupal.org/node/785034

Comment #2

johnnybgoode CreditAttribution: johnnybgoode commented 25 October 2010 at 15:43

additionally, if the location module needs any submit or validate hooks or otherwise sets data in node_form_alter() then see this issue: http://drupal.org/node/937274

note: I am using content_profile, content_profile_registration, and location without any issues, so your problem may be caused by something else.

Comment #3

scalp CreditAttribution: scalp commented 25 October 2010 at 18:05

johnnybgoode,
Thanks for responding. Just wanted to check what your setup was. Do you have user settings set to collect a user's location on registration?

Comment #4

johnnybgoode CreditAttribution: johnnybgoode commented 25 October 2010 at 20:28

Not automatically. I have Location CCK enabled and define several location fields in my profile content type, which users supply manually during registration.

Your problem may be related to the first issue I highlighted, where content_profile stores data from the node_form in variables not expected by other modules. I haven't tried to do what you're doing specifically though, so the problem could be elsewhere.