Not enough information to help really. I don’t see any actual useful error message, though it looks like your page output halts in bbPress’s breadcrumb. You’ll need to look through your output, do some searching through the code, and debug what’s going on.
Start here: http://codex.wordpress.org/Debugging_in_WordPress
There are too many unknowns. Try installing the Debug Bar plugin, and read up about debugging your installation here: http://codex.wordpress.org/Debugging_in_WordPress
I’m addressing this in the next release. It’s a bit of a catch 22, though it’s seemingly only happening on older installations where auto-role was turned off.
The theme has CSS rules that are too broad. You’ll need to write some CSS yourself to counter it, and even the bbPress styles back out.
Links to your forums are not relative to where you use the forum shortcode. When you think about it, how could they be? You’re free to use the shortcodes anywhere you wish, even on multiple pages.
If you want to change the permalinks for your forums, visit Dashboard > Settings > Forums > Permalinks and change them there. 
I don’t understand what you’re asking for. The topics widget has several display options.
bbPress 2.3 will convert Group Forums to regular Forums, and it’s up to you and your installation to determine if they’re connected to Groups or not.
Probably an easy enhancement. Put up a patch on Trac!
BuddyPress 1.2.10 is an extremely old version. You’ll want to update incrementally to the current version of BuddyPress first, then bbPress, and then run the migration scripts.
You’ll want to backup your data, in case something goes wrong. You’ll also probably end up doing some manual work and guessing about what needs to happen, since every installation has its quirks.
Check for javascript errors, or plugin incompatibilities. In the case of a plugin conflict, let us know what you find so we can try to address it in a future version of bbPress.
When you delete a user, WordPress will prompt you and ask you what to do with all of their existing posts.
Probably need more information to be helpful here. What’s actually happening? Are you familiar with debugging WordPress, using WP_DEBUG and such?
Good question. bbPress uses roles in a different way than BuddyPress does. BuddyPress does not have custom user roles the way WordPress and bbPress do. Instead, right now roles are just a way to identify what user’s have what position in the group member hierarchy: admin, moderator, member, banned, etc…
Which is to say, one does not directly effect the other in any real way.
Is something wrong with the code tags here that you’re unable to use them? I’m having a hard time following exactly what to do to duplicate the issue you’re having.
I’ve tried each permutation of posting code and swapping between editors, and it appears to work correctly for me in what is now bbPress 2.3.2. I’ve also synced up dev trunk with deploy trunk, so the beta tester plugin should have the most recent changes in it too.
(Keep in mind that the beta-tester plugin doesn’t grab the latest version directly from trunk; it gets what I merge into WordPress.org Extend’s trunk. This helps me keep what the beta-tester plugin gets stable, even though bbPress.org’s trunk might not me.)
Just installed the beta tester plug in and updated to v2.4-alpha and it did NOT fix this…
Can you include more(any) information on what you’re seeing? From my testing, it’s fixed in trunk and in the 2.3.2-alpha, and fixed here on bbPress.org also.
It’s probably not great to have domain.com/forum/forum/foo/
Think of what your community is about, and do something creative instead.
domain.com/discussion/about/foo/
Not at all related to bbPress. How did you find a 4 year old topic, and think it was worth bumping?
Closing this topic, since it’s old and not relevant.
Sounds pretty strange. First things I’d do:
- Check which accounts might have moderator/super admin access
- Check trash/spam
- Check access logs, see if someone removed them</lill of>
All of bbPress’s trash/delete actions perform capability checks against the currently logged in user, so it’s impossible for an unauthorized user account to delete content inside of WordPress.
It’s also possible someone deleted all of the forum content without your knowledge, using the “Reset Forum” tool under Admin > Tools > Forums > Reset Forum
By the way, I can’t login to this site in Chrome, it just refreshes the login screen every time.
Looking into it; someone else reported the same. Probably because it’s missing a redirect, and we’ve added some caching for logged out users.
Sounds like you have a javascript error in your theme causing issues. Also, as a keymaster you’re allowed unfiltered HTML, but your regular users have limited access to HTML tags and attributes to prevent them from breaking the layout of your site.
What comes in bbPress 2.3.1 is exactly what we’re running here on bbpress.org.
That’s annoying, but a great example of how everyone can be confident it’s a bbPress release causing problems, when another plugin added at the same time is causing a conflict.
We’re all volunteers. If we don’t help you at midnight on a Friday, it’s because we’re probably out enjoying the weekend, taking a break, or traveling 500 miles away to talk to hundreds of people about the software.
I guess our ideas of what makes great support are different, and that’s okay, but topics like these don’t do anyone any good.
Thanks for feedback.
Sounds like it’s possible to get pretty stuck. I’ll see if I can duplicate what I think is happening, and if I can duplicate it, I’ll come up with a fix.
I don’t think I understand what you mean? Can you include more details?
It will be fine, but you’ll likely want to avoid having private or hidden forums. bbPress performs a postmeta query to exclude topics and replies from private and hidden forums, which will be a pretty bad bottleneck.
Hopefully in bbPress 2.4 or 2.5, I’d like to move the last-active-time meta queries to use post_modified in the posts table. That will remove some of our dependency on JOINing tables, and speed things up for you pretty significantly (at the cost of bastardizing the core post schema and its intentions a bit.)
If you have other specific questions as you go, happy to help and be a resource.
