I’ve just committed code to trunk [2096] to make this easier to achieve.
In your template you just need to use the post_form() function like so:
post_form( array( 'last_page_only' => false ) );
Was a bb-config.php file created in the bbPress directory?
bbPress integration plugin is in the WordPress plugin repository.
https://wordpress.org/extend/plugins/bbpress-integration/
Actually the BBXF plugins have been temporarily removed from bbPress.
This one has been on the back-burner for a while, but hoping to base the first real release on the RSS or ATOM standard somehow. Similar to the way WordPress’ export format is based on RSS.
Oh, I forgot, add this to your bb-config.php
define('WP_AUTH_COOKIE_VERSION', 1);
When you upgrade to WordPress 2.8 later, you will need to remove that line.
This would be a pretty easy plugin to write (the note part, not the wiki part).
The suspect revision tracking could be done with a plugin too, just a lot harder to achieve.
The new function is only useful inside the forum loop by the way. Just like other loop bound template functions – like bb_forum_pad().
I just realised that all you want is a bb_get_forum_class_names() function.
This is now in trunk, see [2089] .
The user link can be a spam link though.
Is the template you are using set to display UTF8 charset in the head or header? Is the database actually in utf8 or something else?
The bb-config setting for database charset and collation has to match whatever the table actually is.
Check for mismatches between any manually set cookie paths, particularly mismatched trailing slashes.
This is becoming more of a problem with the newer release of WPMU and with so many people wanting to integrate with it to use BuddyPress.
I’m looking into WPMU integration specifically at the moment in an attempt to make it easier for 1.0
It is actually possible right now, it’s just too damn convoluted to be within most people’s ability. If you can sit tight on just the DB integration for now, then try again with 1.0-rc-2, things should be better by then.
I hope to have that version out within a couple of weeks.
There is no BB_URI, dragunoff has it right.
@_ck_: Have you thought about using the WP_HTTP class instead of relying on curl directly? It detects for multiple available transports to make remote requests.
You can potentially use “special” characters in usernames via a plugin, but with the ability to have separate “display” names it is not enabled in the core.
Putting this in a plugin might work on it’s own actually…
function my_sanitize_user( $username, $username_raw, $strict ) {
if ( $strict ) {
return sanitize_user( $username_raw, false );
} else {
return $username;
}
}
add_filter('sanitize_user', 'my_sanitize_user', 10, 3);
Try the latest 1.0 release (1.0-rc-1). There was a bug in the way orphaned users got their roles applied. If you upgrade, then re-save the role map in the admin, it might fix your problems.
I’ll be working on the admin area this week to get it up to scratch. You can expect another RC next week.
my-plugins and my-templates are now created automatically if they don’t already exist, so they will be created on all new installs.
Seems there is lots of ham being incorrectly sent from bbPress as spam. This may be having a knock on effect elsewhere. I’m trying to track down the problem with these false reports from bbPress at the moment.
Setup should not be any different to the case where they are on the same server besides the obvious need to change the URLs in the admin area of BuddyPress/WPMU.
You will have issues if you can’t somehow share the same user database from these servers though or at least somehow replicate that data reliably to the bbPress server.
If you are using bbPress 1.0-alpha you can use the “bbPress Live” plugin for WordPress.
You can safely create your own config by copying from bb-config-sample.php
You then ned to go back and complete the installation (which bbPress forces you to do).
Probably better to use your IP address or 127.0.0.1 as the hostname, but this is highly dependent on your Apache config.
This was a bug. Fixed in trunk now.
Old posts will need to be edited to get fixed. Hitting edit then save straight away should do it.
