It seems something else is getting into the array. Attached is a screengrab.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | profiletabs_zero.patch | 1.09 KB | maartenvg |
| profiletabs.png | 9.51 KB | christefano |
It seems something else is getting into the array. Attached is a screengrab.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | profiletabs_zero.patch | 1.09 KB | maartenvg |
| profiletabs.png | 9.51 KB | christefano |
Comments
Comment #1
maartenvg commentedI can't reproduce this error. Did you try it on a clean installation, or do you have more modules running that might intervene with profile/profile tabs?
Comment #2
christefano commentedThis is on an existing installation. No other modules that affect profile.module are installed, however. I'll do some conflict testing and report back.
Comment #3
christefano commentedThe conflict is with Extended user status notifications 5.x-1.1 and 5.x-1.2. Do you have any ideas how to proceed?
Comment #4
maartenvg commentedOk, I'll check it out.
Comment #5
maartenvg commentedOk, found the problem.
The user_status module incorrectly returns false on a hook_user('view'), which results in a empty category called '0'. Because there will be more modules that have this erroneous behavior, I've added a check for empty tabs.
It's been commited to CVS, but I will not make a new release yet. Attached you can find a patch, which will fix this issue for you.
Thanks for reporting the bug, and testing which module was naughty.
Comment #6
christefano commentedThe patch applied nicely and the "0" is gone. Thanks for the quick fix!
Comment #7
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.