I’ve thought about unread posts. The easiest way to do it is to update either a user-meta value or a cookie when each user visits the site. Hook into the topic class function and add a special class to topics with unread replies in them since the last time you visited the site. When a user visits a topic with a last active time after the users last activity time, add those topic ID’s to the meta/cookie so they can be excluded as needed.
Using a cookie is easiest, but inconsistent across devices for the same user (iPhone/iPad/Computer all show mixed results.) Doing a ‘persistent’ unread posts adaptation would require a huge amount of overhead, and probably isn’t really feasible without logging the user ID’s that have visited each topic-reply in post-meta. On busy forums with many users, this would be a huge headache.
Seems you’ll want to ping Yoast about it. We worked together a few months ago to make sure they played nicely together.
After you install and integrate BuddyPress, the process to troubleshoot becomes exponentially more difficult, particularly if you’re not familiar with either platform.
Did you choose the option in BuddyPress to use your existing forums for groups?
If you need to customize your theme and do not know how to do it yourself, you’ll want to hire someone to assist you. No one replied originally probably because it is not clear what you are trying to do.
You’ll want to visit your permalinks page and resave them to rebuild them with bbPress active. This will be fixed in the next release.
I see the ticket, I commented on it yesterday. 
I can’t duplicate it, and don’t see any reason that cap would cause that behavior.
For what it’s worth, *not* wanting complete integration between a WordPress install and bbPress is the exception rather than the rule. It’s been a long while since someone has wanted two separate and disconnected installations.
Best of luck!
@chesternerd – This topic is in regards to bbPress 2.0, which is a turn-key plugin for WordPress.
@Stephanie Leary – Try r3404 – Multisite or single? Have you tried deactivating/reactivating the plugin?
@chesternerd – This topic is in regards to bbPress 2.0, which is a turn-key plugin for WordPress.
@Stephanie Leary – Try r3404 – Multisite or single? Have you tried deactivating/reactivating the plugin?
Because bbPress 1.0 doesn’t allow for comment splitting.
If what you want to talk about doesn’t have an existing topic, make one. We’re pretty lax about things getting off topic here, but there are a few focused topics (mostly stickies) that I’m trying to keep on topic.
It goes both ways too – if you start a topic for help on something, and someone comes into it and starts asking unrelated questions, eventually there will come a point where you’ll want things to shift back on topic.
Updated. I pulled the references to those files, so no more errors. In future iterations of the theme, we’ll look into having better profile areas – these are just graduated versions of the TwentyTen author page.
Doesn’t seem so. Marking as resolved.
This should be fixed it the next release.
Let us know how it works.
In the future I’ll look into adhering to the WordPress Discussion settings for restricting comments too.
I’ve added a multisite option to handle the assigning of the default role and caps. I see value in having it work either way, and can see a case for toggling this setting even on a per site basis.
Multisite crisis averted.
It means that the translation isn’t correct and is missing one of the variables needed for the sprintf().
Explain? All of my installs have wp-content located outside of the WordPress install directory, so I don’t believe this to be entirely accurate.
@anmari – At the risk of sounding defensive (which I’m not trying to be) please assume we develop everything with WP_DEBUG on, and anything that pops up is an oversight, not a lack of knowledge or ability. You can create trac tickets at bbpress.trac.wordpress.org to outline the steps to trigger the notices. Thanks!
@ashfame – Ticket please. Thanks!
If you’re using shortcodes, this is normal. You can hide it with CSS if need be. The problem comes from Theme Compat also using the output buffer from the shortcodes, to not have to duplicate a bunch of code.
I’ll dream up a cleaner solution, but until then this is expected behavior.
Agreed. Add a ticket on trac?
Do you have any other bbPress template files in your theme, or are you relying on bbPress Theme Compat to work correctly?
The way that BuddyPress integrates bbPress is currently through BuddyPress Groups. Do you want your forums to be powered by user groups, or do you want to have central forums like we have here at bbPress.org and WordPress.org?
@suziwilson – The way that BuddyPress integrates bbPress, into WordPress, is by taking over the installation and administration of bbPress completely. That said, if you are using BuddyPress to manage your forums, you do not have access to the bbPress admin area any longer.
If you previously had bbPress setup without BuddyPress, there is a large possibility that you will want to go back to the old setup you had before. BuddyPress currently ties forums into BuddyPress Groups, so they work a bit unconventionally compared to your normal support forums.
Very soon you will be able to install a new version of bbPress totally outside of BuddyPress, and they will work transparently without any additional setup, as two separate WordPress plugins rather than having bbPress be tucked away inside BuddyPress like it is now.
I know it’s all really confusing right now, but it won’t be soon.
