Shortcodes are explicitly prevented from working inside of bbPress.
The reason is because Shortcodes do not care who uses them in what context. If you enable them, all shortcodes will work for all users. This allows all of the bbPress shortcodes to work, inside of bbPress, which enables normal users to embed forums inside of topics and replies. No good.
You’re on your own if you want to go down this road, but I wouldn’t suggest it. Shortcodes are transparent, and a poor experience for most users (since they are completely invisible in the UI.)
Instead, I’d recommend building something for bbPress 2.1 (still in development) and write a plugin to tap into the power of TinyMCE.
Clearly links that don’t function isn’t normal; if everyone had this issue, 200k other bbPress users wouldn’t be using bbPress. Sorry if bbPress didn’t do what you expected, but it’s working great for many others.
Overall, it sounds like your theme is the culprit, and that you don’t like the way it looks. That’s a design decision; one that you will need to solve on your own if you don’t like the default styling.
bbPress has never tried to be exactly like “all the other forum software.” The philosophy is to be the smallest and simplest to use, and I think it accomplishes that pretty well inside of WordPress. If it’s missing things you wanted or expected, you are free to build those things yourself.
Thanks for the feedback.
Thanks. Nacin’s looking into it. Someone will report back soon.
WordPress runs post slugs through a sanitization filter to make sure there are no collisions. As such, no two slugs can be the same, regardless of the type of content that it is.
How can i disable HTML and/or VISUAL editor? (2.1 plugin version)
Have you tried Settings > Forum? 
Unless you’re talking about conditionally toggling the mode, in which case you’re on your own to build that as a plugin, similar to WordPress.
Hey thanks! Good to hear it’s working out!
Probably best to fix the issues with your theme instead. bbPress 2.1 is due out soon, and then you’ll be ready for it.
But, to answer your question… Just delete the plugin folder, and no forum/topic/reply data will be deleted.
You’re doing it exactly backwards to accomplish what you want to do.
You do *not* “need” a page with the slug “forum” or “forums” to make your forums appear. They will just work, based on the slug you set in Settings > Forums.
If you want the index of your “forums” to show “forums” then it’s slug needs to be “forums” and not “forum”
If a WordPress page has the same slug as something else (“forums”), the page wins.
(If your forum archive slug in Settings > Forums is “forums” but you have a page with the slug “forums” then the page will appear and it will be whatever the_content of that page is.)
You can have an unlimited number of permutations on the forums to look and work. It comes with the most obvious (and working) settings out of the box.
You can include slashes in your archive slugs, so hierarchical pages work, too.
This part is not broken, it is not a bug. It’s two settings that you need to make match, and you’re in control of both of them on your own to operate however you want your site to operate.
This is by design, since that’s the title of that page.
There isn’t anything bbPress can do to make Akismet work any better. It’s just heuristics and monitoring. Akismet misses a ton of spam here on bbPress.org, too.
On the Super Cache front, some improvements went in, but I haven’t spent a lot of time with them together; you probably have more than I have.
Something with your theme is hardcoded to make that happen. Nothing bbPress can do about it if the theme takes over.
You can use bbp_get_forum_last_active_id() to get the post ID of the latest topic or reply. From there you’ll have to use WordPress functions to get out what you need.
(This, of course, is assuming you’re using bbPress 2.0 or beyond)
I suspect it is. Hashbang URLs are a pain. Will take a look.
Happy to help, but I’m only one person; can’t do it all. It’s way more helpful to everyone (and the project) if you dive into the code and figure it out in your free time rather than relying on mine.
Also, no reason to create one topic and point to your old one. It’s spammy. Closing this one.
Do you also have the WordPress translation files where they belong? If WordPress core cannot find its translations, it will revert back to English. If that’s the problem, it’s possible you’ve had bbPress’s in the correct locations already, and WordPress was nooping it.
Time to dig in the code and look around. The /bbp-includes/bbp-template* files are a good place to start.
bbPress’s template logic works almost identically to the way WordPress’s works, it just needs to do all the same things that WordPress does for specialized content. Just like WordPress has queries and conditions for posts, pages, categories, and tags, bbPress has them for forums, topics, replies, users, topic views, and front end posting and editing.
In many ways, bbPress feels more complex because it is more complex. But, I can assure you, it’s built to the same standard and uses the same conventions as WordPress does.
Invalid header issues indicate you’ve installed the plugin incorrectly, or have an incomplete download.
It’s possible to use the core templates, but it won’t really work the way you want it to. Why? Because when you view a single forum, you also want to view that forum’s topics. When you view a single topic, you also want to view that topic’s replies. A single flat loop isn’t enough to handle this behavior, no matter what you do.
You can still create those templates, and they will work as you’d expect, but you’ll still need to redo some heavy lifting. Probably easier to follow the bbPress conventions for now until the whole flow makes sense.
If you don’t like what the default theme provides, make your own.
I don’t understand what you want to do.
He meant trunk. Also, no reason to open a second topic for the same issue. Closing this one.
It’s overdue already. It’ll be ready when it’s ready. We’ll push out some betas before hand.
Deactivate and reactivate bbPress. Sounds like the plugin you used to ‘reset the caps’ nuked out any custom caps and isn’t playing nicely with replacing them.
You’re wrong. They are most certainly related. Most likely that your install thinks it lives in a different directory, .htaccess rules, rewrite rules, or something similar.
I think you have other things that are broken. Your images are broken, and none of your permalinks work at all, not even for your blog.
http://wbbg.com/blog/let-it-snow-let-it-snow-let-it-snow/
