I am unable to finish checkouts and see this error in other places
"warning: Invalid argument supplied for foreach() in /home/.../public_html/sites/all/modules/uc_signup/uc_signup.module on line 106.
warning: Invalid argument supplied for foreach() in /home/.../public_html/sites/all/modules/uc_signup/uc_signup.module on line 111.
warning: Invalid argument supplied for foreach() in /home/.../public_html/sites/all/modules/uc_signup/uc_signup.module on line 106.
warning: Invalid argument supplied for foreach() in /home/.../public_html/sites/all/modules/uc_signup/uc_signup.module on line 111.
warning: Invalid argument supplied for foreach() in /home/.../public_html/sites/all/modules/uc_signup/uc_signup.module on line 106.
warning: Invalid argument supplied for foreach() in /home/.../public_html/sites/all/modules/uc_signup/uc_signup.module on line 111.
warning: Invalid argument supplied for foreach() in /home/.../public_html/sites/all/modules/uc_signup/uc_signup.module on line 106.
warning: Invalid argument supplied for foreach() in /home/.../public_html/sites/all/modules/uc_signup/uc_signup.module on line 111.
"
There is a similar ticket #997026: Notice: Undefined variable: nodes in uc_signup/uc_signup.module on line 50 but this appears to be done in RC2
Comments
Comment #1
ezra-g commentedDo you have any core user profile fields defined?
Comment #2
skesslerNo.
We do have Content Profile module installed but I tested turning if off and it did not solve the problem.
Thanks,
Steve
Comment #3
skesslerNo.
We do have Content Profile module installed but I tested turning if off and it did not solve the problem.
Thanks,
Steve
Comment #4
skesslerI added a field because we decided we would need one and it works now.
Comment #5
Sung commentedI have the same issue.
Comment #6
rcasero commentedComment #7
Baroch Oren commentedI've also encountered this issue, after a fresh install of COD cod 6.x-1.0-rc1, that includes uc_signup 6.x-1.0-rc3
This issue has been solved after at least one additional (core-)profile field was added to the user profile.
A better approach is to add an apropriate check before any prior assumptions.
For non-programmers, or just those of us who are in a rush: the workaround is to add a profile field using example.com/admin/user/profile
Happy New Jewish Year, Baroch Oren
Comment #8
mcdoolz commentedJust a heads up that I'm running the latest dev and this is still the case.
Creating an arbitrary user profile field fixes this issue.
Dastardly.