@DanielJuhl – Those don’t sound like questions as much as noticing bugs. For the fixes you’ve incorporated into the importer, can you share them on the development Trac so I can look at your approach and use them as the basis for fixes for Beta 2?
Regarding the languages folder, you need to put them in /wp-content/languages/bbpress/
In Beta 2 and beyond, the bbp-languages folder makes a return, and it can use GlotPress integration to provide the proper language files.
@tofugu – Simple plugins can easily swoop in and take control of the allowed tags. Right now it relies on the same tags that are allowed in comments.
This is the second time this situation has come up, so I made a last minute change to the topic/reply form template files to alert the user of this additional ability.
@tofugu – Your WordPress blog actually works the exact same way. As a site admin, you are provided the ‘unfiltered_html’ capability, which allows you to post any kind of content that you want to. It’s your site, do what you want with it. Normal users have restricted access, so that they can’t enter possibly malicious data into your site.
@jckbco – If you use bbPress 2.0 (the plugin) and then have WordPress in Multisite mode, then yes you can. Each site in the WordPress install would need bbPress active on it. And that’s it. 
@jckbco – If you use bbPress 2.0 (the plugin) and then have WordPress in Multisite mode, then yes you can. Each site in the WordPress install would need bbPress active on it. And that’s it.
@papu – Thanks! See the “Requesting Access” section at the bottom here: https://translate.wordpress.org/getting-started
@papu – Thanks! See the “Requesting Access” section at the bottom here: https://translate.wordpress.org/getting-started
Link added to GlotPress for translations.
Link added to GlotPress for translations.
There is a first pass and an importer, yes. Be sure to backup your existing database before using it though; remember it’s prerelease software and not guaranteed to be 100% perfect.
@VanDuch – At the moment, admins and super admins can view private and hidden forums, and those capabilities can be modified real time by other plugins to adjust who can see what. There’s a high probability that dropdown will be disabled/hidden when 2.0 launches, since there’s no real use for it in core. I knew going in that bbPress would need to support forum visibilities for BuddyPress public and private groups, but without an interface for choosing who can access them (BP groups), it’s somewhat pointless.
@VanDuch – At the moment, admins and super admins can view private and hidden forums, and those capabilities can be modified real time by other plugins to adjust who can see what. There’s a high probability that dropdown will be disabled/hidden when 2.0 launches, since there’s no real use for it in core. I knew going in that bbPress would need to support forum visibilities for BuddyPress public and private groups, but without an interface for choosing who can access them (BP groups), it’s somewhat pointless.
You’ll want to create a new page, and use the
[bbp-topic-form]
shortcode.
You’ll want to create a new page, and use the
[bbp-topic-form]
shortcode.
Works for me. Can anyone else confirm this?
Works for me. Can anyone else confirm this?
That would be nice, and I’ll most likely research something similar to this after 2.0. The problem is there is no way to add an additional theme path check on top of the parent theme and the child theme locations. Even then, that doesn’t make the single-, archive-, and page- templates match the HTML structure of your current theme, which means manually editing them anyways.
As annoying as it is to add theme support for bbPress and not have the files there, that’s also the easiest way to communicate ability between theme and plugin. If you add theme support for post thumbnails, and then don’t use post thumbnails in your theme, you just don’t have post thumbnails.
That would be nice, and I’ll most likely research something similar to this after 2.0. The problem is there is no way to add an additional theme path check on top of the parent theme and the child theme locations. Even then, that doesn’t make the single-, archive-, and page- templates match the HTML structure of your current theme, which means manually editing them anyways.
As annoying as it is to add theme support for bbPress and not have the files there, that’s also the easiest way to communicate ability between theme and plugin. If you add theme support for post thumbnails, and then don’t use post thumbnails in your theme, you just don’t have post thumbnails.
What version of bbPress are you using?
What version of bbPress are you using?
Check out the Theme Compatibility sticky topic, and confirm that you’ve followed all the steps correctly.
Check out the Theme Compatibility sticky topic, and confirm that you’ve followed all the steps correctly.
Sorry; I don’t understand the question. bbPress won’t move any files for you on its own. You mentioned that you’ve physically moved files (hopefully you copied, and did not remove them from the bbPress folder.) By putting
add_theme_support( 'bbpress' );
in your theme, you’re telling bbPress “I don’t need your help anymore and I have everything under control.” If you didn’t copy all of the files correctly, then bbPress won’t know what to do.
Sorry; I don’t understand the question. bbPress won’t move any files for you on its own. You mentioned that you’ve physically moved files (hopefully you copied, and did not remove them from the bbPress folder.) By putting
add_theme_support( 'bbpress' );
in your theme, you’re telling bbPress “I don’t need your help anymore and I have everything under control.” If you didn’t copy all of the files correctly, then bbPress won’t know what to do.
Since you’re manually adding theme support to your existing theme (as opposed to letting bbPress do it for you) you’ll need to move the other single/archive/page template files from bbp-twentyten into your existing theme too.
