Not in the plugin yet, and there is a ticket for this already regarding Forum Types.
(Some of this kind of display may be template specific since bbPress has always been more topic centric than forum/category centric.)
Thanks for checking it out though 
Not in the plugin yet, and there is a ticket for this already regarding Forum Types.
(Some of this kind of display may be template specific since bbPress has always been more topic centric than forum/category centric.)
Thanks for checking it out though
Thanks Rich!
Closing this topic to prevent more cross posting and confusion.
Wednesdays @ 2100 GMT
irc.freenode.net
#bbpress
I just committed a first pass at New Topic and Reply forms. They need escaping and a security sweep, but appear to work well enough so far.
I’ve also opened a few tickets for a few things that I haven’t started, for those that are interested in getting involved and dirty with some code.
Will be trying to hammer out the topic/reply counts this week, as well as a very basic front end New Topic/New Reply form.
That’s all it needs to be functioning in a skeletal capacity for initial proof of concept testing and iteration.
I didn’t write a single line of code during WordCamp NYC; spent most of the time supporting BuddyPress questions with our two new core committers, Paul Gibbs and Boone Gorges.
I leave again this Friday through Monday for the Google Summer of Code Mentor Summit, so this week is a short dev week.
Any interest in doing a development chat in IRC next week?
(at least that is my understanding)
Correct. Looking more like October 17 now, to be exact.
On Sunday at WordCamp NYC I’ll be presenting a 5 minute lightning session on the plugins progress so far. Worked on it a little today, and will be doing more until then to have something presentable.
BuddyPress acts as a wrapper for bbPress to get it to work seamlessly inside of WordPress, so using this built in method you won’t have access to the bbPress administration area to play with bbPress plugins.
BuddyPress acts as a wrapper for bbPress to get it to work seamlessly inside of WordPress, so using this built in method you won’t have access to the bbPress administration area to play with bbPress plugins.
If bbpress plugin use wordpress custom post types, is that mean that plugin how work on wordpress will work also with bbpress (like subscripte to comment for wordpress, similar topic plugin for wordpress …etc) ?
Things that bbPress can already do won’t disappear, but will rely on WordPress core functionality to replace them where possible.
Can you give us an idea how theme’ing will work when it is a plugin? Will it base itself around the current WordPress theme and kind of insert itself inside a blog post like other forum plugins do?
Like Kevin said, out of the box you could use the WordPress post type templates and easily make files to fit any theme. I’d also like to have a format similar to WordPress and BuddyPress, where maybe you can stash all of your bbPress template files in a subdirectory so they don’t get intermingled with your existing template files.
Matt and I have shared a similar dream for allowing blog posts to either act as or create their own dedicated forums, allowing for dedicated topics and branched discussions about those blog posts. Linear comment rivers often end up with hundreds of comments with no way to tell what is relavent to what you’re looking for. Allowing subscribed users to create topics around blog posts inside one installation could change things up in a really neat way. But, you can see how theming that could get complicated…
Honestly themes and plugins are really hard right now because there are a lot of dependency issues to try to work around, and I don’t have a 100% fool-proof plan yet. Once it’s time to start thinking about integrating bbPress into existing themes, we’ll probably huddle up with the WP core devs and talk about what everyone thinks makes the most sense.
@qprints That is the plan. Anything that might add any extra bloat should be modular, so you can turn each component on or off as needed. A good example would be that there’s no need to load up bbPress User Profile code if BuddyPress is there to handle things.
@Jyri No promises about a SimplePress importer at launch, but in the spirit of owning your own data it would make sense to have that too.
Update: Just emptied out http://bbdevel.wordpress.com and moved everything to http://bbpdevel.wordpress.com. No sense in having two development blogs. The prior should eventually be deleted.
Re: Legacy plugins – It’s low on the list, but I think it’s important there be /some/ level of support. Would really be a shame to lose 100% of that time and effort.
@tonicarr – Nothing will be changing soon, so no worry there. Eventually the goal is to give bbPress users the option of migrating their existing installations into something more tightly integrated with WordPress as a plugin, instead of as a bridged (deeply integrated) stand-alone installation.
A few thoughts.
If you’re going to fork it, call it something new and fork it. Sever the ties so that discussion can start someplace else and these forums can continue to be used for bbPress. It’s in bad taste to rally the troops on this website for something that will only further fragment the already small community we have.
If you’d like to continue to support or contribute to your favorite existing branch of bbPress, that doesn’t require a fork; it requires ownership and dedication like _ck_ has for 0.9.
Quick update – Aiming for October 15 for the aforementioned super-pre-alpha. Pete Mall is waiting on me to commit a few local additions that need to be fixed up before he jumps back into the fray. Glad to have him back aboard.
@erlend – Understandable. Will try to do better.
@mbiernat – Thanks for the pat on the back. Definitely helps to have some support
I’ve been side tracked with BuddyPress bugs and paying work, so don’t expect anything official for a week or two. I have a few projects coming up fast that will need this working so while I’m missing my soft Sept 15 deadline, I don’t think it will be /too/ far off.
Sorry to disappoint, it’s no fun… and thanks for your patience with me and it.
For the record, I love bbPress. I have a few commits going into 1.1, and I have every intention of making bbPress be the best it can be as a WordPress plugin.
Regarding my motivation and priority, it’s to make great forum software that fits inside WordPress; nothing more and nothing less.
Regarding why I was able to step into this role, it’s because our peers believe I am capable, and I am willing to dedicate time and effort towards it getting it done.
Regarding any possible benefit BuddyPress might see, is a welcome bonus but not a priority. BuddyPress/bbPress processing times should decrease with BuddyPress 1.2.6, as a few tweaks have been made and a bug or two have been patched in that regard. Even still, nothing compares to the blazing fast speed of bbPress by itself, even in the slower 1.x branch.
Regarding everything else, I’m just here to write the best code I can, help make bbPress a great WordPress plugin, and have fun doing it all. So far, so good on my end.
I don’t even know what to say right now.
I want you all to know I’m reading everything, but I’m speechless.
@_ck_ I think that’s a good idea. Anything to minimize confusion.
Aw, you’re all so afflicted.
A few of the more vocal people in the BuddyPress forums raised concerns about me dual wielding projects, so it made more sense to address it there than here. Plus there’s a bigger audience over there, and since both blogs feed into the WP dashboard you’re all going to see it regardless.
It’s easy to assume that no one is thinking of you guys, I am, I was, and I did.
And yes, I’d like to have /something/ usable in a month or so, like I said in that post “give or take a missing feature or two.”
So, buck up. 
johnhiler, part of us using WordPress’s built in API and architecture means we’re actually leaving turned off a lot of functionality that could easily be turned on, filtered, changed, or added to with actions.
Without it being too over the top, we’re trying to plan ahead and put actions and filters where I think I would use them myself. Since most of what we do for clients is develop custom plugins to change the way WordPress functions, we should be able to apply that experience to bbPress.
One of the things we’ve struggled on with BuddyPress, is how to make plugins, for plugins. Since plugins don’t have an internal dependency like there is on CSS or JS, we’ve had to filter and action our way into a workable solution.
So while bbPress itself is a plugin, the plan is for other plugins to be able to sneak in and change bbPress behavior before it loads, or be able to ‘plug in’ the same as always. So bbPress will be its own core, but also modular and pluggable.
All this, while striving to be as light as possible. Our work is cut out for us.
I think if there was such a thing as optimism police, they would live in these forums.
I also think, the people we will win over, are everyone that thinks this is the worst thing ever to happen since burnt bread.
I think bbPress as a plugin is going to win a lot of people once it’s ready and out in the wild.
Erlend, will try my darnedest to deliver
johnhiler, if you like plugin-centric development, you should love the bbPress plugin so far (hopefully) Hopefully it’s able to walk the line and offer the best to both.
What is a plugin and what is core is always one of those topics that tends to change and drift with the times. 6 years ago having properly formatted links to someones blogroll was considered important enough for WordPress core, but chances are people are using that functionality less and less as time goes on and people are able to connect to people more quickly and organically.
kevinjohn, we haven’t tackled it in the plugin version yet, but the difference between a ‘category’ and a ‘forum’ will be fairly distinct once we get it going. My experience working with the Categories Hierarchy project back in my phpBB days taught me the importance of handling the way those types of data behave.
Pete and I talked about this in #bbpress last night a little bit. Using WP post types lets us inherit all this neat stuff, but much of it isn’t really /needed/…
Like Forum/Topic/Reply revisions, comments, thumbnails, excerpts, etc… Sure there’s lots of neat ways those things could be used, but they don’t help keep things trim and tidy.
Would love to get some good feedback on this!
Thinking part of the JS minify issue may have been not emptying the cache after changing the settings. Before I wasn’t automatically uploading the changes to the CDN.
Seems to be fine now, and can’t duplicate it when I want to see it.
If you really want it minified, I’m happy to get the plugin author involved in testing, to see if it’s a w3tc or bbPress issue.
Spent the past week or so testing a few larger BuddyPress/bbPress installations with W3TC, and I can say that it works a treat with the bundled version of bbPress we tuck in there too.
Experienced the same JS minify on the inline JS also actually. Wonder if it’s a bug. I’ll see what I can dig up.
