[Sam Bauers]

The only gotchas with bbPress-1.0-alpha (up to alpha-6) are the less stable code and a few missing functionalities with regards to tag management. If you are doing “deep” integration then there are reported problems with language translation files not being loaded. There are some other sundry issues as well, most of which just need some quality time with a PHP person to fix.

[Sam Bauers]

Also, a plus for bbPress is that it has built-in user integration with WordPress – which as far as I know doesn’t exist on any other platform.

If you have the coding resources in-house and are familiar with WordPress development, I think you will find bbPress quite comfortable and flexible. However, in it’s current alpha state, bbPress is not for the faint of heart, there are known bugs and missing functionality in the current releases. But if you have people willing to fix them, submitted patches will be in core before you know it.

[Sam Bauers]

Actually, in bbPress 1.0 you can drop in the memcached object cache plugin from WordPress. This cuts out a lot of MySQL queries. There is no page caching solution that I know of, although we get by without it on all our installs (wordpress.com, wordpress.org, etc.).

[Sam Bauers]

It’s not in bbPress 0.9, you need to run the alpha to get that functionality.

[Sam Bauers]

How many more alphas? I don’t think we’ll get up to 10, but if a bad bug sneaks into one of the alphas it’s possible that you could see two or three in a week. I’m not doing any point releases of alphas (e.g. alpha-6.1) so by the time we are done we may have 10 or 20, it’s hard to say.

Basically we aren’t going to beta until all the new functionality is in place. During the beta period I’m hoping to just be doing stability and speed improvements. The Trac tickets are a good guide of what needs to be done before beta is released. As long as there is significant stuff on that list under 1.0-beta there is no beta release.

In any case, the beta will not be “stable”, it will only be feature complete. So it still won’t be recommended for production use. Things will be accelerating for bbPress soon due to some internal work at Automattic. This is occupying a lot of my time right now, but it will all be fed back into bbPress in the near future.

And yes alpha-7 will be a commit bomb that will potentially break a lot of things. I’m trying to minimise damage, but the API will be a little unstable for a couple of alpha releases. I don’t recommend that plugin devs rush to make their plugins work until these fairly fundamental shifts in the API are complete.

[_ck_]

Sam does not delay bbPress because of plugins or design it in one way or another for them other than to make the hooks or filters they need.

If you don’t use plugin then just use the SVN with the trunk and you can have weekly updates as Sam makes them.

[frooyo]

@ _ck_

Thanks for the reply.

Nope, I don’t use plugins.

As for that topic, your response makes it sound like a large reason why bbPress is slow to release is due to the fact that plugins will break.

Maybe I’m a little confused here but what’s the problem with that?

Plug-ins are just that, “plugins”. They are not part of the core product.

Just an observation, but it seems to me that something that is not apart of the core product, like plug-ins, shouldn’t slow down the release of the core product.

(Especially plug-ins developed for a non-stable, non-1.0 release)

Just my 2 cents

[sumit1988]

hey guys, just another idea:

what about integrate bbpress and wordpress that far (maybe with a plugin) that if registered and logged in users post a comment at a wordpress blog-post, this comment will appear in the profile of bbPress users under “user activity”.

And related to that:

WordPress users doesnt really have a profile page, so it would be nice if a user register and post a blog-comment, his name-link would open his bbpress profile page.

Hope you understand what i mean. I think it isnt that difficult. But too much difficult for me

greetings

Sumit

[_ck_]

You keep quoting other people and their nonsense lists.

Those are commercial programmers with commercial projects.

bbPress is free and makes no money for the people who make it available.

(Joel isn’t even a programmer according to Wikipedia, but was a manager on Excel for Microsoft, so he couldn’t be more opposite in thinking to open-source web based code development – he blogs about concepts to sell his company’s commercial, closed-source software so what he says is motivated by profit)

Let’s say bbPress 1.0 final was available tomorrow.

But half the plugins won’t work with it, so are you going to fix them?

Let’s say Sam gives into your pressure and releases bbPress 1.0 beta early – but because of the rush there are bugs or security issues – are you going to fix them? Are you going to adjust the plugins for bbPress 1.1 because of rushed release on bbPress 1.0 ? I’m not.

I can give you my timeline as far as plugins – January 2010 is my estimated completion date for plugin compatibility with bbPress 1.0 – this is not an exaggeration. Hopefully this will satisfy your quest for deadlines on free, non-commercial programs and let you plan accordingly.

So if you aren’t using any plugins, I guess you’ll be all set for the next alpha and beta releases, nag away.

[frooyo]

@ _ck_

How is this a pointless question?

Simply saying that bbPress 1.0 will be finished “when it’s ready”, is an absolute lack of leadership.

And using Trac’s Roadmap functionality but not updating it to be current, since it states bbPress is 6 months behind, indicates also a lack of commitment by the development team to push this project forward.

Also, don’t you find it interesting that you have had to make the comment before numerous times and say “people, please stop asking for a release date”.

https://bbpress.org/forums/topic/eta-of-bbpress-10#post-21764

I’m not even asking for a specific date, just a better understanding of the roadmap. If people are constantly asking you the same question over and over again, isn’t that a signal to you that people are: concerned with the current development state and/or unclear as to what the roadmap current entails.

Unfortunately, not everyone here is a developer. So simply stating “why don’t you help code” is not an option always. The best many of us can do is simply use the ALPHA version and report bugs if we see any … which we do.

P.S.

Also, one thing good about roadmaps is that it holds people accountable. Having a roadmap in Trac that, as you have stated before is “meaningless”

https://bbpress.org/forums/topic/yet-another-10-timeline-roadmap-question#post-22122

is a complete embarrassment to this development project. I hate saying that, truly, because I greatly enjoy bbPress.

But if you cannot even update a simply Roadmap, now 6 months out dated, indicates to me that bbPress 1.0 is vaporware … regardless of how many Trac ticket check-ins you have in any given week.

I’m not alone on this, Joel Spolsky include keeping Roadmaps up-to-date on his 12 steps for better coding

http://www.joelonsoftware.com/articles/fog0000000043.html

[_ck_]

Dozens more. At least that what you should be assuming.

But more importantly, alpha 7 will break roughly one third to one half of the plugins for bbPress (seriously) so if you rely on any, you won’t be using more alphas or using the beta any time this year.

(and please stop asking questions like this, they are pointless)

[chrishajer]

Looks to me like you are not logged in as keymaster, but as administrator maybe. That means bbPress does not know you’re keymaster and the WordPress user you logged in as does not have the proper permissions.

[chrishajer]

This looks pretty similar to what you are doing:

https://bbpress.org/forums/topic/latest-wordpress-stories

It’s latest stories not a page menu, but still, it’s querying WordPress from within bbPress.

[John James Jacoby]

Also don’t forget to copy over the code from the .htaccess file that bbPress semi tries to generate for you. Simply changing the setting in the drop down box isn’t enough.

[frooyo]

Curious to know how many more ALPHA builds to expect before the builds move into BETA.

We are currently on build 6, I see a soon to be released ALPHA v7 is in the pipe.

Not trying to hold the bbPress team to a specific # of releases or anything, just curious if we have just a few more ALPHA’s or like a dozen more before BETA begins

For what it’s worth, I have been using ALPHA v6 since release without any problems.

[matthijs]

I have wp and bbpress succesfully integrated. Now in my bbpress forum I’d like to display the wordpress pages. Basicly I want to replicate wp_list_pages() from wp. I know there’s a way to include wp in total inside bbpress. but that has a performance penalty and I’m also afraid it might cause bugs in the future.

So I’d prefer a simple query. What I have thus far:

global $bbdb;

$query = "SELECT wp_posts.*

FROM  wp_posts

WHERE wp_posts.post_status = 'publish'

AND wp_posts.post_type = 'page'

ORDER BY wp_posts.post_date DESC ";

$results=$bbdb->get_results($query);

foreach($results as $result) {

echo '<li><a href="' . $result->guid . '">' . $result->post_name . '</a></li>';

}

But I need a query which replicates wp_list_pages() closer. Where can I find that function in wordpress? Or how could I improve my query so that I get the subpages as well, for example?

[hpguru]

Ok, thanks for this information!

[Ipstenu (Mika Epstein)]

You can change the post.php template page to make the avatar link to the profile.

I have it so the name links there and it works fine.

<a href="/forums/profile/<?php post_author_id(); ?>"><?php post_author(); ?></a>

As for the URL not updating, this is fixed in the Trunk build, but I don’t think it’s made it to the alpha yet. See https://trac.bbpress.org/changeset/1930

[John James Jacoby]

Yeah some of my users haven’t updated their profiles, and BuddyPress doesn’t recognize them until either they do, or I force the info (which I will probably do.)

@TeddyC, it took me installing WordPressMU 4 times before I followed the instructions correctly, and I’d recommend not doing it on Valentines weekend so your girlfriend doesn’t hate you for a few days, but otherwise I think it went as smoothly as it could considering I migrated 200 users from WordPress.org/bbPress over to MU. There’s a few places where I had to trial and error my way through the multi-blog switchover and the URL re-writing still isn’t perfect (categories and postnames are broken?) and I had to manually dump the DB and replace all the directory references for all of the uploaded media.

Otherwise the rest was just tweaking and tinkering. Lots of it.

I’ve got the forums FULLY integrated now with BuddyPress, so single account access, cookies, and users are able to post to group forums from within the group itself, and vice versa. It’s a neat little bridge and I rather like that it’s all playing nice. Hopefully upgrading to 1.0 or new alpha’s doesn’t TOTALLY break everything too badly, although I anticipate that it probably will. Yay!

I am going to be using BuddyPress to do a small social networking site for a non profit, that is going to be incorporating some school related content, so I will let you know how that goes and be sure to stay in touch as it progresses. I’ll link back to it here if we decide to incorporate bbPress.

[Alvaro Degives-Mas]

richcon: mah plezure.

chrishajer stated:

I still can’t figure out why people want integrated logins, why they have users that both post to a blog and post in a forum.

I’ll give you a real-life example. When WordPress is not used as a blog, but as a CMS, and its support for registered members serves to allow restricted reading access (so, not even posting!) to certain pages / posts (or portions thereof), those members need to log in, so as to be able to read those parts that are off-limits to guests. Now, let’s imagine such a blog-turned-CMS has a forum as well. And that said members were put through the hassle of logging in again on exactly the same site – just to be able to access a forum, where they “really” participate and exchange posts. No explanation on technicalities like “cookie synchronization” could undo their irritation, and frankly, I’ve joined their chorus. If only because the customer is king.

So, allow me to invert the perspective here: why on Earth would anyone even want to justify a klutzy non-unified login system that doesn’t recognize users who logged in on one part to access another of the same site, that is driven by software that, ordinarily, ought to be considered siblings?

Don’t get me wrong – I very well understand and accept the premise of technical difficulty. I have no problem in assessing it as merely the way it is, and patiently awaiting (and appreciating) the effort underway to address this issue. But I see no merit whatsoever in attempts to belittle the annoyance and inconvenience to users – remember: they make the site worthwhile – by way of questioning the validity of expecting a unified login. Human logic and behavior isn’t necessarily always linear in its expression, but it is what one has to deal with, in order to lead a practical and profitable (as in: rewarding) life.

And this inconvenient thing called real life is what made me, in the end, opt for a non-bbPress forum solution for a professional association: because I’m totally, utterly, radically done with dealing with complaints from non-technically oriented member users about “not being able to access” the site that they in essence (through membership of the association) paid for.

Is this a majority scenario? No, of course not. But it is very real. Hopefully now you understand why there’s interest in a unified login system, shared among WordPress and bbPress.

(Added afterwards: if you’re looking for the forum, you won’t see it until you logged in – it appears in the navigation menu only after you logged in as a member. And for the really curious: I opted for the SPF route to solve the login issue, while still remaining in the WP family.)

[chrishajer]

There is no documentation for it really, at this point. It’s easiest to just look at existing plugins, and if you’re familiar with the way WordPress plugins work , bbPress works similarly.

There have been a couple of attempts at listing bbPress functions:

https://bbpress.org/forums/topic/writing-and-uploading-plugins

https://bbpress.org/forums/topic/list-of-filtersactions#post-22463

https://bbpress.org/forums/topic/function-list-for-v10-alpha-one

[davidjmartin]

I want to develop some plugins for bbpress, but cannot fid any documentation anywhere, is there anything that I can look at to get a list of filters/actions and what they do? bbpress looks great, but without any documentation for plugin developers its kinda hard to build for it…

Cheers.

[PJ Brunet]

@chrishajer thanks I’ll check that out.

But, I’d like to fix this problem because the URL of the “member” is very important to me. Should I start reading “https://plugins-dev.bbpress.org/” or? I’d like to help work on the code but I have no experience contributing to open source.

As it is now, the URL is not saved, it’s not even in the list on the profile page.

I’m guessing that’s the responsibility of the “bb_get_current_user_info( ‘id’ );” function?

I personally think clicking the member’s pic should take you to their profile, that would be more intuitive IMO. I wouldn’t expect to click the text “Member” to see a profile, and that makes even less sense if I give the member some custom name under his/her picture. Let’s say a member works for XYZ Inc. Now I want to show “XYZ Inc.” under his/her profile picture, a pretty typical use of the member’s custom title. To me it would make more sense to link “XYZ Inc.” to XYZ.com using the member’s URL. But the way you have it now, clicking “XYZ Inc.” takes you to his/her profile page, which doesn’t make sense to me.

[revilo78]

Thanks for the links. I was hoping there was a built-in BBpress function and it turns out there is one. I found bb_get_usermeta(), and everything worked great.

[_ck_]

Top 1000 gets updated with Top 100, sometime in April, maybe end of March if I have time, not before then. Look for the Firefox 3.1 release date as a guide since 3.1beta has a bug I need to wait for them to fix.