[@kevinjohngallagher Member 15 years, 11 months ago]

I absolutely agree that this is far from a “guarenteed” fix, but I’ve long found that the more things we can rule out when going through a bbPress to WordPress integration the easier life becomes.

For example, I still define the following in my WordPress config file:

define(‘AUTH_KEY’, ‘authkey’);

define(‘SECURE_AUTH_KEY’, ‘secureauthkey’);

define(‘SECURE_AUTH_SALT’, ‘secureauthsalt’);

define(‘LOGGED_IN_KEY’, ‘loggedinkey’);

define(‘LOGGED_IN_SALT’, ‘loggedinsalt’);

define(‘SECRET_KEY’, ‘secretkey’);

define(‘SECRET_SALT’, ‘secretsalt’);

define(‘NONCE_KEY’,’nonce_key’);

define(‘NONCE_SALT’, ‘nonce_salte’);

define(‘COOKIE_DOMAIN’, ”);

define(‘COOKIEPATH’, ‘/’);

define(‘CUSTOM_USER_TABLE’, ‘wp_users’);

define(‘CUSTOM_USER_META_TABLE’, ‘wp_usermeta’);

And the following in my bbPress config file:

define(‘BB_AUTH_KEY’, ‘authkey’);

define(‘BB_SECURE_AUTH_KEY’, ‘secureauthkey’);

define(‘BB_SECURE_AUTH_SALT’, ‘secureauthsalt’);

define(‘BB_LOGGED_IN_KEY’, ‘loggedinkey’);

define(‘BB_LOGGED_IN_SALT’, ‘loggedinsalt’);

define(‘BB_SECRET_KEY’, ‘secretkey’);

define(‘BB_SECRET_SALT’, ‘secretsalt’);

define(‘BB_NONCE_KEY’,’nonce_key’);

define(‘BB_NONCE_SALT’, ‘nonce_salte’);

$bb->wp_siteurl = ‘http://www.mydomain.com/’;

$bb->wp_home = ‘http://www.mydomain.com/’;

$bb->wp_table_prefix = ‘wp_’;

$bb->user_bbdb_name = ‘XXXXX’;

$bb->user_bbdb_user = ‘XXXXX’;

$bb->user_bbdb_password = ‘XXXXX’;

$bb->user_bbdb_host = ‘localhost’;

$bb->custom_user_table = ”;

$bb->custom_user_meta_table = ”;

$bb->authcookie = ‘wordpress_’;

$bb->cookiedomain = ”;

$bb->cookiepath = ‘/’;

$bb->sitecookiepath = ”;

$bb->wp_table_prefix = ‘wp_’;

Now I know that most of that code is redundant, and left over from older integration methods; but by using this as a base that I know works for bbPress0.9/1.0.2 to WP2.5->2.9 I’ve found that I’ve not hit any real integration issues that weren’t procedural or human error in over a year.

Adding “AddHandler php5-script .php” to my .htaccess file wont cause any overhead (as i should be using PHP5 anyway), and will also help rule out that 1 out of 100 times that installation/integration hits an issue.

@Zaerl and Chris

PHP4 to 5 was a huge change, a leap into correctly written OOP.

bbPress1.0.2 (for all its faults) and specifically backPress are really brilliantly written OOP code; and while not 100% sure, i’m quietly confident that using backPress/bbPress1.0.2 on PHP4 would throw some inconsistances.

I doubt this fix is anywhere near “guarenteed” to solve anything, but if it works for 1 out of 100 people, it should go in the “win” column