Ask a silly question 
Page links for bbPress (1.0.4) should be removed, since it’s build in to bbPress 1 (per Sam). But yeah, the rest of your plugins look fine.
I’ve never lost admin access on any integration (6 and counting). Hence my confusion 
@filiped – So far so good. I think if they’re working on RC1 and RC2, odds are likely they’ll work on Final.
@the_Wish – What plugins are you running?
@phaniraj01 – That’s a plugin https://bbpress.org/plugins/topic/bb-attachments/ – But it may not work on RC2
They should vanish from view and become hidden. But AFAIK, you can’t totally delete them yet.
Inching forward.
When I share tables, the default role of the admin of forums has a subscriber role in capabilities, thats why the admin access is lost.
Right, but WHY does that happen to you when it doesn’t to everyone else (that I’ve heard of) who sets up bbPress/WordPress the way you described It’s weird and I wonder what happened. It’s not the different wp_/bb_ prefixes, I’ve tested that.
Michael, I meant massbases’s site, not yours.
@ashfame I didn’t say they couldn’t, I said they didn’t. I chose that word on purpose
The way that WP-Super-Cache was originally written, logged in users DO NOT get cached pages. Now I understand that Donncha added in a toggle to turn that option on and off recently, but I’ve not used it and I’m not sure exactly what that does.
As for ‘why’ logged in users don’t get cached pages (historically), well, Donncha says this:
If you’re logged in or have left a comment you’ll never see a super-cached page. You’ll see plain old regular WP-Cached pages instead. That’s not so bad since a huge majority of your visitors will never leave a comment.
We’re going in circles. And yes, I know it’s working know.
My question is this: WHY were your xx_capabilities and xx_usermeta messed up in the first place? There’s no reason I can think of that the setup you described (install WP, configure. Install bb, configure. Integrate bb and WP) should have whacked those settings. You see why I’m confused?
ash, I was talking about the exact same plugin you were. Read the very first post on the plugin page.
This plugin is only meant as a simple way to fix roles for users doing reverse integration of bbPress with WordPress without having to resort to using phpMyAdmin but it may have other uses if a primary admin role gets corrupted or wiped out for some reason.
So really, unless your admin role is being wiped out somehow, this shouldn’t be needed in the situation you describe.
All the latest poster links go directly to /profile and not a user’s profile.
I’m using … trunk with a fix (trunk from Sunday morning).
Sam’s first point, about logged in users … With wp-super-cache, if you’re logged in, you don’t get cached pages. So on a forum, most folk are logged in, thus defeating the purpose.
Single topics pages can be cached untill a new response comes in.
That would be new and different, and IIRC not a part of bog-standard WP-Super-Cache, so that’s a pretty hefty write.
It’s working for me as well now.
If I edit a link that was made in the ‘bad time’, it’s still bad, but once I fix it, it stays fixed. All new links are fine.
AHA! That is an old problem: #1033
My guess is something old got reintroduced. I’ve reopened the ticket.
Single quotes are bad HTML anyway and shouldn’t be used…
Checking with trunk: If I add in a link: <a href="http://bbpress.org">This is a link</a> it works. If I edit that post, I get this: <a href="http://bbpress.org"">This is a link</a> It gets even weirder as it goes on.
Why is this really familiar? I think we had this once before…
(tags working, pagination of users working. We’ll get there! )
Think of this as a reference post we’ll go back to, in order to get information to make a tubularly cool super sexy bbPress Codex magnifique!
Sorry, it’s been a day.
ashframe, even the admin plugin says it’s supposed to be for when you do reverse integration. Which is why I’m asking why you think you need it in the first place I totally get that you need to make the change manually due to your specific setup. I don’t get why the change is required in general for a bog standard WP + BB setup.
bbPress shouldn’t be writing over the value in the DB. IIRC, it’s supposed to pull the WP values to create new BB values in the BB tables, once integration is setup in bbPress.
Try it WITHOUT doing the muckity muck with the bb_capabilities, maybe?
Aha, I can repro this too. It’s not that you can’t add tags, it’s that you can’t add tags that have been used before to a new post. EW! ew ew.
There should have been (that param was required for 2.7/1.0 integration).
Check your bbAuth keys in bb_config and make sure they match the WP ones. Flush your cache and cookies. Your browser could be caching the old cookies, as they did change in WP 2.8.
Purge your cache and dump all site cookies. Then try again? I ran into that once, and it only seemed to affect my admin stuff. My regular posting stuff didn’t get affected at all.
To achieve integration between 0.9.05 & WordPress 2.7.1, I overwrite the bb_capabilities in wp_usermeta for my user by sql query as I don’t have phpmyadmin and I am using custom table prefixes.
I’m at a loss why you would have to do that anyway… I’ve never heard of anyone having to go in via SQL and making those changes except in the case of ‘reverse’ integration (where by you started with bbPress and are now adding on a WP site). In theory, if you’re starting with everything brand new, you just do WP first and then bb and it should work.
Looking at your doc, you also mention changing the wp_ prefix to rocking_ which is totally fine, but later on you have this:
Add these two lines in bb-config.php
$bb->custom_user_table = 'wp_users';
$bb->custom_user_meta_table = 'wp_usermeta';
Those too should be rocking_users and rocking_metadata
What theme are you using? I can add tags just fine.
Yes. And it’s mentioned all over
Try removing define('WP_AUTH_COOKIE_VERSION', 1); from your bb-config.php file.
