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.
We turned off the visual editor in 2.3.1 because of issues users were having losing formatting when switching between visual and HTML modes.
We put up a snippet with the 2.3.1 release to re-enable it.
http://codex.bbpress.org/enable-visual-editor/
Try hitting Tools > Forums > Repair Forums
…and run the “Remap existing users to default forum roles” fixer.
Basically, blog admins aren’t always forum admins, they need to also be Key Masters. Sounds like you lost (or never had) the Key Master role.
It may be worth approaching this differently in a future version, and trusting administrators implicitly.
There is no changelog. What’s changed?
There is a changelog, you just need to read the blog post this topic is connected to. 
Or, even better, keep an eye on Trac if you’re concerned about the exact changes.
You are correct. I’m also improving this in 2.3.1, which should fix any issues you’ve had with it currently.
Enable the Fancy Editor in your forum settings.
Unfortunately, this won’t scale very well. Notifications and Favorites are stored in a serialized array is usermeta, and keeping track of every topic will eventually slow things down significantly.
Instead, I’d filter `bbp_is_user_subscribed` and invert the results. That way you’re subscribed to all topics, and bbPress only stores the topics your users are not subscribed to.
Make this into a plugin:
`function invert_subscribe( $is_subscribed ) {
return ! $is_subscribed;
}
add_filter( ‘bbp_is_user_subscribed’, ‘invert_subscribe’ );`
Sounds like a conflict somewhere. bbPress should be redirecting back to the exact same topic/reply that each user creates, similar to how it does here.
Check Settings > Forums, and make sure there’s no trailing slashes on any of your settings. We can trim off the trailing slash when you save your settings, though it may have negative consequences if anyone actually relies on that.
@kannued – Also, please include links to your site.
Depends what the boolean function is comparing. Can you open a new topic in the forums here, and be more specific?
Sigh. No; first I’ve heard of it, and totally lame that’s happening.
Do you mind opening a ticket over at http://bbpress.trac.wordpress.org?
Looks like it did change, but only for the positive in this regard:
http://bbpress.trac.wordpress.org/changeset/4336
My guess is no; or that the default option value changed in 2.3 (I don’t recall) and there is no option in the DB.
