Re: User and Cookie Integration FAIL
Is it even supposed to show the WordPress users inside bbPress?
Yes it is.
I tell you what I have done. I have bbPress and WordPress on the same database and both have table prefixes. The blog is on my-domain.com/blog. The BBS is in my-domain.com/forum
On forum/bb-admin/options-wordpress.php:
1) the role map is key master, administrator, member, member, member.
2) WordPress URL is my-domain.com/blog, WordPress Blog is my-domain.com/blog.
3) Cookie salt “auth” valid, no Cookie salt “secure auth”, Cookie salt “logged in” valid.
4) AUTH_KEY <=> BB_AUTH_KEY and others set on (bb-config/wp-config).php and the NONCE_KEY <=> BB_NONCE_KEY
5) Table prefix set to the WordPress table prefix. Usually wp_
6) No advanced settings
On /blog/wp-admin/options-general.php?page=bbpress-integration-admin
1) bbPress URL = my-domain.com/forum/. Your plugin URL = nothing. WordPress type = WordPress.
2) Manual Cookie Settings tells me define( ‘COOKIEPATH’, ‘/’ ); which is defined in both config files (on top of those)
My wp-config.php:
<?php
define( 'COOKIEPATH', '/' );
define('DB_NAME', '...');
define('DB_USER', '...');
define('DB_PASSWORD', '...');
define('DB_HOST', '...');
define('DB_CHARSET', 'utf8');
define('DB_COLLATE', '');
define('AUTH_KEY', '...');
define('SECURE_AUTH_KEY', '...');
define('LOGGED_IN_KEY', '...');
define('NONCE_KEY', '...');
$table_prefix = 'my_wordpress_table_prefix_';
if ( !defined('ABSPATH') )
define('ABSPATH', dirname(__FILE__) . '/');
require_once(ABSPATH . 'wp-settings.php'); ?>
my bb-config.php:
<?php
define( 'COOKIEPATH', '/' );
define('BBDB_NAME', 'same as wordpress');
define('BBDB_USER', 'same as wordpress');
define('BBDB_PASSWORD', 'same as wordpress');
define('BBDB_HOST', 'same as wordpress');
define('BBDB_CHARSET', 'utf8');
define('BBDB_COLLATE', '');
define('BB_AUTH_KEY', 'same as wordpress');
define('BB_SECURE_AUTH_KEY', 'same as wordpress');
define('BB_LOGGED_IN_KEY', 'same as wordpress');
define('BB_NONCE_KEY', 'same as wordpress');
$table_prefix = 'my_bbpress_table_prefix_';