Conflict with user.module on line 1131, 1144 - Missing argument 2 for user_category_load()

I can confirm this issue...
This bug has been troubling me for a few months now, Thanks Drake for pointing out that I can remove the error by disabling tab tamer
Its a pity though as this is a very useful module... solving this bug would be greatly appreciated

Thanks

Which version of content_profile is in use?

I am using an older dev of content_profile and I don't have any problems. So I guess there might be some other conflict here.

I am using 6.x-1.0-beta4 of Content Profile
Hope we can fix this

Thanks for great module

I am using not the latest dev but one created after beta4. Could you try the latest dev and see if the problem persists? The dev I am using is totally stable. Do you have a test site?

Cool will try that out, thanks for suggestion.
Unfortunately it is a secure site, so no public access. I will try set up a test case of it if the dev does not fix it.

Thanks
Gregg

Nope I am still getting this error even with the latest Content-Profile Dev version.

Any updates with this, i would really love to be able to use this module again.

you mention a 'secure site' - just in case - we have hit several issues with Secure Pages tripping up other modules. May be worth checking

I am getting the exact same errors, however no functionality seem to break. I have the same setup with tab tamer and content_profile, running drupal 6.14.
Would love a solution to this since I use tab tamer extensively.

I am using the premium module for secure content but I dont think it has any effect on tab tamer.

My first drupal.org post from a drupal noob. Hope it's constructive for someone.

I'm not using the tamer tab (mainly because I didn't know it existed until reading the above bug); however, I am attempting to alter tabs manually. A description to do that is here: http://drupal.org/node/483324

There is a problem with the procedure in the above link because it doesn't discuss using the correct wild card category. The solution was posted here: http://drupal.org/node/604850

If I don't use the correct wild card type for ALL menu items being altered (even if not related to the user/edit menu item), you get the errors posted in this bug. If you correct the wild card types for EVERY item, the errors disappear.

It's therefore my sneaking suspicion that there is actually a bug in the tab tamer module wherein the correct wildcard type is not being used for one or more menu items that are being altered. It seems that this mistake causes many many problems throughout drupal.

subscribe

I haven't been able to duplicate this at all. :(

Could you please tell me the exact settings that you are using for all of the user/* paths?

I had the exact same symptoms with the same error message. Disabling tab tamer resulted in the error message disappearing, enabling it again caused the error to re-appear. The solution in my case ended up being quite simple.

1. Go to /admin/settings/tabtamer, and click Save (this rebuild this modules menu settings).
2. Flush the Drupal caches.

The cause of the issue was that my site's menus had changed since tab tamer had been configured. This resulted in orphan menu items in the tab tamer variable (tabtamer_tab_settings), which were causing the error. The tab tamer menu settings don't get rebuilt when clearing the cache, only when the admin page is saved, hence the steps above being necessary.

Hello guys,

I had this same problem and i did not solved, but i found a way to avoid it:

go to ( this problem its about "account profile" module ): admin/settings/account_profile and unset the "Redirect on User Edit page"

hope that it was usefull

I got the same error using the http://drupal.org/project/account_profile with http://drupal.org/project/me. The module 'me' alias has big module_weight: 999 After i set account_profile module weight 1000, everything worked well.
Well, imho the problem shoud be the same, there are a module need less module_weight, then Tab Themer.

To set the module weight install the http://drupal.org/project/util, or set it directly in database system table.

Thanks cladom! #15 got rid of the error message.

Issue account_profile and me module, here:
#929344: Integration with 'me' module
Patch available.

#992744: views_arg_load error with views 3 dev and local tabs. should fix this problem