Always more useful to test the trac version than the releases. The trac version is the most up-to-date code available.
No timeline, but the sooner the better. 
Sounds like a GMT issue. Will look into it.
@Anthony – bbPress 2.0 is a plugin for WordPress. Please don’t answer questions that you don’t know the answers to.
@soggybiscuit – You can turn off the root slug in the Forum Settings, but it might still get confused.
@Anthony – Not a bug with the plugin.
Yes. Activate bbPress Network Wide, and it should do the rest.
You can try making topics hierarchical, but that might make things goofy in other places.
You might need to buckle down and write your own custom rules to overload the ones that WordPress generates with the custom post type.
Can we please try to keep the discussion in this topic on bbPress, and not use it to support each others plugins?
Can we please try to keep the discussion in this topic on bbPress, and not use it to support each others plugins?
This will probably come down the pipe eventually, and is something someone can do and contribute back to core also. Any takers?
Fixed in branch. Will be fixed in next release.
https://bbpress.trac.wordpress.org/ticket/1594
Fixed in branch and next release.
Refreshing your permalinks is what fixed it.
Missing the bbp_get_topic_tag_template() function. Fixed in branch.
@Mike1233 – I edited the swearing out of your post. That’s not a great way to get help.
Fixing. Will put out another RC today.
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!
