#639 closed defect (bug) (fixed)
admin bar error
Reported by: | bloom | Owned by: | |
---|---|---|---|
Milestone: | Priority: | major | |
Severity: | Version: | ||
Component: | Keywords: | ksort, array_marge, bp-core.php, admin toolbar | |
Cc: |
Description
I just updated from trunk 1281 to 1287. Everything works fine so far, except on every page but the homepage I get an error in the admin bar:
Warning: ksort() expects parameter 1 to be array, null given in /home/wearesau/public_html/wp-content/mu-plugins/bp-core.php on line 1189
Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /home/wearesau/public_html/wp-content/mu-plugins/bp-core.php on line 1192
On wearesau.net it works, but on wearesau.net/blog and all similar URLs it errors. It also errors on blog.wearesau.net.
Change History (7)
#4
@
15 years ago
Please don't mix and match trunk files. You should be downloading the entire trunk and using that.
#5
@
15 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
- Summary changed from admin bar error in trunk 1287 to admin bar error
I didn't mix/match trunk files. I upgraded to 1287 and then tried to back out the file in question to the previous working version. It obviously didn't work.
I've just upgraded to 1289 and the previous error has disappeared. Now when I drop down the "My Account" menu all of my options (except for "Logout") are gone and replaced by error:
Warning: Invalid argument supplied for foreach() in /home/wearesau/public_html/wp-content/mu-plugins/bp-core/bp-core-adminbar.php on line 62
#6
@
15 years ago
Okay, when you said "I just uploaded bp-core.php from trunk 1281" it sounded like you were only upgrading specific files.
Sounds to me like something is wrong with your install here and the plugins are not registering correctly in the navigation array. Are you running any other plugins?
Could you first try this, disable any plugins you are running other than the BP plugins, and then revert to the default themes. Can you then confirm if the error still persists?
#7
@
15 years ago
- Resolution set to fixed
- Status changed from reopened to closed
I didn't even think of plugins.
I deleted all mu-plugins that weren't BP trunk and it didn't help. Then I deactivated all plugins on the blogs. That fixed both my admin bar and groups display issues. So I reuploaded all the mu-plugins and got no error. I reactivated TwitterToWire and it brought back both the admin bar error and group display error.
It's TwitterToWire causing both of my tickets. Something upgraded between 1281 and 1289 must be conflicting.
Thanks.
Additional info: I just uploaded bp-core.php from trunk 1281 and it didn't fix my issue.