[Billy Wilcosky]

I hate it when something so easy is giving me problems. I have a link to my search page… mysite.com/myforum/search.php… like that. And it works fine, except the font color on the search form itself is a gray or reddish color and it doesn’t go with my dark blue layout… I need the font to be white. With CSS I’ve got the font set to white everywhere else, even the search results are white, but the form itself is not so you can barely read it.

I’ve tried editing the color with CSS, regular html, I’ve been in my search.php in my forum root and my search.php in my template, and I’ve been in my search-form.php file, and no matter what I do… I can only get the font to change in firefox… for some reason in ie6, which should be illegal to use, the font it not white.

I simply added <font color=”white”></font> to the form, and again, it works in firefox, but when I test it with ie6 it doesn’t work. Why?

I even tried adding a new div… I added <div id=”searchcolor”>search form code here</div> then in my CSS file I have #searchcolor {color:white;}, but even that doesn’t work. Nothing seems to change the form font color in ie6.

This is frustrating because it’s something SO simple! Font color!

[swaymedia]

I want to get the latest version, but I was wondering what would actually go wrong with it.

I mean dont you just develope it further from 0.9 which was stable…. so.. it should be fine. i mean what could go wrong with it?

[wendel-brume]

It appears that the ‘deep integration’ between bbPress and WordPress will provide the basis for doing this, I’d need to be able to re-code the registration screen to make the ‘occupation’ field a required field. I also want it to be coded so it’s a dropdown list of choices that I determine.

This issue is way huge for anyone wanting to monetize a website through advertising. Advertisers on the web want to know who your audience is before they will pay reasonable CPMs. I’m showing videos that will eventually incorporate ads, and I want the site to know how to identify a registered visitor so that the video ads can be targeted based on their self-identified occupation.

I also need the forum to be incorporated into a WordPress page, the way I have a test of Simple:Press set up here:

http://architecturecartoon.com/forum/

Is there a relatively simple way to make bbPress look like that?

[batesy]

Hey guys,

I just installed bbpress at http://www.halifamous.com/staff for writers of a new blog to discuss ideas for the site. I am able to view the main forum page, and get into the admin section. The problem is that I’m getting a blank page any time I try to click through to the test post or into the ‘Introductions’ forum section I created. I also get a blank page when I try to access my user profile.

I haven’t touched the code. Any idea why this might be happening?

Thanks,

Greg

[_ck_]

This is a quick and dirty security fix. Only tested on a basic level.

This code is for the original, not detective’s mod which I will examine tomorrow unless Detective wants to apply the stuff below himself…

replace around line 100 the entire function pm_new_message

from:

function pm_new_message( $id_receiver, $id_sender, $pmtitle, $message ){

...

}

to this:

function pm_new_message( $id_receiver, $id_sender, $pmtitle, $message ){

global $bbdb, $bb_table_prefix;



$created_on = bb_current_time('mysql');

$id_receiver = intval($id_receiver);

$id_sender = intval($id_sender);



$pmtitle=substr(strip_tags($pmtitle),0,64);

remove_filter('pre_post', 'post_regulation');

$message=substr($message,0,2048);

$message=force_balance_tags($message);

$message=apply_filters('pre_post',$message,0,0);

$message=apply_filters('post_text',$message,0);



$pmtitle=mysql_real_escape_string($pmtitle);

$message=mysql_real_escape_string($message);



$bbdb->query("INSERT INTO ".$bb_table_prefix."privatemessages

(id_sender, id_receiver, pmtitle, message, created_on)

VALUES

('$id_sender', '$id_receiver', '$pmtitle',  '$message','$created_on')");

}

This patch should in theory make it virtually completely sanitized (but still not completely validated unfortunately) and has the added bonus that most other plugins that affect posts like bb-smilies, etc. should work inside PM’s

[shinku]

I use the latest stable verson and doe not work for me. I think i finnaly i had to use the tinymce and have more secs loading it.

[chrishajer]

The latest stable bbPress (0.9.0.4) does not integrate nicely with WordPress 2.7.1.

What does line 14 of wp-blog-header.php look like?

[psheld]

Thanks Chris. My version of bbpress is the latest stable one at the time of writing: 0.9.0.4.

Just changed the secret key in both bb-config.php and wp-config.php to a 37 character long string of letters only, and we have success at http://www.atcv.net/bbpress . Awesome. Thanks v much.

But I get the following at my wordpress root http://www.atcv.net:

Fatal error: Call to undefined function wp() in /home/philipsh/public_html/wp-blog-header.php on line 14

so perhaps my integration with WordPress remains flawed?

[chrishajer]

Latest Alpha or latest stable? 0.9 series or the 1.0 Alpha series?

[swaymedia]

Hi,

In the latest version of BBPress, are the user roles/permissions well intergrated with the WP roles/permissions.. ?

[cldnails]

This is my first jump into bbPress and to be honest, I like the included template. So, I went ahead and used the included and am in the process of modifying it so it fits my needs.

Grayline bbPress Forum is for my automotive blog The-Grayline.com, so the theme is slightly modified to mimic my wordpress blog.

Mods:

Integrated Google Search

CARP Feed Parser for Updates on Blog in Lower Corner

Swapped Latest Posts w/ Forum Sections

The RSS feed for the blog in the bottom right has been floated to the right, so that when logged in the visitors information is displayed to the left and it all looks pretty. Please let me know what you guys think.

[deadlyhifi]

It’s probably slightly more complex than you think.

For each forum you’ll have to fetch the latest post and then its details. I’m not sure how to go about that. Maybe someone else can shed some light on it. Sorry…

[jpanizzoli]

Sorry if my original post was confusing. Let me clarify: I’m trying to add “Latest Poster” and “Freshness” to front-page.php – but include it in the main forum table – not in the latest discussion table. You can see it here:

www (dot) eco-wheelz (dot) com/forum/

You can see I’ve created the new columns, but I can’t get the appropriate information to display. I’m trying to include more data in the main table and only include new topics in the latest discussions…

[krischan68]

Thanks. I’ll give it a try on a test installation.

[superann]

You’re welcome, krischan68! You should be able to upgrade all the way to the current WP 2.7.1 as far as integration is concerned; I’ve tested this method on another site and have gotten it working.

I highly doubt the plugin will break with minor point releases; it wouldn’t make much sense for the dev team to make such drastic changes unnecessarily.

[Matias Ventura]

I just wanted to share the experience I have gathered while working, designing and pushing bbPress so as to not look like a generic bbPress instance. My latest work are these forums (the rest of the site is WordPress), and if you have the time please consider registering to be able to play a bit with the design from a member-perspective (enjoyed better in Safari). I would appreciate your feedback.

I am really captivated by the possibilities bbPress offers; but I also feel the obscurity of these possibilities are somehow hindering proper development in the design department. The lack of a proper and exhaustive codex, readable for theme authors —without having to dig into core files—, remains as the biggest obstacle. I am all for contributing, should it be possible, in this way or another.

[inkey]

I’ve installed bbPress 1.0.6. alpha and integrate it with WordPress 2.7.1. Everything is fine.

But there is one big problem:

When user with IE is registered, he can use forum for 2 or 3 days, after that he cannot open no one topic. After User is log in and click on topic link page loads and there is error pop-up, that says (translated to English):

Can not load page –there is url to topic page–

Operation aborted

With “OK” button.

After clicking “OK” there is IE page, that says “Internet Explorer can not view this page”.

In Firefox, Chrome, K-Meleon and Opera everything is fine.

You can test it on: http://oakdaily.ru/forum

Sorry for my English.

[_ck_]

It’s strange that I didn’t think to downgrade WP 2.7 to match bbPress 0.9 but I guess I overthought the process and figured the new “auth” cookie method would be required in the admin area on WP so it would break. I assume you have tested your admin access in WordPress after your changes?

WordPress 2.7 added three new kinds of cookies, surprised it doesn’t break anything when you force it backwards. Did you delete all of your old cookies on your browser to make sure it wasn’t “cheating” ?

In any case, my new plugin is here and should be downloadable for testing shortly:

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

One plus to the WP downgrade method is it might work with deep integration where mine will definitely not work and should not even be tried that way.

[superann]

Yep, same method above works with WP 2.7.1 and bbPress 0.9.0.4. Just tested and there’s full cookie integration.

[jpanizzoli]

I’m trying to combine some of the functions in the “Latest Discussions” table with the main “Forums” table. I’d like to include the “Latest Poster” and “Freshness” to my forums section. So far, I’ve successfully displayed these items within the table, but they’re not showing the appropriate data. Instead, I’m getting only the most recent poster and freshness displayed for every forum. This should help clarify:

www (dot) eco-wheelz (dot) com/forum

This is the code:

<table id="forumlist">

<tr>

<th><?php _e(‘Main Categories’); ?></th>

<th><?php _e(‘Topics’); ?></th>

<th><?php _e(‘Posts’); ?></th>

<th><?php _e(‘Last Poster’); ?></th>

<th><?php _e(‘Freshness’); ?></th>

</tr>

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

<?php while ( bb_forum() ) : ?>

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

<td><?php bb_forum_pad( ‘<div class=”nest”>’ ); ?>“><b><font color=”#339900”><?php forum_name(); ?></font></b><small><?php forum_description(); ?></small><?php bb_forum_pad( ‘</div>’ ); ?></td>

<td class=”num”><?php forum_topics(); ?></td>

<td class=”num”><?php forum_posts(); ?></td>

<td class=”num”><?php topic_last_poster(); ?></td>

<td class=”num”>“>

<?php topic_time(); ?></td>

</tr>

<?php endwhile; ?>

<?php endforeach; endif; // $topics ?>

</table>

THANKS FOR YOUR HELP!

[frooyo]

To help get more people actively involved, why doesn’t bbPress host a “bug fixing marathon weekend” and offer a prize to the most bugs fixed within a 48 hour period.

Or a contest to redesign the web site.

Or a contest to improve the documentation.

Just trying to come up with ideas to help.

[_ck_]

The news about bbPress on that blog is just rehashing news elsewhere (and it’s a month out of date at that). 2009 will indeed be a big year for *development* for bbPress 1.0 – but that doesn’t mean 1.0 should be adopted for use on live sites in 2009.

I don’t know how to explain it any further that 1.0 is not simply a continuance of 0.9, it’s about 50% rewritten. 0.9 was reaching a certain maturity but now virtually every major function has been changed in some way that makes it more complex (for the same functionality).

You’re not using code in 1.0 that’s been proven stable in 0.9, you are using code that’s been rewritten to mimic the functionality of 0.9 with complexity added to force the use of BackPress (essentially WordPress core functions). Not only does the added bulk slow things down, but it degrades the proven stability that was in 0.9 because the new code is not thoroughly tested.

You shouldn’t be nagging about 1.0 over here, the key question you should be nagging developers about is over on the WordPress side: When will WordPress use BackPress? If it’s not going to (anytime soon) what was the point in rushing to break a stabilized bbPress to make it use Backpress and why are people rushing to use bbPress 1.0 when it’s not finished?

I think there was only one problem: it’s that 0.9 never got support for the cookies in WP 2.7 so way too many people rushed to 1.0 despite heavy warnings not to do so, somehow thinking they know better, or worse, that they’d just nag about any problems they have and get some kind of priority fix.

I am considering releasing a plugin to make 0.9 work with WP 2.6-2.8 cookies to stop this nonsense once and for all however people still won’t be able to downgrade unless I also make another plugin to downgrade the database also. But it’s a lot of work and I have little motivation since I would never use WP 2.7+ myself.

[Ipstenu (Mika Epstein)]

@kevinjohngallagher – I got it from the horse’s mouth. She posted it on her blog and in her Blog Herald post last Friday.

WordPress News, scroll down to bbPress On Fire.

And yeah, the ‘follow the blog’ was partly tongue-in-cheek (I know updates are sparse), but also serious (as it is the best place to get ‘this has changed’ news). The blog will be updated when there’s news to update. And if there are long gaps between posts, well, it’s not a dev-blog. The forums are kind of the dev blog right now.

[kevinjohngallagher]

I write this in response to the growing posts and their ever-increasing angrier responses from moderators, to people who are simply asking for clarification of (mis-)information.

The problem we have, as a community, is that we have no communication nor project management involved with BBpress.

COMMUNICATION

A great example would be:

How many more ALPHA’s before BETA?

_ck_ rightly points out, and then gets angry at the poster, people are constantly asking the same questions. The bit _ck_ misses is that they are not pointless to a lot of people, or indeed one person, even if they are pointless to her. The point that hasn’t seen to be grasped by Sam/Moderators is that have an external facing Trac website that says one thing, when another is true, which is why people are asking the same questions over and over.

Instead of getting angry at people, why not change the date on Trac?? Even if you put it at 1st Jan 2010, it’s at least in the future and closer to being realistic than 1.0Beta 2 months ago.

I brought this up in October, and then again in December, and now again in February, but people who are new to this project or maybe not as involved ask _ck_ get their information from the website; but this info has been wrong for over 5 months. Which is why people are asking for clarification!

If you give people wrong/bad/out of date information, you have to accept that they will ask questions about it on the forum. It’s been the nature of humans throughout history, and we’re not going to change simply because it’s BBpress (sadly).

Given that the issue could be fixed by a BBpress person (not sure about user roles here so don’t want to presume that a forum mod could do it or if we need to wait for Sam); maybe we should stop being rude to people and fix it?

<u>A further example:</u>

It’s great that _ck_ knows that alpha 7 will break her plugins; but what about everyone else? Where is the blog post? Where is the forum post by Sam? Where is the sticky? Where is the announcement? Etc.

After much searching it turns out that 3 weeks ago _ck_ made a post about it, which has been off the front page of the forums section for the last 15 days. Brilliantly meaning that if you didn’t read the BBpress forums for a 5 day period at the start of February for any reason, then you won’t know about these massive changes. At the risk of appearing sarcastic, does anyone else think that maybe this should be the sort of thing we should Sticky/announce/keep on front page? Shouldn’t this sort of thing come from Sam?

But regardless it just re-emphasises the fact that communication about BBpress is close to non-existant.

TRAC

Devs and Moderators tell us to use Trac, and then are surprised that people are confused about the roadmap saying that Beta comes out 01/08/08 .

Either update Trac so that people don’t get confused, or inform people in some another way (which is a little redundant as that is what the Trac roadmap is for).

PROJECT MANAGEMENT

It somewhat goes hand in hand with the communication aspect, but as any developer knows, rushing head first into coding with no long term view quickly becomes fruitless.

As a community, and i’m in no way saying that Sam answers to us (really want to make that clear), we have no freaking idea what the heck is going on at any given time. We’re either given an ever changing answer by a moderator, or we’re told that Sam will tell us (like the voice behind the curtain), or we’re left with the (wrong) info on the website.

Every change comes out of no-where.

We have no idea what the short, medium and long terms goals are.

As much as this software is ‘free’, anyone planning to use it on a website at least wants to plan a little in advance.

It’s very difficult to want to help/take pride/give back to an open source project when we’re constantly told “it’s ready when it’s ready stop asking” – and in fact shows a total lack of project management and control.

Who runs the BBpress project?

Do they know/can they answer:

– how many scheduled man hours until alpha 7?

– are people assigned to work on it, or have they been moved elsewhere?

– what is the testing time on alpha 7?

– how long and we holding open bug acceptance for alpha 7?

– what is the due date for alpha 7?

– what is the likelihood of hitting that date?

– what are the dependant factors?

– what impact does alpha 7 have on existing installations?

– have the testers been informed of this?

– have the contributors been informed of this?

– what potential conflicts are there between current versions and alpha 7?

I’m not specifically looking for answers btw, as I said before Sam doesn’t answer to us, but I’m not sure I believe that ANYONE related with this project can answer those questions, and that is really really worrying.

IT IS FREE – THEREFORE IT IS OK.

Free is good, free we like.

Free means we accept bugs.

Free means we accept it’s not ideal.

Free means we know we wont get a 100% fit to what we need.

Free doesn’t mean we accept no communication.

Free doesn’t mean we accept what communication we get being wrong.

Free doesn’t mean we accept no management.

Free doesn’t mean we should get slapped down for asking perfectly legitimate and reasonable questions.

Free doesn’t mean we should accept instant yet wide sweeping changes.

Free doesn’t mean we should accept a total lack of respect.

AUTOMATTIC IS NOT A COMMERCIAL COMPANY

It is.

No, really… it is, so can we please stop saying that it’s not. Sam, while a loveable rogue to be sure (and he’s very cute in his picture), he is not fucking Ghandi – he does this for a wage.

Automattic is not building BBpress out of the goodness of their hearts to save all the wee orphans of the world, they’re a company making a profit and paying people’s wages.

Lets drop the humanitarian line when someone makes a good point and the moderators want to slap it down, eh? Or am I wrong, is BBpress ending world hunger as we speak? No? ok, maybe lets stop this one then. Just a thought.

HOW TO FIX THIS.

At the risk of opening up an old wound, I made a list at Christmas time (the oh so fun Facebook thread).

Either pause development on BBpress 1.0alpha7 for a week, or engage someone else to do it but:

<u>Fix the website. </u> Seriously, spend time going through each static page (there are 20 of them) removing all the bogus/wrong/out of date information. Some pages are fine, some are really really out of date. Given how much has changed with BBpress since WP2.5 came out, if you haven’t updated a page since that time then you know it’s wrong before reading.

<u>Blog more. </u> Not in a twitter “I am eating an apple” way, but you’ve made 5 posts in over 6 months (and 3 of them were within 3 days of each other). That development blog is our window into the BBpress development. It says “hey, this project ain’t dead”; instead all it does now is say “we released this bit of software on this date”. It’s not a blog, there’s no info other than release dates of software that don’t work anymore (for the most part).

<u>Extend / Plugin section. </u> This drastically needs an overhaul. There needs to be an option to filter out plugins that either don’t work or haven’t been updated to the latest release. Lets be honest, some of these plugins are 2 years old, and as soon as you click into them that’s the first stat you see.

<u>Download section. </u> Kinda/probably/should/maybe say that if you download the latest version it won’t work with a wordpress install form the last 9 months. Even though it’s from the same company. And it says it does work in the About page. And says it again on the Integration page. Yeah, we should probably write the truth somewhere or people will keep asking…

<u>Trac. </u> Lets update Trac. If someone has an understanding of the project to the level that they can answer the Project Manager 101 questions above, then why not put some of that info into Trac? I’m confident (though it’s just my opinion) that people are more motivated to fix bugs if we know there are X outstanding before the next alpha, rather than a huge list that has be fixed in an unknown amount of time.

<u>Development documentation. </u> A tough one this, and time consuming. I get that, I really do. But it makes helping out really difficult. As someone with rusty PHP coding skills (I‘ve been a BA far too long), I find Navigating bbpress to be a pain, and while I understand wordpress comparisons aren’t favourable, documentation makes wordpress editing 1000 times easier.

<u>Give us an overview. </u> Sounds very simple, and most PM’s have an overview list for each project anyway (usually on a power point to fob directors off), but it would make life easier. Many of us still don’t know what ‘features’ are standard with BBpress and which will only be available via plugin. Many of us don’t know what features are intended on being added, or what direction BBpress is going to go in. These aren’t bugs, we can’t add them to Trac, but many good points have been raised on these forums in the past – and I don’t think it’s right of us to assume you missed them or have ignore them, simply because there’s no communication.

Last bug not least…

Any chance we could have a reigning in chat with some Moderators? It’s great that they give up their time to reply here, and help the community, but (and I don’t know if it’s just someone having a bad day) the comments are getting way more aggressive/argumentative/absolutist.

It’s not that the standard answers aren’t wearing thin ofc, it’s just that we know the answer is going to be:

• It’s free.
• Sam’s too busy to pass on info.
• Blame Matt.
• It’s free.
• Stop asking. It’ll be ready when it’s ready.
• It’s free.
• Automattic are here to save us all and do not make any moey at all ever and everyone works for free I loves them – please ignore the $29 million they got which included the development of BBpress in the pitch.
• Go to trac.
• Don’t believe Trac.
• Sam’s too busy to keep you lot updated.
• Microsoft.
• It’s free.

That’s said a little tongue in cheek, and I hope it caused no offence, but while the moderators are clearly trying to do a great job (and we thank them), rarely do we get answers or constructive conversation when we talk about things like this. We’re shot down very quickly that we dared to have a different view point, and then given one of the standard answers that blame someone else or that it’s free.

WE WANT TO HELP.

Anyone who takes the time to hang around this forum sees we want to help. Anyone who takes the time to write on the forum wants to support BBpress.

If you’re the only developer on BBpress, or the person making almost all of the plugins, or the moderator who slams anyone who asks a question: please let us help.

We can’t just rock up, roll up our sleeves and stick our hand up a cow’s butt (an old farming joke – sorry). We need some direction, we need to be able to ask questions, we need information. Once we know what stage BBpress is at, we can help in taking it forward – with you.

But right now, all we can do is right posts like these every 2 months.

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