You aren’t inside a function so there’s no need to globalise $bbdb.
This will get you every user (including all meta) into the array $users:
$user_ids = $bbdb->get_col( "SELECT ID FROM $bbdb->users WHERE user_status = 0 ORDER BY id;", 0 );
$users = bb_get_user( $user_ids );
print_r( $users );
“from now on” means “as of bbPress 1.0”
The favourites RSS feed was always public, for some reason the page was made private in the past. We decided (me and mdawaffe) to just make it public from now on instead of getting rid of the RSS feed.
If you don’t want it to be public then you’ll need to write some plugin code to make that happen, just remember to kill the RSS feed as well.
You could also try restarting your memcached service to clear any potentially bad buffers.
@r-a-y
Can you please do a var_dump($cached_ids) so we can find out exactly what the value of $cached_ids is?
Just before line 71 in that file would be the spot, before $_cached_ids = join( ',', array_map( 'intval', $cached_ids ) );
It should output something useful to the screen.
@r-a-y
OK then, you really need to upgrade.
Here’s how I would do it…
- De-integrate cookies, clear out all cookie settings in bbPress/WordPress including hardcoded ones in configs with the exception of you secret keys (BB_AUTH_KEY and friends)
- Upgrade to the latest Trunk of bbPress
- Upgrade to the latest release of the bbPress Integration plugin
- Clear all relevant cookies in your browser
- Setup integration in WordPress first, go to the admin panel for the plugin – use the settings it gives you to use in your wp-config.php file
- Setup integration in bbPress second, if the plugin in WordPress tells you to add a special constant to bb-config.php, do that now too. You’ll need to login to bbPress separately at this stage. Only enter settings into the admin, don’t try to add anything back into your bb-config.php except that one line from the WordPress plugin
- Now you should be good to go again, clear your browser cookies and try various ways to login and logout
Visit the WordPress Codex and search for information on apply_filters().
You can filter that array with a simple plugin.
There have been significant changes in the file where your errors turned up (exactly around those lines).
There is a good chance that the problem no longer exists, but please give us a bit more info to go on.
That article on the BuddyPress Codex is a little confused.
Are you using WP-Super-Cache (output caching) or an object based cache like the memcached object cache?
The error “Query was empty” is directly from MySQL. Do you have access to MySQL logs?
I won’t be able to get to bbPress Live until after 1.0 is released. Hopefully that’s in a couple of days.
You should really move to a newer version, preferably trunk.
johnhiler nailed it and there’s nothing particularly hardline about my statement. It’s a matter of prioritising the features that bbPress supports and in turn the features that I support as the main developer of the software and the various community members support on this forum and in any future docs.
We could make bbPress do lots of things, some would stray not far from the expected feature set, like this. I’m just drawing the line, that’s all I’m saying.
Not at the moment and it won’t have anything available in the first release.
WordPress is not designed to play nice with bbPress loaded inside it in this fashion. It will probably break things (not just visual things). I won’t be writing support for this into bbPress at all, even if someone patches it to work. I gotta draw the line on integration somewhere. Try the bbPress Live plugin for WordPress and see if it doesn’t give you what you need.
@nuprn1
Are you integrating with WordPress there?
They have to be changed separately. You might be able to write a plugin for WordPress that syncs them up or even deletes the bbPress role for recreation (based on the role map) when the user next visits bbPress.
It should be faster, unless your forum is completely empty, then it might be slower.
It says that in the notes on that field.
The cookie change took me by surprise too and is a bit of a pain in the neck generally.
Try this…
post_form( array( 'h2' => 'Woot!' ) );
