If you don’t have a forum yet, now isn’t the time to worry about if it will scale.
Scaling is about spreading the pain around. As you outgrow one technology (or set of technologies) you upgrade to another as needed, not as predicted or as planned.
This isn’t to say you shouldn’t have a plan, but it’s awful early to know if it’s worth the time spent worrying about.
If you’re 100% certain that you’ll have +1million posts a year with billions of hits a month, then you wouldn’t be asking this question because you’d already know the answer: no, it won’t scale out of the box; you’ll need caching, memcached, and countless servers and data centers to manage it all.
The short answer, don’t be afraid to start out small. When it’s time to grow, you can pretty easily export specific post types with WordPress’s export tool and shard it across multiple multi-site blogs if you wanted; shard the database(s) across multiple servers; whatever you need to do to get by.
If your forums grow quickly and you find performance gains, it’d be great to have them contributed back to the project. It’s true that moving from bbPress standalone to plugin traded some performance for convenience, but it’s been the # 1 most requested feature since it’s introduction.
Also, there’s nothing *wrong* with bbPress 1.1. If you’re more comfortable using something purpose built from the ground up as a simple forum, you can still use it. Just know that nothing but fairly significant code changes or bug fixes are actively going in.
* Taxonomies don’t have metadata, to allow for topic & replies counts or latest content
* Comments don’t allow for attachments without some major work
* The API for custom post types is farther along, more robust, and provided a relatively quick head start (see above)
This is already fixed in the development version. Probably best to wait until its released.
I understand that maybe you could misinterpret a lack of moderators to the entire project being dead, but topics like this only end up making the active contributors feel bad. There’s only so much time available to volunteer in the day. If you want to help us out, tag any spam topics as ‘modlook’ and Jared and I will go through them when we see them.
This is strictly theme controlled. Nothing bbPress can really do about overriding this for now.
More likely it’s your theme not working with bbPress, then. Does whatever you’re trying to do, work correctly with TwentyEleven or bbPress (TwentyTen) ?
Looks like it’s an issue with filter priorities. It’s being turned into a link from inside wp_editor() instead of an autoembed. Seems to work if you post a link from the HTML editor. If you can confirm this is true, can you create a bug on trac, and I’ll close this topic?
bbPress comes with a built in set of theme files to get you started. You’ll need to customize your active theme yourself if you want it to look differently. There isn’t a huge market for third party themes quite yet.
Yes. If you want to have tons of private and hidden forums, you’ll want to look into optimizing the core queries to not rely on meta queries. If you’re using public forums, you should be just fine.
If you’re currently using a caching plugin on the WordPress side, or thinking of doing it, some people have reported cache invalidation issues, namely that it’s not happening correctly. I need more eyes and input on that, or need to sit down and really experiment with what’s going on, to say for sure if it’s a bug or not.
I don’t really understand the question. If you want to make a theme that looks like another theme, you make it. If you don’t know how to, you either learn how and hopefully contribute what you learn back to the community via the codex or forums, or you hire someone that already knows how to do what you do not know how to do. 
Maybe I’m missing the point. I get that the documentation isn’t great right now, but it’s exactly the same as making a WordPress theme. The template files and their locations are already in the bbp-twentyten theme as an example.
Making an entirely custom theme is *not* a step-by-step paint-by-numbers thing. It’s not something anyone can teach you how to do, you have to learn it yourself.
bbPress uses WordPress’s user profiles code, so any new fields you add to the dashboard profile (with a plugin or otherwise) should be mirrored in the theme. If you need an easy GUI to create profile fields, try BuddyPress.
There are a bunch of examples on how to do this with WordPress. Follow those instructions and you should be fine.
To answer your question, you’ll need to put a custom filter on WordPress’s kses. A Google search should help you tremendously. If you’re not a developer or not comfortable diving into the code, you’ll want to spend some time learning, or hire someone to help you.
This forum is staffed by volunteers. The more you bump and complain is the less likely one of our awesome staffers is to help. It moves too slowly here to bump 4 times a day.
If you decide to post somewhere else, none of us are likely to look there to help.
That’s not a bug. It’s just letting you know that your active theme doesn’t come with bbPress templates, so bbPress is going to automatically fill in the gaps as best as it can.
Probably the same bug others are running into with setting forums as Private or Hidden, and then changing them to Public. The topics in those forums still act like they are hidden; will be fixed soon.
You should just be able to uncheck the box in Settings > Forums
It’s always been like this. You’ll need to create a custom template tag to output a formatted time to your liking.
No idea what the error is to help.
The plugins page has a big yellow disclaimer on it, with a link to plugins for bbPress 2.0. The blog has recent posts, and the forum is alive and well. What makes you think it was ever dead?
Yep. It’s a known bug, that will be fixed in the next point release. Probably the cause of a bunch of issues people have found recently.
Short codes are not used in bbPress, to limit their exposure from unauthorized users. Most shortcodes do not have capability checks attached to them, and since bbPress comes with its own shortcodes, we don’t want shortcodes inside shortcodes.
Maybe in a future version.
Keep in mind that bbPress 2.1 is still in development. It’s pre-release software and there might still be some kinks to work out.
But, on paper it’s *supposed* to be better than 2.0.
Happy this is helping some people. Closing for now since this topic seems to be a hotbed for spammers.
Jared is correct. There is a migration plugin already. Also, this is a duplicate post of one from several weeks ago that you posted here and then cross posted to WordPress.org. The more time we spend moderating the forums of duplicate content is the less that’s spent writing code.
