@ck:
based on my recollections, as i’m on a road trip and can’t readily pull up the code, WP2.6 (maybe older, too, i don’t know), in the midst of their new cookies, has an action hook that can be tapped at cookie-creation to make an additional cookie for bbPress to read (in my instance, bbPress is in /forums/ so the new cookie is restricted to that path). the function that destroys the cookies at logout doesn’t have an action hook, so it has to be overridden (it’s pluggable). on the bbPress end, it’s virtually identical–use an action hook at login to create the various cookies that WP expects, override the pluggable cookie-destroying function.
there’s also some work in syncing up all the various secrets.
it’s worth noting that the cookie that’s now restricted to wp-admin/ in WP2.6.x is the same cookie that was unrestricted in path previously, so the mechanics of the cookie contents and whatnot aren’t any different, just the path restrictions.
Though I hesitate to say this out loud, it is possible to integrate bbPress 0.9.0.2 with WordPress 2.6.x (I have a site running the two and logins to one part work in the other, cookies are properly set and cleaned up, etc.), BUT it requires plugins to both bbPress and WordPress (or, alternately, modification of core code) and I’d venture to guess that it might substantially weaken the cookie security introduced in WP2.6. If anyone is desperately interested, I can share details, but it’s messy.
Is there a proper place for BackPress discussion, such a a specific forum or wiki or mailing list?
Having just read the thread over here, I went and rechecked that my WordPress “secret” setting as listed in /wp-admin/options.php matched the setting in my bbPress admin-stettings-wp-integration screen and found that somehow they no longer matched. My best guess is that in the database “update” with the 2.5.1 upgrade of WP, it regenerated the database secret, thus killing the integration.
