| Project: | Signup Integration for Ubercart |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Tested identical sites in PHP 5.2 and PHP 5.3. PHP 5.3 will not allow the profile information to be loaded in the checkout process. After email address is submitted for anonymous users the following errors occur (dev snapshot):
warning: Parameter 2 to profile_user() expected to be a reference, value given in /var/www/example.com/includes/module.inc on line 462.
warning: array_values() expects parameter 1 to be array, null given in /var/www/example.com/sites/all/modules/uc_signup/uc_signup.module on line 92.
warning: Parameter 2 to profile_user() expected to be a reference, value given in /var/www/example.com/includes/module.inc on line 462.
warning: array_values() expects parameter 1 to be array, null given in /var/www/example.com/sites/all/modules/uc_signup/uc_signup.module on line 92.
Thanks for a great module, I just don't want to downgrade my PHP to an older version.
Comments
#1
Does this help at all?
This is a quick untested patch that might resolve the problem.
#2
Patch prevents uc_signup from hooking into the checkout workflow altogether. I think the problem is similar to this error which is present on PHP 5.3 with the google analytics module installed.
warning: Parameter 1 to profile_load_profile() expected to be a reference, value given in /var/www/example.com/includes/module.inc on line 462.
Here is an explanation to what appears to be causing incompatibility in contrib modules such as google analytics and uc_signup. http://drupal.org/node/679404. Long story long, it has to do with passing by reference with module_invoke in PHP 5.3. I'll take a look at a creating a patch with something similar to what fixed the google analytics module unless you see a quick fix. Thanks again.
#3
I just tested and committed the following fix. We'll get additional testing in the next dev and beta.
#4
Oops, here's the right patch.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.