I had to make this fix after the update
In bp-core-avatars.php I commented out
`return apply_filters( ‘bp_core_fetch_avatar’, ‘<img src="' . `
onward and added
`return apply_filters( ‘bp_core_fetch_avatar_url’, $gravatar );`
Also commented
`return apply_filters( ‘bp_core_fetch_avatar’, ‘<img src="' .`
and added
`return apply_filters( ‘bp_core_fetch_avatar_url’, $avatar_url );`
Not sure whether this is correct or not, but my site works.
I guess Mark’s post is what the menu item should read out-of-the-box. I agree with Mark, since Blog and Blogs confuse people. It’s about usability – especially for non-techie users.
Try this work-around, if you can explain it to your users. Set the unread_count to 0 in the table wp_bp_messages_recipients for all messages. I see this issue going away by doing that!
By the way, I have this error persisting. It’s not for everyone. Its coming randomly to some users. I could have fixed it, if only I can detect a pattern!!! Will spend sometime this evening.
In my opinion, in the brave new collaborative world, the traditional definition of beta is a little blurred. Where the users are actually developers and developers are users, betas will get to “near-production” environment. By the way, the social network I mentioned itself is in beta!
My concern is that there could be many more such db issues (which I did not expect when I rolled out Buddypress), and these need to be fixed. I should not wait until the users come back and tell me they’ve got problems.
That’s for the blogs. I face with problems such as Buddypress says there are notifications or messages for a user, and when I click on links such as Notifications or My Account > Messages > Inbox there is nothing out there. Then I need to go to PHPMyAdmin, find out which entry is causing the problem and delete it. This does not happen with every users. Just some users, and fixing it on a case-to-case basis is tough. There should be some way to figure out and entry in this table means an entry in another table, which will then ensure consistency across tables.
In fact there was another bug which went away when I upgraded to beta 2. I guess the bug was with pagination. I was not able to see the last page in any of the paged lists. Now it’s fine.
