[aajkaal]

I completed Step 2 (WordPress integration) successfully. On step 3, I hit Complete Installation and I receive a blank screen. So I change permission on bbpress directory to 777. Now I am back on Step 1. Step 2 with the same values as I gave earlier now fails. So I skip step 2. Fill up step 3 and hit Complete Installation and I receive a blank screen again.

[timskii]

If you upgraded WordPress, the wp-config file may not contain all the keys. Generate them here, and add them to WP. The first 3 of the WP keys are them added to BBPress (via the admin screen):

• WordPress “auth” cookie salt = AUTH_KEY
• WordPress “secure auth” cookie salt = SECURE_AUTH_KEY
• WordPress “logged in” cookie salt = LOGGED_IN_KEY

[michael3185]

Yes johnhiler! But without much extra work.

(My ‘Holy Cow inefficiency’ rant was fueled by a late night and beer – I finally got out of the house).

bbPress, and WordPress, need some standards for plugins. Think about it. I know there’s no perfect analogy, but let’s imagine it’s a car. Ford decide to release a twenty-first century car, and it’s damned cool. It has a chassis, steering, wheels and an engine, but everything else is bolt-on. You get to choose how it looks and works. Some people bolt on an aerodynamic shell and a blower, and achieve speeds in excess of 150mph. Others bolt on a big shell and wheels, and lots of seats to carry their kids around. Everyone has a hundred other options. Cool! However, anything you want to bolt on has either a) to be ratified by Ford, or b) noted as a user bolt-on from elsewhere. Ford has a main site/blog/forum where you can see authorised bolt-ons working and links to where to get them, but there are a thousand sites/blogs/forums where you can get ‘unauthorised’ bolt-ons. The world is, as Douglas Adams said, any mollusc you like. But at least you know the Ford authorised bolt-ons are going to work, because they’ve tried them, and all the screws fit the right holes.

Sam and other core developers need to do something similar. Set some standards. Many existing plugins may adhere to those standards already. Many won’t. They should do it across all systems they’ve created. They tell the world that these new standards exist, and that they’ve set a benchmark. The world reports that bbPress/WordPress has set standards other forums haven’t. They don’t need to do much more work, but lickety-split, they’re an authority in the blog/forum world.

When that happens – and it had better happen if the developers want to be taken seriously – users will do a few simple things. They’ll download and install, grab some certified plugins, and go. Sites will appear all over the world with comments like, “I clicked a couple of links, sent the package to my server, added a few certified plugins, and YAY!”

That’s what you folks developing the core of bbPress/Wordpress want.

Isn’t it?

[arandomdan]

I’m running WP 2.7.1 and bbPress Version 1.0-rc-1 on localhost. WP has been installed to /3dd/ and I installed bbPress to /3dd/bbpress/ today and have done all the proper steps for syncing in the bbPress admin.

I have added the following code to bb-config.php:

require(BB_PATH . '../wp-blog-header.php');<br />

define('WP_AUTH_COOKIE_VERSION', 1);<br />

$bb->bb_xmlrpc_allow_user_switching = true;

I can login to both WP and bbPress with my WP user account (yay!), but <b>the problem is that WP doesn’t know when I logged in to bbPress and vice versa</b> (i.e. when I am logged into WP, bbPress still shows the login form). In addition, <b>when I login to bbPress, WP logs me out; and when I login to WP, I am no longer logged in on bbPress</b>. I have cleared my cookies many times and tried it in both IE and Firefox, same result.

Together, WP and bbPress create the following cookies (aside from the wp-settings and test cookies):

Domain                  Cookie name<br />

/3dd/                   wordpress_logged_in_*<br />

/3dd/wp-admin           wordpress_*<br />

/3dd/wp-content/plugins wordpress_*<br />

/3dd/bbpress/bb-admin   wordpress_*<br />

/3dd/bbpress/bb-plugins wordpress_*<br />

/3dd/bbpress/my-plugins wordpress_*<br />

/3dd                    wordpress_logged_in_*<br />

I believe the last 4 are created by bbPress and it should be noted that there is no trailing slash on the wordpress_logged_in_* cookie path.

Does anyone know what the problem might be?

[daniellaf]

[UPDATE] I fixed my problem by uninstalling my bbpress and rolling back my wp database to an earlier version and then just installing again. Install works fine now. I think where I went wrong was changing the bb_ prefix to wp_ and not including define(‘WP_AUTH_COOKIE_VERSION’, 1); in bbconfig!

[Tynan Beatty]

Yesterday I updated a public site with a relatively inactive and fresh bbP forum from WP2.7.x and bbP1.0alpha-6 with the bbPress Integration 1.0-alpha-4.1 plugin…

to WP2.8-beta2-11509 and bbP1.0-rc-1 with the bbPress Integration 1.0-rc-2 plugin.

I haven’t done extensive testing, but the integration worked flawlessly before the upgrade (following Sam’s video tutorial sticky to the letter), and seems to work almost as well now.

The one scenario I’ve found where it doesn’t work is users logging in from bbP cannot logout from WP. All other bbP/WP login/logout combinations seem to behave as expected; however the only way I could get this to happen was to not add the wp-config.php changes suggested by the bbPress Integration plugin. When I did add those changes it broke at least WP login entirely.

I did a little bit of testing with different combinations of the definitions the bbPress Integration plugin suggests, and the details can be found in this post.

peace~

[Tynan Beatty]

I just upgraded a public site from the latest WP2.7.x to the latest WP2.8-beta2 and decided to upgrade the site’s bbP1.0alpha6 and the bbP Integration plugin that was made for that version (all working as expected).

I was having similar problems with wp2.8-beta2-11509 and bbp1.0-rc-1, using the bbPress Integration 1.0-rc-2 plugin. I found that adding it’s suggested changes to my wp-config.php was causing the problems. I also removed the integration speedups suggested from the bbP admin ‘WordPress Integration’ settings. Now I haven’t tested registration from the bbPress end, but everything else seems to work back and forth. Here’s what I have near the bottom of wp-config.php with everything working:

define('WPLANG', '');

define('COOKIEPATH', '/');



/* That's all, stop editing! Happy blogging. */

Where the '/' might be a '/subfolder/'

And here is the bottom of bb-config.php:

define('BB_LANG', '');

?>

The only thing I’ve found not working thus far is users logging in from the bbP side cannot log out from the WP side. Everything else seems integrated for logins/logouts (login/out from WP, login from WP/out from bbP, login/out from bbP).

This is a minor issue compared to not being able to login to WP at all when using the suggested bbP integration changes to wp-config. I also have all 4 random keys matching between configs, including the nonces (which I don’t think were mentioned in the integration video post, but I don’t remember now). I hope there’s a fix for the login from bbP/logout from WP in the next release of the Integration Plugin, and I also hope that the issue doesn’t affect registration from bbP (since it seems to be related to the plugin). Great work on this so far Sam

On a side note, further testing suggested that it was the ‘SITECOOKIEPATH’ definition causing the inability to login from WP, and the ‘COOKIEHASH’ definition seems to allow WP login, but break the integration.

peace~

[eraticdance]

The problem with not being able to log into sub-domains was fixed when I changed SITECOOKIEPATH from ‘/wp-admin’ (as recommended by bbPressIntegration 1.0-rc-2) to ‘/’. An additional cookie, wordpress_XXXXX was created and now I can log into the sub-domains as admin. fyi.

[eraticdance]

Does anyone know what cookies should be generated when you’re logged in as admin and using user integration?

In the video tutorial on bbpress integration, there were 3 bb- type keys, but I don’t see any. all I see are the wordpress_test_cookie and the wordpress_logged_in_xxxxxx cookies. Has the cookie handling been changed for WPMU? If someone could point me to any documentation on this I’d appreciate it.

[John James Jacoby]

This will be fixed with 1.0 of bbPress. Problem is that the get_locale call gets triggered by WordPress when using deep integration.

I submitted a trac ticket about this a few days (weeks?) ago and talked to Sam via IRC about it. He’s aware of it and it’s on his radar.

I suspect that checking for deep integration and hooking into the locale filter will be the only way to do it without forcing it through a new bb_get_locale function.

[chrishajer]

If you didn’t get the email, how did you get the password? I forget now if on installation it shows you the password. If it does, then please ignore this question.

What version did you install, and is it integrated with WordPress?

[bzmillerboy]

I tried deleting uft8_general_ci from my wp_config.php file and left it blank during the install however now I’m getting the following error.

Referrer is OK, beginning installation…

>>> Setting up custom user table constants

Step 1 – Creating database tables

>>> Modifying database: bria5519_buddypresstest (localhost)

>>>>>> Table: bb_forums

>>>>>>>>> Creating table

>>>>>>>>>>>> Done

>>>>>> Table: bb_meta

>>>>>>>>> Creating table

>>>>>>>>>>>> Done

>>>>>> Table: bb_posts

>>>>>>>>> Creating table

>>>>>>>>>>>> Done

>>>>>> Table: bb_terms

>>>>>>>>> Creating table

>>>>>>>>>>>> Done

>>>>>> Table: bb_term_relationships

>>>>>>>>> Creating table

>>>>>>>>>>>> Done

>>>>>> Table: bb_term_taxonomy

>>>>>>>>> Creating table

>>>>>>>>>>>> Done

>>>>>> Table: bb_topics

>>>>>>>>> Creating table

>>>>>>>>>>>> Done

Step 2 – WordPress integration (optional)

>>> WordPress address (URL): http://brianandlindsaymiller.com/buddypresstest/

>>> Blog address (URL): http://brianandlindsaymiller.com/buddypresstest/

>>> WordPress cookie keys set.

>>> WordPress “auth” cookie salt set from input.

>>> WordPress “secure auth” cookie salt set from input.

>>> WordPress “logged in” cookie salt set from input.

>>> User database table prefix: wp_

>>> WordPress MU primary blog ID: 1

Step 3 – Site settings

>>> Site name: BuddyPressTestForums

>>> Site address (URL): http://brianandlindsaymiller.com/buddypresstest/forums/

>>> From email address: bzmiller@fuse.net

>>> Key master created

>>>>>> Username: keymasteradmin

>>>>>> Email address: bzmiller@fuse.net

>>>>>> Password:

>>> Description: Just another bbPress community

>>> Forum could not be created!

>>> Making plugin directory at /home/bria5519/public_html/buddypresstest/forums/my-plugins/.

>>> Making theme directory at /home/bria5519/public_html/buddypresstest/forums/my-templates/.

>>> Key master email sent

There were some errors encountered during installation!

[daniellaf]

[UPDATE] I have kind of fixed my problem – I logged onto phpMyAdmin and went to wp_usermeta for my admin account and changed the wp_capabilitoes meta_key back to a:1:{s:13:”administrator”;b:1;} from a:1:{s:9:”keymaster”;b:1;}. Now, my BBPress admin of course does not have keymaster privileges, but that’s ok right now. Still haven’t sorted out cookies.

[Sam Bauers]

The additional queries are probably due to the new taxonomy structure we are using for tags.

On the upside, you can now use memcached to cache bbPress objects which should give you better performance than 0.9

I’d be interested to know if the query count was also higher on other pages.

There is a small amount of code “bloat” because of BackPress abstraction layers, but it’s here to stay. It’s already being utilised in a couple of other projects including GlotPress and there are a few people interested in merging it into WordPress as well. The benefits of using it to the ongoing development of bbPress is becoming clearer all the time.

As for feature creep, it’s going to be really limited. bbPress is just supposed to do a few things simply and provide enough hooks for plugin and theme devs to add the bells and whistles. That won’t be changing any time soon. Most development over the next few iterations will be concentrating heavily on easing integration with WordPress and making the lives of plugin and theme devs easier.

[timskii]

To put some more detail on the “bloat” thing: I’m comparing databases with identical sets of posts/users, and very similar templates/plugins (I’d hope the 1.0RC code would be better). One setup is 0.9.4/2.5.1, the other 1.0RC/2.7.1.

With 0.9.4, my forum front page is processed consistently in under 100ms (when repeatedly refreshed). With 1.0, 150-200ms is more typical. For reference a simple 2.5.1 (without wp-cache active) WordPress front page on the same hardware is just under 100ms, 2.7.1 is just over 100ms.

That’s barely noticeable to the user, who often experiences a few 100ms of latency, and is still more likely to be slowed down waiting for adverts/graphics than the forum software to dispatch the HTML. But it evidently is slower. I don’t have a reliable way to break down that extra processing time… but I’m instinctively drawn to 11 queries vs 45 queries. Probably because those are the only other number I can see!

[daniellaf]

I’m also having this problem with WordPress 2.7.1 and BBPress 1.0-rc-1 using integrated database and with BBPress in a subdir.

I’ve had WordPress installed for a while. Installed BBPress 0.9 using Simple Scripts, but it didn’t work, so I deleted the BBPress files. Then I had an “Error establishing a database connection.” Fixed that by restoring my database and making a new admin user for the database.

Reinstalled using 1.0-rc-1. Now, my WordPress/BBPress admin user can only log into BBPress. When the admin tries to log into WordPress, I get “You do not have sufficient permissions to access this page.” This only affects the admin user. All other users can login. New users can register.

Logging out of one site logs the user out of the other site, but logging into one site does not log the user into the other site.

Ideas?!?!??

[raphaelb]

Using bbPress 0.9 and WordPress 2.7 — when a user tries to perform a password recovery, it’ll accept anything. It doesn’t give an error message if the username doesn’t exist.

Case study (this actually happened):

A user “forgot” his password, but it turned out he had actually never registered. So he goes to the password recovery page, enters a username that doesn’t exist, and is then greeted with the default reset password text, saying “An email has been sent to the address we have on file for you.” That text made him expect an email which never came.

A. Is this something that can be fixed? B. Is this something that should be filed as a bug?

[eraticdance]

Running WordPress 2.7.1, bbPress 1.0-RC.

I got user integration working, so I can log in WP and be logged in in BP and vice versa. And I can log in as admin for the top-level site, but when I try to go to the dashboard for the any of the sub-blogs, it gives me the WP login screen and doesn’t recognize the password.

I’m using sub-directories instead of sub-domains, which may or may not be significant.

[dss]

I’ve got the latest version of WP and BBP

So that’s BBPress 1.0 rc-1

and WP 2.7.1

In my wp-config I have the Secure Auth Key but in the WordPress options.php there’s no “secure auth salt” so i have no idea how to find this and use it for integration.

[thekmen]

Try deleting all your cookies or using another browser to log in & see if it lets you.

[thekmen]

I can’t really add to the argument except to say that I never tried any older versions, so downloaded RC1 last week & love it. I only have one issue mentioned in another thread, I can’t get the function bb_new_topic_link();

to work but have worked around that for the moment using hardcoded links. The function is only used in 3 places so it’s not much of an issue.

I am using it on a live site for less than a week now – http://xfactor-updates.com/forum/ – its quiet at the moment but will get busy & fully tested in the next few months

As WordPress 2.8 is due out the door any day with it’s new widget classes, a lot of themes will have to be upgraded to take advantage of the changes so I can see a lot of people leaving WordPress 2.5, 2.72 and so on behind and making the switch to 2.8.

The sooner bbPress can be fully integrated with WP 2.8 the better in my opinion.

[_ck_]

bbPress will likely travel the same path as WordPress

so bloat and uneven internal feature adoption is unavoidable

but my hope is it will happen in far later versions than sooner.

I will fondly remember and miss the “good old” 0.9 days

Note I’m not saying NEVER use 1.0, I’m saying for an active site don’t rush into it and perhaps for any new site, don’t start with it, since it can be upgraded.

Template developers should not use 1.0 until it has extremely wide adoption as it’s features are not backwards compatible, but any template you make in 0.9 will work in 1.0 with virtually no modifications.

timskii don’t worry about 1.0 not being debugged enough, even before RC1 it has a 10% adoption:

1.0a6 : 5%

1.0 ? : 5% (1.0 using pre-a6)

0.9.x : 52%

0.8.x : 35% (this is likely wrong, it includes 0.8 installs that upgraded to 0.9)

[johnhiler]

Great points, timskii!

One note – it’s now possible to integrate bbPress v.9 with the latest versions of WordPress, using either of the plugins here:

https://bbpress.org/plugins/topic/freshly-baked-cookies/

http://superann.com/2009/02/26/wordpress-26-27-bbpress-09-cookie-integration-plugin/

I share your concerns about bbPress becoming bloated. I hope the platform doesn’t go down that path… that would be the main thing that would eventually drive me off of bbPress.

[Metzae]

First of all, thanks for your help so far…

I can’t use the WP plug-in because I can’t even log in to activate it.

I’ve also tried the fix-admin-access plugin but it doesn’t work for me. I get administrator access back but not keymaster access (which means I can’t even see the plugins link in the admin panel). I would edit the database directly if I knew what to change the values to, but so far every time I mess with that it just resets me to “member.”

I tried the freshly baked cookies plug-in, but I don’t know how to make it work. The notes say that I’m supposed to set my LOGGED_IN_SALT and AUTH_SALT, but they’re both in the WP admin options, and since I can’t log in, I can’t find them.

At this point I’m willing to just uninstall bbPress and wait until a more stable version comes out, but that won’t solve my main problem, which is my inability to log into WordPress. :o(

[timskii]

I’ve been “testing” 1.0 out privately over the last week, primarily by re-writing my custom code and templates, and then working through every user operation (to check both my changes, and the underlying software). So I’ll try and play devil’s advocate to _ck_’s “don’t upgrade!”

From the user’s perspective, little has changed. The most significant feature to pull out is the use of Display Names. That’s a huge plus on an “international” forum, because users can now set their names to contain non-English characters. And there’s no need to workaround empty display names in WordPress (when a user registers via BBPress).

Templating is similarly unchanged. About the most significant change is that the contents of tag-form.php can no longer be altered via a template – which was likely never required anyway. Semantically, existing oddities remain (like the profile edit is still a table), and usability can be clunky in places (when you register successfully, there’s a message that tells you to log in, but nothing immediately helpful, like a login screen).

Plugins very much depends on how deep they go. The only place I stumbled was in user roles, where the underlying code had completely altered. But I’m not using many plugins, and the custom code I had been using, I’d been prepared to rewrite. (Most of it was a mess anyway!) A clear “your mileage may vary” caveat, and particular risk if one doesn’t understand enough programming to work round anything that breaks.

Technically, 1.0 feels fairly solid. I have found glitches, but nothing worse than some of the 0.9 versions. 1.0 does perform many more database queries. Like 50 on certain pages. Although it is hard for me to assess the load implications without running it on a public site. Integration worked OK as an upgrade, once I’d realised that the upgrade did not automatically add the new cookie-related keys (which needed to be added manually to the existing config files). The whole package feels more “bloated”, but that may be more the fault of WordPress than BBPress. I just hope BBPress doesn’t evolve into the messy, feature-overloaded forum software I had been trying to avoid.

So, if I was just running BBPress, on balance I’d stick with 0.9, at least until the dust settles on 1.0.

But. There’s a but.

If nobody uses 1.0, hardly anyone is debugging it, hardly anything gets fixed, and so on. There’s a danger of putting 1.0 on the shelf, waiting for someone else to finish it, and then wondering why the bugs never get found. So even if you aren’t running it on a live site, it might be useful to try it out privately.

Rightly or wrongly, WordPress 2.5.1 makes me increasingly nervous: As times goes on, I’m going to find plugins and templates that aren’t designed for that version. And while it is claimed that 2.5.1 has no security flaws, if almost nobody is using it, the chance of any flaw getting found and reported is also low. In contrast, the latest version is sure to get picked apart and patched back up very quickly.

And then I started to look at BuddyPress, and… I don’t even know if it’s possible to run that on top of 2.5.1. But you can see the way I’m starting to think: An old BBPress is itself rooting me in the past. And while I knew it was unfinished software when I started using it, I had rather assumed it would at least keep pace with WordPress, not get left a year behind.

So right now, it’s a rather person decision. All other things being equal, I tend to agree with _ck_.

However, I see a lot of WordPress 2.7+ blogs with phpBB forums hosted alongside. And naturally no integration between them. In the near future, that’s the first big, obvious “market” for BBPress. Yet almost all those people need compatability with the latest WordPress. For us “early adopters” that’s important: Some of those new BBPress users will write plugins and templates, and they won’t bother trying to support outdated code. Once that starts to happen, old 0.9 users will find they are missing out – which will probably be the time for most existing users to upgrade.