bbPress will probably be used to augment BuddyPress’ groups with forums. It’s a complimentary product, not a replacement.
I would register the New Posts RSS feed with FeedBurner and subscribe from there.
My guess is that you didn’t specify a charset collation for the database on install.
I’ve just made a change that should fix your problem (if that was it).
Try using a full path in the require_once() rather than a relative path.
If you create a new user in bbPress the user record should turn up in the wp_users table. That’s the best way to check.
@chrishajer
I went into your non-working accounts profile-edit page and submitted the form. That might make it work now. Can you give it another try?
bbPress is not a competitor to WordPress, it is a complimentary product.
I don’t think they are even using WordPress. Looks like it is all custom code.
chrishajer speaks truth.
We should probably check for this and stop it on install/integration.
Just delete lines 168 – 172 in bb-settings.php to get around this for now.
If you are upgrading the file will be replaced and fixed anyway.
We will probably start using some form of display name in bbPress in the next version.
There is already a built-in way to map user roles between WordPress and bbPress within the admin area under WordPress Integration.
define('BB_LANG', 'sv_SE.mo');
.
I just realised that you may not have a language file for bbPress installed at all. bbPress does not come with any language files by default. You need to download them separately and follow the instructions in the bb-config.php file about where to put them.
The language file you are after should be here…
http://svn.automattic.com/bbpress-i18n/sv_SE/trunk/
Tagged modlook to get Trent’s attention.
Are you loading WordPress inside bbPress? If so the textdomain does not get loaded due to the fact that it is called “default” like the WordPress one.
If you merge the language files of WordPress and bbPress and load it in WordPress it should work.
It’s the old glob() problem.
If you have access tot he database directly you can delete the row from bb_topicmeta with a meta_name of ‘active_plugins’ to completely remove the reference to them.
Role capabilities (like delete posts etc.) are modifiable via a plugin. You should look at examples in teh “Extend” section of this site.
I wouldn’t recommend doing that, so I won’t add it to the documentation. WP tends to stomp on stuff that bbPress needs. I’ve had a project on the back-burner for a while now that will eventually allow what you are after. But it’s not ready yet.
Integrating won’t merge your user tables for you. De-duplicating that data is up to you.
As long as you have all the fields that should be there, the extra fields shouldn’t affect bbPress.
Make sure you setup a WordPress to bbPress role map in bbPress before you do the integration. That way your WordPress admins should be able to instantly login to bbPress as keymasters.
Keep in mind that if you have existing data in your bbPress tables, the user ID associations will be out of whack on posts and topics.
This is a problem with parse_url() dying when there is an http:// in the querystring. The latest commit in branches/0.9 fixes this problem, which would only occur when trying to add a new topic when not logged in.
We use user_login to identify users in display.
user_nicename is used for the url in the user’s profile page when using pretty permalinks. It is basically the user_login filtered to conform to URL standards.
display_name is not populated in bbPress at the moment.
Probably at the same time as WordPress 2.6
