When you say blog post you mean more than just updating the front page activity stream? (as seen here: http://testbp.org/ )
You mean actually writing a blog post?
There’s 2 ways you might go about doing it.
1. In your blog dashboard go to “Site Admin” >> “Options” and change the “Dashboard User Default Role” to Author. That will now allow every user on your site who signs up without creating a blog of their own to be able to post on your site’s main blog.
They still won’t be able to post on the front without going into the dashboard until you switch your main blog to a theme that supports front-end posting such as P2. To make the P2 theme compatible with BP install the “Buddypress Template Pack” plugin: https://wordpress.org/extend/plugins/bp-template-pack/
If you want your users to make posts to the main blog from the “site theme” and not from the “wp-admin” then you’ll need to use a theme that supports front end posting such as the default buddypress theme or P2.
Otherwise posting to a blog from the “site theme” is not an option bundled with BuddyPress.
I’m using the default theme provided with BP 1.2.1 for the main site.
At one point while I was still deciding which theme to use on the front I ran Andy’s BuddyPress Template Pack on another theme but then decided to just stay with the default theme in BP 1.2.1 . It was after that I noticed the gravatar/avatar problem. But maybe the problem existed before then?? I don’t know since I didn’t check.
As I already mentioned I’ve already deleted BP 1.2.1 manually and then manually reinstalled it but still to no avail.
Do you think it might be something with the default theme?
Alright, one other anomaly. When logged in as the administrator but I create a blog post on someone else’s blog that isn’t mine it shows the avatars/gravatars correctly, but only for that post. All the other blog posts on the blog by the blog owner show the avatars/gravatars incorrectly (i.e. they replace every gravatar/avatar with the blog owner’s uploaded avatar).
Does anyone else have this problem? Or does anyone have a clue as to what’s wrong?
It’s only remotely similar. Our main blog is fine… but that’s because it’s using a theme that was added after the BP 1.2.1 install (or rather, it was added <i>by</i> the BP 1.2.1 install – we’re using the default BP 1.2 theme).
All new themes added after the install work correctly, it’s only the pre-existing themes which have problems… which means that everyone is still using the old themes and I can’t exactly tell them to switch themes right away.
I just upgraded to BP 1.2.1 (from BP 1.1.3) last night and noticed that right away. In fact I created a brand new user, logged in as them, and then deleted my account… only to find out that I wasn’t logged out by the deletion. So I manually logged out… and then logged back in as the deleted user. All of my activities on the site had been erased but the user was definitely still there.
I had to go into the admin dashboard and delete the user from the WordPress MU Users list.
@Andy Peatling: I assume you’re talking about the codex page here. Now what if I’ve made some custom hacks to the core installation of BP 1.1.3 but now I want to install BP 1.2.1 fresh?
Will following the update instructions on the codex page truly give me a “pure” install of BP 1.2 (i.e. erasing all my custom BP 1.1.3 hacks)? Or is the real solution in deleting the BP 1.1.3 plugin from the plugins folder and installing BP 1.2.1 through the “Install New” option?
You know, I feel that this is so obvious that maybe it should be “considered” to be included in the core? Obviously this wouldn’t be for 1.2 but maybe for 1.2.1?
I mean, think of all the BP installs that have bloggers who comment who aren’t logged in. It could be included as an option in Site Admin -> Options as a check-box to “include non-member comments in sitewide activity streams”?
