hook_requirements to notify users to create profile fields

I do not have any fields configured in /admin/user/profile.

I think this might also happen if people have fields but none of them are shown on the registration page. I kind of think we should remove the dependency on profile module if it's at all possible.

greggles is indeed correct here. We should make the core profile module optional, probably as part of an implementation that would also support content profile (#527700: Optional Content Profile support, and make core profile optional as well).

As for the user accounts being blocked, that is a separate issue. After checking a development site where this is in use it seems that the user accounts are defaulting to blocked even when it is functioning correctly. Not a good default.

Actually, after further investigation, users are not created as blocked by default -- That would have happened in earlier versions of uc_signup, when we used user_save instead of drupal_execute to create the new accounts. If the accounts are being created, with the latest version of uc_signup, I would expect that they would be active regardless of these foreach errors. Can you specify which version of uc_signup you're using?

Closing due to lack of response.

I am also running with the same issue with uc_signup 6.x-1.0-beta4 version.

In my case I am not taking any optional content profile parameter.But after completing the order it shows the following Error:
" warning: Invalid argument supplied for foreach() in ../sites/all/modules/ubercart/uc_signup/uc_signup.module on line 601. "

Modules & Versions used:
signup - 6.x.1.0-rc6
ubercart- 6.x.2.2
drupal - 6.15

I need it as the earliest.

Thanks in advance

@puneet - do you have the profile module enabled with at least one field?

Hi Greg Thanks for responding

Yes we have profile module enabled but we do not added any field because we just want to take email of the attendees.

So Is there any way to fix it without having field on profile module?

Still Looking for response

uc_signup doesn't currently support not having profile fields. For more about how it could support them, please see #623900: API for additions to attendee info form.

Perhaps in the interim uc_signup could have a hook_requirements implementation that requires profile fields with the proper settings (i.e. a field that is visible on the registration form, right?). This would at least make sure people have their sites configured properly.

Yes, this seems like a good idea. At the very least, we should probably avoid these invalid arg foreach errors.

Why is invalid to have no profile fields? Especially if using content_profile.

UC_Signup doesn't support content_profile. Currently the checkout workflow is optimized to use profile fields, but could be modified to skip a checkout phase if you were using it to only check out the current user.

Here's a patch for a hook_requirements implementation.

This is now committed.