I've been getting these errors since upgrading to the latest dev release whenever a user's profile page is viewed:
Missing argument 2 for user_category_load(), called in [path_to_drupal]/includes/menu.inc on line 410 and defined in [path_to_drupal]/modules/user/user.module on line 1162.
Missing argument 3 for user_category_load(), called in [path_to_drupal]/includes/menu.inc on line 410 and defined in [path_to_drupal]/modules/user/user.module on line 1162.
Disabling the "Password change tab" module stops this error from occurring. I think this issue may have something to do with what's going on here, but it's really just a guess on my part. I've tried looking at the diff of contrib/password_tab/password_policy_password_tab.module, but I don't see anything obviously wrong.
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | password_policy.1131262-110614.patch | 1.1 KB | iva2k |
Comments
Comment #1
Yanxi commentedI started to get this warning message after upgrading to the latest stable version. It looks like quite a few tab-related modules have had the same problem. Any patches available to fix this one?
Comment #2
iva2k commentedI tracked that through the menu router to line (23) in password_policy_password_tab.module:
Changing it to:
and clearing caches seems to resolve the problem. Though I did not test if it does not break anything else.
Comment #3
earth1 commentedComment #4
sterndata commentedI can confirm this on my system, too. I disabled the password change tab module and things are OK again.
Comment #5
earth1 commentedI can put the password_tab: module/password_policy/contrib/password_tab -> module/password_tab.
Comment #6
rj commentediva2k's solution from #2 fixed the issue on my system...
Comment #7
hbergin commentedThe problem also went away for me when I disabled the password change tab module.
The system seemed to have been working OK before Password Policy was upgraded to version 1.0. When I switched the Password Policy module back to version 6.x-1.0-beta1 on another system showing the same behaviour, it too started working again with no errors.
Comment #8
roball commentedExactly the same issue here with 1.0.
Comment #9
dppeak commentedYou need to add 'load arguments' to the menu definition.
So in the password_policy_password_tab.module after line 29, add:
'load arguments' => array('%map', '%index'),Final result would look like:
You will also need to add a hook_user to the module to register "password" as a category.
After line 34, add the following:
Comment #10
roball commentedGreat. Could you please post these changes as a patch?
Comment #11
adnanhader commentedThanks. #9 worked for me.
Comment #12
iva2k commentedPatch from #9 (apply to password_policy module level).
Confirm it works and fixes the problem. Makes more sense than my hack in #2.
Comment #13
wxman commented#12 patch worked for me as well.
Comment #14
roball commentedPatch from #12 and flushing all caches perfectly fixed the problems here also. Please commit!
Comment #15
Crom commentedditto - Please commit. thanks.
Comment #16
erikwebb commentedFixed and committed!
http://drupalcode.org/project/password_policy.git/commit/14910b831ce9ca4...
Comment #17
roball commentedComment #18
sterndata commentedFix does not work with version 6.x.1.1 with password tab module enabled:
warning: Missing argument 2 for user_category_load(), called in /var/www/vhosts/breadboard.greatharvest.com/httpdocs/includes/menu.inc on line 411 and defined in /var/www/vhosts/breadboard.greatharvest.com/httpdocs/modules/user/user.module on line 1155.
warning: Missing argument 3 for user_category_load(), called in /var/www/vhosts/breadboard.greatharvest.com/httpdocs/includes/menu.inc on line 411 and defined in /var/www/vhosts/breadboard.greatharvest.com/httpdocs/modules/user/user.module on line 1155.
Comment #19
roball commentedThis is because the bug does still exist in 1.1. Thus I have updated the affected version number.
Comment #20
erikwebb commented6.x-1.1 was pushed out for a critical bug. If you can try with 6.x-1.x-dev, please confirm the issue is resolved. There were only a few insignificant fixes added after 6.x-1.1, so I'll likely push a 6.x-1.2 release after those fixed bugs are confirmed fixed.