[Ipstenu (Mika Epstein)]

This is NOT an attempt to knock _ck_ (any more than she meant to diss on Sam), as her points are totally valid and, in fact, I’m a member of ‘If it ain’t broke…’ If you’re ON .9 and everything works and you’re happy, then STAY. If you have needs that can no longer be met by .9, however, you may need to start looking into 1.0. There’s a reason that some people are still on WP 1.5ish releases. It works and they’re happy. There’s nothing wrong with it.

My reasons to use 1.0

1. You haven’t installed bbPress yet, so you don’t have an existing stable site.

2. You don’t actually use a lot of plugins anyway.

3. You can integrate with WP 2.8 and WPMU without having to hack the bbPress cookies (thanks to WP changing things all over the dang place…)

4. The Admin area ‘matches’ WP and, lets face it, pretty is better

5. If you’re going to write new plugins for bb, you may as well write them for the release version since that’s the way it’s going to be.

6. While it is slower, we’re not talking ‘it now takes 3 minutes to load a page’ like some bbs out there. And it’s still faster than WP.

7. Given the speed of servers these days, you may not ever notice the DB queries.

8. No matter how long you spend debugging, you’re never going to find all the bugs until something’s used for real by hundreds of users, so months vs years really doesn’t mean as much as you might think. Now DAYS versus months… Still, until a lot of people get out there and try to use it for weird ways, 1.0 won’t be as well tested as 0.9, but that’s true of any new release of software.

9. RC seems rushed, with a lot of slapped up fixes, but that’s because a group of us were out there breaking things for the rest of you. The major kinks are fixed.

10. Once you bite the bullet, the small upgrade to 1.0.1 (which is inevitable and we all know it) will seem like nothing.

11. You really want to see that download counter MOVE!

Okay, so some of mine are for the amusing side.

I’ve been on the 1.0 train since I started, since at the time you couldn’t do 2.7 WP and 0.9 BB. I’ve never had a major OMG! show stopper problem and I think bbPress is far far better than the old systems I’ve used. Small, simple, easy.

Thanks to Sam and also SO many thanks to _ck_ for her patience with stupid questions

[johnhiler]

@frooyo – I agree that changing the name to Release Candidate greatly increased community involvement. Marking a release as 1.0 stable seems like a scary way (to me) to increase involvement! But maybe the release will be stable, and my skepticism is unwarranted. Looking forward to seeing how the release goes.

But can I ask that you please not attack active members of the bbPress community? _ck_ has done more than almost any other volunteer to help extend the power of bbPress. I’ve seen a number of open source projects where someone is told that if they disagree with something, they should shut up and just fork the code. I hope that bbPress doesn’t become one of those sorts of projects.

Good luck with the release Sam!

[Ipstenu (Mika Epstein)]

Y’know, most of my users never realize they can change that so it’s never come up before. That’s a good point! You used to be able to use post_author_id(), but that stopped working in the 1.0 series.

[_ck_]

A reminder to those using 0.9 not to upgrade to 1.0 yet as many of my plugins (and others) do not support 1.0. I will not be addressing plugin upgrades until December.

10 reasons why to wait a few months to upgrade to bbPress 1.0

1. Your 0.9 install is stable and the core is secure

2. Roughly half the plugins for 0.9 will not currently work with 1.0

3. Once you upgrade you cannot downgrade due to database changes

4. It does not have significant additional features over 0.9

5. It doesn’t use the proven 0.9 core, major parts have been rewritten for BackPress

6. It’s slower, uses 50% more code when producing the same output as 0.9

7. It uses more database queries per page than 0.9

8. It’s code has only months of debugging vs years for 0.8 + 0.9

9. RC was rushed, some changes were made only days ago and are not well tested

10. Version 1.0.1 will be out in a few days (if not a few hours)

[Filipe Deschamps]

Wow, really nice! I was expecting this only in 2010

[frooyo]

@Sam

Thanks for the 1.0 release !!!

Quick question. I don’t believe what you changed in the core is still the desired result.

I only have 1 forum, and that forum is called = “All”.

I have the following code in my post-form.php template

<label for=”forum_id”>Category:

<?php bb_new_topic_forum_dropdown(); ?>

</label>

It’s printing/echoing to the screen the forum name (“All”) –> see image below

http://img22.imageshack.us/img22/4105/categoryy.png

The generated HTML is:

<label for=”forum_id”>Category:

<input type=”hidden” name=”forum_id” id=”forum-id” value=”1″ /><span>All</span> </label>

It seems to me that if someone only has 1 forum, that you should simply have the hidden input and NOT print the forum name in any SPAN element at all.

Do you agree?

[Gautam]

I just wanted that plugin to work, so just researched a little bit and here is the fix.

Open the plugin-browser.php

Add this line below <?php at the top:

if ($_GET['plugin'] == 'plugin_browser_admin_page') { include( '../bb-admin/includes/functions.bb-plugin.php' ); }

Note: If you have plugin-browser file in another folder within my-plugins, then use this:

if ($_GET['plugin'] == 'plugin_browser_admin_page') { include( '../../bb-admin/includes/functions.bb-plugin.php' ); }

[plop]

Hi all,

I have a bbPress 1.0-alpha-6 running, and I don’t know why the favorites link on a topic doesn’t entirely work.

When I click on the link “Add this topic to your favorites”, it creates a meta on the database “bb_favorites” with the proper id, BUT, the link still shows “add this topic to your favorites” instead of a link to the favorite page.

AND, if I add another topic to my favs, it doesn’t add the id with the previous ones, but overrides the meta_value with the new one

Is it a known bug or is something wrong with my bbpress ..?

[Gautam]

Thanks Mate

I am the 24th to download it

I will also write a blog post on it….

[Arturo]

ehi Sam thanks!

is possible have the pot for the 1.0 release? in the svn repo the last pot is for the rev 2285… i have to make the localization before update or my users kill me

Thanks!

[teknohippy]

Like the download counter, I was twelfth to download at 12 minutes

Admin looks loverly now.

Draggable forum order is nice.

[clarklab]

I’m also curious about this. Using

<a href="/profile/<?php post_author(); ?>">User Profile</a>

doesn’t work for me since some users have display names that aren’t their user name. Is there not a simple bbPress template tag for calling the link to the user profile?

[chrishajer]

Or, the FAQ here:

https://bbpress.org/documentation/faq/#pretty-permalinks

Note, for people who cannot get this to work on a 1&1 server, you need to put this at the top of your .htaccess file:

Options -MultiViews

The Options +MultiViews does not work (IME) at 1&1, so in addition to creating the rewrite rules manually as in the FAQ, you need to DISABLE MultiViews to make this work. Worked for me.

[chrishajer]

Frooyo, to answer your question, you can remove that dropdown as you did, but first you need to add the forum name as hidden value to the form. You can look at the source of a rendered page, find the select, grab the form field name and value, and just code that into the form as a hidden value. That way, when you submit the form, it looks the same to bbPress as if someone had actually selected one (of one) value for a forum name.

Mine looks like this (your forum ID might be different):

<input type="hidden" name="forum_id" value="1" />

[chrishajer]

Heh, Sam. It’s been like that since the 0.7 series I think. I’ve only ever had one forum, but it always showed the dropdown I used to fix it but them maintaining the changes across updates became a hassle.

Also, the width of the dropdown was never wide enough, in FF3 (and FF2) at least. Never really tested it. I can’t recall if it was fixable with CSS or if that width was in the template. I think in the template with a width=”xx” value.

Was going to take a screenshot just now, but I realized I took the select out in my installation, so people don’t have to choose, and hardcoded the value into the form. BUT, there is still a dropdown with just one value (if you have just one forum) when you’re logged in as keymaster and you have the option to move the topic to another forum. Probably shouldn’t even show the option to move it to another forum if there’s only one.

Weird that this is just coming up now. I always just thought it was normal.

[Sam Bauers]

In bbPress to use SSL you need these in your bb-config.php:

define('BB_FORCE_SSL_USER_FORMS', true);

define('BB_FORCE_SSL_ADMIN', true);

[Jason Giedymin]

WPMU Trunk + bbPress Latest RC + Integration Plugin with:

define(‘FORCE_SSL_LOGIN’, true);

define(‘FORCE_SSL_ADMIN’, true);

Does not work. Setting the values to false (disabling SSL/HTTPS), integration works great. However when it comes to SSL, forget it. I’m going to say it’s impossible.

We need SSL to work across software packages, security is paramount.

Any help from anyone or the devs, let me know.

Again, this is a SSL WPMU install.

[Sam Bauers]

In bbPress 1.0 you can use post_position() inside the loop of posts.

[smfadmin]

Uhhh…I’m no programmer. Messing with actual code could get me in a lot of trouble. Is there an easier way? WordPress has tons of Plugins to make things like this simple. I can’t find much in the way of Plugins for BBPress.

[Ipstenu (Mika Epstein)]

That’s just adding in the link in your theme.

Seriously You can edit your header.php to have this, no plugins needed.

[Jason Giedymin]

Running:

WPMU + Latest RC of BBPress, User tables integrated, v1 of Integration Plug (on wp side) installed. Latest RC of bbpress was installed directory fresh but over an existing bbpress 9.x (latest stable) tables.

Tests Passed:

– Logging into each site individually works fine. Can’t log out without errors (understandably as there is a cookie issue see below).

Tests Failed:

– Log into bb-press via https

– Log into wp blog.

– Should go to Admin.

Debug:

– Stepped through to find wp was looking for “wordpress_sec_[long hash string]” cookie. Thinking it was ‘mal formed’ it redirects to the wp login.

Question:

– Why would the “wordpress_sec” cookie not be created by bb_press?

I will be stepping through the bbpress code but wanted to put a heads up in the forums if maybe someone already knows whats going on.

Btw Is there a developer forum?

[thekmen]

If you are willing to look at the source after the first post is added, you could add styles to suit that post to your css.

something like:

#thread #post-3 .threadpost { background: #7CFC00; }

#thread #post-3 .threadauthor img { display:none }

#thread #post-3 .threadauthor { background: url(images/question.jpg)  no-repeat 0 0;  width: 80px;

height: 80px; }

should work ok for that page.

other than that, i’m sure you could find a jQuery solution to find the first post in a thread & style it.

[michael3185]

I think there’s a missing check for the count..? I put a counter in my frontpage.php to limit the number of recent posts which are displayed;

<?php $recent_count = 0; ?>

<?php if ( $topics || $super_stickies ) : ?>

<h4><?php _e('Recent Posts'); ?></h4>

<table id="latest">

<?php if ( $stickies ) : foreach ( $stickies as $topic ) : ?>

<?php if ($recent_count >= 10) { break; } ?>

<?php $recent_count++; ?>

<tr<?php topic_class(); ?>>

<td><a href="<?php topic_link(); ?>"><?php topic_title(); ?></a><br /><div class="hints"><?php topic_posts(); ?> posts. <?php topic_last_poster(); ?> posted <a href="<?php topic_last_post_link(); ?>"><?php topic_time(); ?></a> ago.</div></td>

</tr>

<?php endforeach; endif; ?>

the $recent_count variable is incremented for each post link, and the loop is jumped out of if it hits 10. No doubt there’s a neater way of doing it, but it works fine. Checking for 1 instead of 10 would do it for you.

[lemonade-joe]

Thanks for the answer. Maybe I am doing something wrong, but after I insert the code into the topic.php, I only get a blank screen. No error messages, only blank screen.

[frooyo]

In 1.0 RC, it appears I need to have the users select the “forum” or “category” for their new post to be tied too.

However, I only have 1 forum – so in my post-form.php template, I removed the following code which produces the dropdown list (since only 1 value is selected).

<label for=”forum_id”>Category:

<?php bb_new_topic_forum_dropdown(); ?>

</label>

But now, when I try to add a post – I receive an error message that says “This topic has been closed”.

Any idea how I can force all new post into the only forum I have setup … so that I don’t have to display the “category” dropdown menu which only has 1 item listed.