[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.

[Metzae]

This is exactly my problem, and I tried using that plugin after I accidentally reset my access to member. The plugin worked fine and restored my administrator access, but I’m still not able to convert myself to key master. All of the trouble started when I changed the permissions for my users, specifically when I set my “admin” (user name) to “administrator.” Two things happened at that point: I am no longer key master and (more importantly) I can no longer log into my WordPress part of the site. :o(

Please _ck_, wave your magic wand or something and help a brotha out!

[johnhiler]

Ah those two versions of bbPress and WordPress are not cookie compatible, without some extra plugins. Either of these two should work – one upgrades your bbPress cookie, and the other one downgrades your WordPress cookie.

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

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

Sometimes bbPress will lose keymaster access during reverse integration – try this to fix that:

https://bbpress.org/plugins/topic/fix-admin-access/

[Metzae]

Update…

I just realized that my account isn’t working properly on either site. I can log into bbPress but now I don’t have full. I wanted to install a plugin but there’s no option to do so (even though there was one a few minutes ago). It says I’m listed as an Administrator, but not the Key Master.

I checked phpMyAdmin and these seem to be the most relevant fields…

dharmaguild_capabilities a:1:{s:13:”administrator”;b:1;}

dharmaguild_user_level 10

[Metzae]

bbPress 0.9.0.4

WordPress 2.7.1

I just followed the automated installer to integrate the two. At first I had issues because I’d mistakenly installed WordPress in the wrong database. So, I wiped the bbPress from my database, exported/imported the WP information to the correct database, made sure WP was working properly, then installed bbPress again. Everything worked fine for bbPress (and it still does) but now WP isn’t working.

I checked the forums a bit and looked at my database using phpMyAdmin to see if there was some setting on my user name that had been tweaked, but honestly I don’t know it well enough to tell at a glance if it’s okay. But, like I said, bbPress is working fine and the *front end* of WordPress is working fine…just not the users.

[johnhiler]

What versions of bbPress and WordPress are you using?

And what techniques/plugins did you use to integrate the signins?

[eraticdance]

Never mind. I got the plugin and installed it and now the cookies look like wordpress_logged_in_12341234…

It’s still not working, but that’s progress.

[Metzae]

I just finished successfully installing bbPress and importing the user database from WordPress, but now I can’t log into WordPress anymore. It recognizes my user name and password, but it comes up with a relatively blank page that simply says, “You do not have sufficient permissions to access this page.” I’ve tried flushing my cookies and logging in and out but it’s no good.

Please help!

[eraticdance]

“Remember you will still need the bbPress Integration plugin on the WordPress side to drop the bbPress cookies.”

What is the bbPress Integration plugin on the WordPress side? I’m trying to set up user integration, but the cookie that gets generated on the WP side is wordpress_logged_in_ only, and not wordpress_logged_in_xxxxxxx, as I think it should be.

Thanks.

[_ck_]

I highly encourage the use of 0.9 until (and maybe even through) 2010

1.0 is a different creature internally than 0.9 and while 0.9 has a few years of development and debugging (and compatible with most plugins) 1.0 has none of these things.

IMHO 1.0 should *never* have been called 1.0

0.9 should have been finalized and released as 1.0

and then what is now being called 1.0 should have been called 1.5

People simply do not understand that 1.0 is not some kind of minor upgrade to 0.9 with just incremental fixes – large portions of code have been changed or replaced entirely. Certain database tables have been completely replaced into a much more complex scheme, etc.

Remember, you can *never* downgrade once you start with/upgrade to 1.0

but there is always an upgrade path from 0.9 to 1.0

(someone someday might be crazy enough to write a downgrade routine for 1.0 to downgrade the database tables but it won’t be me)

There is also no clear path for bbPress from Automattic.

They are replacing the WP code base with WPMU, which means the purpose of the extremely labor-intensive drive to integrate BackPress into bbPress 1.0 is now even more unclear.

I’ve yet to see a single feature/ability in 1.0 that you will miss with 0.9

ps. I also think WP 2.5 is the last decent version of WP made but that’s for another forum

[johnhiler]

chmod is a way to change your file permission settings. More on that here.

https://codex.wordpress.org/Changing_File_Permissions

[johnhiler]

I am also sticking with v 0.9x for now! If your site is working nicely now and you’re happy with how it’s going… there’s no need to change your platform.

I hear that version 1 will have better post-level meta data support? That’s exciting and something I’m looking forward to. Other than that, this is what Sam wrote about version 1.0:

“There is no feature list as such. In fact, you will find that not much has changed at this stage on the front end. The main difference is that we are now using the BackPress library for core functionality. There are some other “under the hood” changes as well, like the introduction of WordPress’ taxonomy structure for storing tags and the creation of a global meta table which can store metadata for forums, topics and posts as well as site options. The global meta table can also store custom meta from plugins.

The major cosmetic difference is the new admin area which is modelled on WordPress.”

[englishlangprof]

Hi.

Have uploaded bbpress to a folder in my server.

It’s at: /public_html/bbpress-0.9.0.4 and I have wordpress in that folder too.

So I just want to visit ‘the intended url’ but it’s not there. Have tried it a dozen times. What am I doing wrong?

[janvi]

Hi.

Is wordpress required for installing bbpress?

[bzmillerboy]

I’m also having this issue. My collation was set to something different so I thought I had found the issue, I changed the collation on the DB using phpMyAdmin>Operations however even after setting the DB to utf8_general_ci I still get the same error.

bbPress 1.0-rc-1

Wordpress MU 2.7.1

BuddyPress 1.0

Can we leave the collation blank in the wp_config.php and while installing bbPress? What is this for?

[thekmen]

Hi all,

Just wondering if anyone has a shared login working with bbPress RC1 & WordPress 2.8 beta?

I have WordPress installed at root level and bbPress in a sub directory using the WordPress users table.

When setting up bbPress I went through all the integration settings.

Now users can log in at either end no problem, it’s just that they are not logged in on the other end when visiting the forum/wordpress.

I then regenerated the keys using http://api.wordpress.org/secret-key/1.1/ and placed these in both config files with the required BB_ bit for the bbPress config.

I added the following to my bbPress config:

$bb->wp_siteurl = 'http://site.com/';

// that's your WordPress URL, not bbPress



$bb->wp_home = 'http://site.com/';

// almost always the same as siteurl unless you tinker



$bb->wp_table_prefix = 'wp_';

// should almost always be wp_ unless you tinkered



$bb->user_bbdb_name = 'xxxx';

// this is the MYSQL database name for *WordPress*

// you can copy it right out of WordPress !



$bb->user_bbdb_user = 'xxxx';

// this is the MYSQL user name for *WordPress*

// you can copy it right out of WordPress !



$bb->user_bbdb_password = 'xxxx';

// this is the MYSQL password for *WordPress*

// you can copy it right out of WordPress !



$bb->user_bbdb_host = 'localhost';

// 99.9% of the time it's going to be localhost, unless you are on DreamHost or some other weird ISP



$bb->custom_user_table = 'wp_users';

// 99.9% of the time it's going to be wp_users



$bb->custom_user_meta_table = 'wp_usermeta';

// 99.9% of the time it's going to be wp_usermeta



$bb->authcookie = 'auth code i set with wp plugin';

// in theory you should be able to leave this out

// but this is going to be copied from WordPress cookie

// this *must* match the WordPress setting

// do NOT use the 1234567 part, use your own cookiehash from WordPress - see the note at the very bottom



$bb->cookiedomain = '.site.com';

// note the leading DOT - this is important

// this *must* match the WordPress setting



$bb->cookiepath = '/';

// I *highly* recommend you set the cookie path to /

// this *must* match the WordPress setting



$bb->sitecookiepath = '/';

// I *highly* recommend you set the cookie path to /

// this *must* match the WordPress setting



$wp->cookiedomain = '.site.com';

define(COOKIE_DOMAIN,'.site.com');

// note the leading DOT - this is important

// we list both for WordPress legacy compatibility



$wp->cookiepath = '/';

$wp->sitecookiepath = '/';

define('COOKIEPATH', '/' );

define('SITECOOKIEPATH', '/');

// I *highly* recommend you set the cookie path to /

Now when I log in at the bbPress side, a wordpress_logged_in_xxxxx cookie is created but then when I visit the wordpress end, I am not logged in.

When I do then log in on the WP end, it creates another wordpress_logged_in_xxxxx cookie, the cookie names are both the exact same but their values are different.

Anybody got any tips on how to fix this?

[dss]

I’ve been living with bbpress and wordpress integrated badly for a while now. I suspect it’s because I can’t really work out where my wordpress secure auth salt is.

I don’t see it in the options.php for wordpress

I’ve tried adding the secure auth key from the config file, an the nonce salt but these don’t work.

I am tired of being logged out of wordpress or bbpress when switching between them.

I have searched this forum, and googled my head off, but there’s no clear explanation I can find on where this simple bit of data lives.

Where is the secure auth salt?

[Atsutane]

@johnhiler

I want to correct something here. Bbpress latests discussion is a wordpress plugin, not a bbpress plugin. It should not conflict with any bbpress function.

[citizenkeith]

Looked in the archives here and couldn’t find a topic specifically about this…

I am fairly well versed in HTML and CSS. I have no programming experience though. I’ve been using bbPress for a couple years now, and have used WordPress for much longer.

I want to learn PHP but I don’t have previous programming/coding experience. I’d probably just use this to write plug-ins.

Can you recommend a good book or online tutorial for the absolute newb?

Thanks!

[_ck_]

There is no place yet for themes.

Even the theme manager on WordPress.org is a fairly new rewrite.

I’ve put your theme on my theme switcher @ bbShowcase.org

http://bbshowcase.org/forums/?bbtheme=bbVanilla

[Ramoonus]

@parallax view;

my provider uses subdomain vhosts …

i presume the problem is in cookies / vhosts + bbpress + wordpress

[chrishajer]

I wonder how hard it would be to do something like a bbMU? Not hosted (like wordpress.com) but just like WMPU?

[thekmen]

You should just be able to edit your bb-config.php in /forum/bbpress/

Look for $bb_table_prefix = ‘englisl5_’; and change englisl5_ to what ever is set in your WordPress wp-config.php

[jpmendoza]

It would be nice to have only one point of signin.

If nothing else works, I guess I’ll just use Hidden Forums and a custom message or something.