Closed (fixed)
Project:
One page profile
Version:
6.x-1.11
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Sep 2010 at 13:27 UTC
Updated:
30 Oct 2011 at 04:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
swentel commentedHrm, one second, seems to be wrong, I'll get back to this.
Comment #2
swentel commentedOk, first patch was wrong, this one is better.
Comment #3
nicholasthompsonInteresting... When would a form not have an
#id?!Comment #4
swentel commentedHrm, ok did some more debugging and it's actually the fault of the onepageprofile module in onepageprofile_user() where it calls drupal_alter('form') - actually funny looking at that code - http://drupalcode.org/viewvc/drupal/contributions/modules/onepageprofile.... This is obviously more his fault because he's not passing an '#id' here. We should rather file an issue to his module I guess .. :)
Comment #5
swentel commentedMoving this to one page profile. By calling drupal_alter('form') and not supplying a $form['#id'], a lot of other modules trigger PHP notices. I actually made a fool of myself filing already 3 issues for the same problem before I really started debugging ... :) Anyway patch attached, not sure if the '#id' name is ok, maybe this could be something else.
Comment #6
swentel commentedchanging title
Comment #7
aidanlis commentedGood pick up everyone, will get this into the next version.
Comment #8
aidanlis commentedComment #10
dontgoquietly commentedHi, this error is still occurring with 6.x-1.11. I get the following error:
warning: Parameter 2 to auto_username_form_alter() expected to be a reference, value given in /includes/common.inc on line 2883.
warning: Parameter 2 to date_timezone_form_alter() expected to be a reference, value given in /includes/common.inc on line 2883.
warning: Parameter 2 to video_form_alter() expected to be a reference, value given in /includes/common.inc on line 2883.
warning: Parameter 2 to content_profile_registration_form_alter() expected to be a reference, value given in /includes/common.inc on line 2883.
warning: Parameter 2 to taxonomy_defaults_form_alter() expected to be a reference, value given in /includes/common.inc on line 2883.
warning: Parameter 2 to multistep_form_alter() expected to be a reference, value given in /includes/common.inc on line 2883.
warning: Parameter 2 to rules_forms_form_alter() expected to be a reference, value given in /includes/common.inc on line 2883.
when viewing a user profile.
I checked that $category_form['#id'] = 'profile_form_profile'; was applied to onepageprofile_user().
swentel, you had a question about the #id name. I'm not sure what's happening here, but if you've managed to get this to work, please let me know if this is the same error or if I need to open a new ticket.
Thanks
Comment #11
dontgoquietly commentedIt may have something to do with date/timezone module, as disabling that module caused this error to go away. Unfortunately, I need that module, so I can not use onepageprofile as it currently works.
Comment #12
fberge commentedThis is an error with func_get_args() and references
See comments in common.inc
Supplied patch does the trick for me
Comment #13
aidanlis commentedWow, nicely found!
Comment #14
fberge commentedShould we set the status for this issue to done or something?
Dont know what the practice says, but it bothers me that this ticket is one of my active ones =)
Comment #15
aidanlis commentedI'll set it to fixed once the patch is in CVS, I should have a chance to go through my patch queue this week.
Comment #17
aharown07 commentedPatch "failed"... Applied it manually. Fix works (using D6.20 PHP 5.3.something)
So... will we see this in a new release soon?
Comment #18
carvalhar commented#12 patch worked for me.
Comment #19
hk2000 commented#12 patch worked for me as well.
I was getting mulitple errors along the lines of:
Parameter 2 to hook_form_alter() expected to be a reference, value given in /var/www/includes/common.inc
It is in regards to the way drupal_alter is called on line 82 of 6.11. Recommend updating to this patch as soon as possible to fix this issue.
Comment #20
aidanlis commentedFixed, sorry for the delay in getting this live!
Comment #21
aidanlis commented