[deadlyhifi]

Thanks _ck_. I’m sure it’s easy when you know how.

The cookie now has a different name.

my old cookies are:

$bb->authcookie = ‘wordpress_REPLACEDcabef’;

$bb->secure_auth_cookie = ‘wordpress_sec_REPLACEDcabef’;

$bb->logged_in_cookie = ‘wordpress_logged_in_REPLACEDcabef’;

I was messing with

setcookie('wordpress_logged_in_REPLACEDcabef','',time()-3600)

just placing in the head of my page but I get a headers already sent message.

[ovizii]

I guess the 1.0.1 update fixed it so far. still got two remaining issues:

– the feed still shows every topic/post double

– my key master still has (Inactive) after his name, refreshing sometimes shows him as (key master) but rarely although the integration works, wordpress realizes the user is a keymaster and logged in I can go to the admin part of wordpress and bbpress without hickups, but when viewing a key master’s psot, it still says: Inactive

[clarklab]

Are new users created in WP left as inactive (no role) until they sign in? We saw a bunch of users marked as inactive, but plenty of users posting just fine.

When I went into WordPress Integration Settings – User Role Map everything is set as it should be. Clicking ‘Save Changes’ (without actually making any changes) automatically switched all users marked inactive to member.

We had someone report they were unable to login so I went to check the user’s account and that was when I found his inactive role along with dozens of other users.

When trying to replicate it myself with new, test registrations any user I can create that shows up inactive is immediately switched to member on the first log in.

The main reason I ask if because the number of inactive users seemed very high and simply clicking ‘Save Changes’ and having them all switch in unison seems a bit odd.

[punktoronto]

Has this been solved? I’ve been trying to figure it out as well. Everything I’ve found is for wordpress-mu and I’m not sure what needs to be changed to use it with regular wordpress.

I found this http://insecure.no/2009/01/wordpress-and-bbpress-nice-url-rewrite-for-nginx/ it sort of works. pretty permalinks work but any attached files such as the css sheet or jquery.js returns a 404 not found error. Any Ideas?

# SEO friendly URLs for bbPress

#

location /forums/ {

root /path/to/YOURDIRECTORY/public_html/forums;

index index.php;

if (!-e $request_filename) {

rewrite ^/forums/topic/(.*)$ /forums/topic.php?q=$1 last;

rewrite ^/forums/forum/(.*)$ /forums/forum.php?q=$1 last;

rewrite ^/forums/profile/(.*)$ /forums/profile.php?q=$1 last;

rewrite ^/forums/view/(.*)$ /forums/view.php?q=$1 last;

rewrite ^/forums/tags/(.*)$ /forums/tags.php?q=$1 last;

rewrite ^/forums/rss/(.*)$ /forums/rss.php?q=$1 last;

rewrite ^/forums/bb-admin/ /forums/bb-admin/index.php last;

rewrite ^/forums/ /forums/index.php last;

break;

}

}

[aberrantphoto]

John,

I do not have a WordPress install attached to bbpress. The upgrade went smoothly except for one error that said I already had forums. Other than that, everything seemed to work fine except for the registration. For registration, I am using the plugins “approve user registration”, “terms of service”, and “human test”, but I had deactivated all of these prior to upgrade and then again when testing the default theme.

[johnhiler]

Ah ok.

While we wait for someone to weigh in on this, quick obligatory question: are you using WordPress as well? If so, what version… and have you integrated signin?

[_ck_]

In 1.0 you could use xmlrpc to do that and convert a plugin from WordPress if such a creature exists.

Your best bet is to use a service that is optimized for mobile, maybe like flickr and then use a plugin to post it elsewhere.

[_ck_]

I have to say that while I may not agree with some of the politics around the 1.0 release, the amount of effort Sam has put into 1.0, especially over the past few months, is simply amazing and very impressive. Converting the entire bbPress core to use the WordPress core was not a trivial task.

[Marcomail]

is it possible link, for each registered user, the link to the relative profile on bbpress ?

[leehow]

thanks so much _ck_, it works!

[deadlyhifi]

For WordPress:

<link rel="stylesheet" href="<?php bloginfo('stylesheet_url'); echo '?' . filemtime( get_stylesheet_directory() . '/style.css'); ?>" type="text/css" media="screen, projection" />

For bbPress:

<link rel="stylesheet" href="<?php bb_stylesheet_uri(); echo '?' . filemtime( bb_get_active_theme_directory() . '/style.css'); ?>" type="text/css" media="screen, projection" />

Creates a unique number (based on time) after the filename which is automatically updated if make a change to your stylesheet.

[Caesar]

@_ck_:

See https://codex.wordpress.org/Version_2.7#WordPress_Upgrader – “All file operations are performed as the user that owns the files, not as the web server’s user. All files are set to 0644 and all directories are set to 0755, and writable by only the user and readable by everyone else, including the web server.”

Regarding the phoning home “with all your install info” – according to the docs, the only info sent is your version and locale. I haven’t checked this myself.

Most WordPress users find the “automatic” upgrade very useful, and most bbPress users would too. The sooner it’s available the better, in my opinion, though I don’t know how much work is required to port it from WordPress.

[Ipstenu (Mika Epstein)]

Simon, thanks! That’s perfect for me (since everyone signs up via WordPress on my sites).

[litchi]

Where can I find the document about bbpress with memcached?

I tried to use the object-cache.php for wordpress but it seems does not work.

Can anybody help me?

Thanks in advance.

[michael3185]

Just my tuppence worth, but as I said elsewhere, I’ve taken _ck_’s advice and stuck with 0.9. My forum needs aren’t very demanding, I have all the plugins I need and they work fine, and I don’t use WordPress so integration isn’t an issue. I have enquiries from others who want sites and forums building, but static sites rather than blogs. I can use my DTP package and bbPress 0.9 to do everything very quickly, and have excellent stability from both.

I also agree with _ck_’s points about core vs. plugins. From what I can gather, the original idea was to have a fast, secure, and plugin extensible system. Even as a user rather than a developer that makes a lot of sense to me. It means the core quickly becomes more and more stable, and anyone is free to develop whatever they want to hook into it. Brilliant. But putting various functions into the core means that any changes have to be redone by Sam et. al. and re-uploaded, hacked in the core by users, or redeveloped by hooking in a plugin to change the functionality. As everyone has differing needs and opinions, plugins for anything but basic core functions leave open far more options. Anything which is not essential to all users is not a core function. Gravatars, for example, are not required or even wanted by many users.

As to people remembering old versions with fondness, but having moved on with each bleeding edge version, I’d suggest that it’s only those who keep moving on who voice their opinions most in these forums. There are huge numbers of users who’ve built forums with very old packages of all kinds, and when they build new ones they use the old software too. I think it’s important that those who love bleeding edge, along with the challenges and time consuming re-uploading and fiddling around, don’t forget that many people are perfectly happy with what works and see no need to keep reinventing the wheel. After all, how much better really, do all these new ideas and functions appearing all over the web make life? This is probably a point for a philosophical forum, but worth mentioning I think. We seem to spend so much time redoing and redoing, that often purpose is lost in the background noise of being so busy changing everything. We live in a, “Yippee, it’s new!” culture, where anything which doesn’t titillate the mind is ditched for whatever’s next.

New functionality is great if it’s genuinely useful, but I’m glad 0.9.0.5 exists and works so well, and the occasional security update will do fine. Incidentally, I’d quite like to see a separate 0.9 forum. It would save 0.9 users having to wade through all the 1.0 questions and allow us to quickly see what’s relevant.

[_ck_]

@Gautam: the auto-upgrade feature in wordpress requires you to make your directories world-writeable which is very dangerous. Also it “phones home” with all your install info, which I am not certain everyone wants to happen. I suspect it’s unfortunately going to come to bbPress eventually but I wouldn’t be in a rush for it.

[grassrootspa]

@Jason_JM: Buddypress? No way, that’s overkill and misses my point. Gravatars are built into the bbPress (its part of the CORE). If Gravatars are turned on and someone tries to edit their profile (think newbie who wants to pick their picture) it makes sense for there to be information re: where they can get one. Hyperlinked note directing them to Gravatar.com. Blam. Done.

Best of all, no one will ever need to use avatar uploading plugins ever again. It would solve so many problems.

@Marcomail: if they uploaded the same avatar via a WordPress avatar uploading program and bbPress avatar uploading program, sure why not?

[buddha-trance]

Thank you for the clarification. I have now reactivated the plugin. It is indeed necessary to enter the bb-admin area, when logging in from WordPress.

[Gautam]

Hmm.. upgrading……….

In the next release please also put auto update feature…. like wordpress notifies you to upgrade and then automatically upgrades in a single click….

[r-a-y]

Thanks Sam for the update and to _cK_ as well for posting just the changed files.

Question for you Sam.

Does this fix how user roles are mapped between WP and bbPress?

When a WPMU site administrator makes a forum post in bbPress, in the bbPress admin area, it shows the user as a regular member, instead of a Key Master (or whatever role you setup in bbPress’s user role map to sync up with WordPress).

The only person who seems to be a Key Master is the WP user who integrated bbPress.

Is this the way it is supposed to work currently?

I should also mention that I’m using BuddyPress, so that maybe a contributing factor.

[John James Jacoby]

Out with the old, in with the new.

If it wasn’t against the grain to open up a .9 legacy forum here specifically for supporting it, I’d say just do that and see who falls into it.

A majority of the audience of bbPress are people that want to be on the bleeding edge of WordPress development, and be part of a growing and maturing community. As such, people will remember .9 of bbPress as much as they remember .9 of WordPress (b2evo anyone?)

I personally think anything officially past the end of 2009 is a stretch, and is a very generous offer from Sam to not leave the early adopters on their own without patches and support.

[_ck_]

Read Only Forums has not been tested or fixed to work on bbPress 1.0 which is why you are probably having problems. If any of my plugins work on 1.0 it’s mostly luck at this point.

As far as hosting, I wrote this little bit last year:

http://ckon.wordpress.com/2008/12/18/some-tech-tips-to-find-a-better-wordpress-or-bbpress-host/

[QuickD]

I decided to test out this new version of bbpress on another website I have on Godaddy. I couldn’t link from BBPress to the Msql wordpress database and followed the steps to link to the database. Godaddy tested out and said that nothing wrong with the database.

BBpress asking for

Database Name (so tried with both Name and host name)

Database User (so put in godaddy msql User Name for wordpress database)

Database Password (Put in password to link to that database)

Did not work and gave following message : There was a problem connecting to the database you specified.

Please check the settings, then try again.

Godaddy said that the settings are fine.

Any suggestions.

[toosalty]

Hi smi1ey,

Could you elaborate on how you resolved the problem? I’m facing the same problem that you have but I don’t really understand your solution.

Thanks!

[_ck_]

If I missed such a large site in the top 100 be sure to let me know.

Sometimes it’s hard for me to find certain sites given how much bbPress is being customized.

(I had written a whole thing here but I accidentally closed the tab and restoring it never brought the text back unfortunately.)

You should never adopt a program based on one person, especially if that person doesn’t do it for a living and even more important since that person doesn’t work for the company that made the program in the first place

To be clear I am not abandoning bbPress, at least not until I find something better and I am not actually looking for something else right now and what I have seen over the past year has not impressed me much. Besides, there are other talents around here and they are slowing releasing more and more impressive plugins or porting them from WP. A couple years from now people won’t even remember me.

My biggest problem with 1.0 is how bbPress was on a course with 0.9 to correct many of the legacy mistakes that WordPress had made, and suddenly with a whim by Matt, bbPress has turned around 180 degrees and steered itself neck deep back into the muck and mire via BackPress. It’s now burdened with many more layers and required compatibility and it will never be any more lightweight than it is now, which is not so fantastic anymore.

Another big problem growing with 1.0 is how instead of taking any feature that is outside of the API functionality and making it external as a plugin, it is being poured directly into the core, setting itself up for more legacy failure, like WordPress. Sam wrote some really great plugins as an independent but now as a core developer he can just slide it right into the core. It’s far easier to modified the core to get new features done fast but it should be resisted at all costs. You’ll notice that WordPress doesn’t have any official plugins outside of akismet and “hello dolly”, it’s a very clear but invisible company policy – “we don’t make plugins, put it into the core”. bbPress is now headed down the same path and it’s not necessary.

Things like:

gravatars

voices

topic page icons

should not be in the core. Instead any necessary action and filter hooks needed to accomplish such features should be carefully created and then the features should be made as plugins that can be enabled or disabled as desired. bbPress already comes with a “factory” plugin directory, it should be put to good use.

bbPress 0.9’s greatest strength was as a lightweight framework.

1.0 is not just a framework anymore, it’s starting to tell you how it should look and feel, and that is bad, because there are dozens of other forum programs out there that will do just that.