[_ck_]

Sam please break whatever you feel is necessary in the core to make things work better in logic, and not worry about backwards compatibility. Broken is broken in my book and I’m still going to delay doing anything until 1.0 is final (and the 1.0.1 bug fixes are sketched out)

I’d rather you break in any way needed for the right reasons and not be saddled with backwards compatibility like WordPress did (and look at what a mess it’s become).

For what my opinion is worth, I’d rather you not call it beta until it’s production ready because you just know that hundreds, if not thousands, will jump on anything labelled beta and expect it to work near perfectly, as well as any plugins they currently use.

Heck if the alpha numbers have to go into triple digits, let it be, at least the people who need to feel there is constant progress will feel better as the numbers get bigger.

Last but not least I think there should be an incredibly strong warning to people that there is no downgrading from 1.0 to 0.9 once they upgrade because of the db changes.

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

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

[_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)

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

[_ck_]

Let’s put it this way, if you have decent income from a forum of that size, you should not waste another minute your time (or anyone else’s) and just pay for vbulletin and the extra hardware it will need at that size (dedicated mysql and email servers). Seriously, it’s the best for a reason, but you will have to pay for everything once you go down that path, addons, etc.

If you are trying to cut corners and do it on the cheap, bbPress 0.9 is lightweight enough to handle it (wordpress.org has many times the traffic you do) though a dedicated mysql server can always help, and keep in mind bbPress has no caching plugins available yet. The money you save will be spent in hours of customization and tuning and creating your own fixes for problems.

You can always turn to lighttpd or nginx if you know your stuff and have days to fiddle with it or the almost instant installing litespeed, if you want an apache replacement that will double the capacity of your server.

The only cloud on the horizon is bbPress 1.0 as I estimate it in some cases will be roughly 30-50% slower than 0.9 (with still no caching plugins) and at this time roughly half of my plugins will not work with it (and won’t for quite some time, assume the end of 2009 at the soonest).

After 1.0 stabilizes and someone ports WP Super Cache to it, that will change the picture again but that kind of caching only helps visitors that aren’t logged in.

Oh and bbPress isn’t going to solve your search problems. It will only make it worse. bbPress’s search is completely non-indexed, and has virtual no options. My Super Search plugin might eventually cache searches but that’s not going to solve the problem of 1000 users searching for different things at once. I mentioned http://sphinxsearch.com a few months back and amazingly they are now using it on wordpress.com so there is hope that one day there will be a plugin for wordpress/bbpress to use it for searches on larger sites which will completely solve the performance problem.

Your groups of forums will require bbPress 1.0 and the downside of that again is half the plugins for bbPress 0.9 will not work with it. If you do install 1.0, don’t install anything more than 1.0 alpha 5 to use with my plugins.

ps. the top 100 list hasn’t been updated in 90 days and many of those forums are much bigger now – next update will be sometime after Firefox 3.1 is released

[_ck_]

I once tried to make wp 2.7 cookies work with 0.9 but gave up.

I’ll might revisit it later this year – it’s definitely technically possible.

I still don’t understand WHY people want to run more

than WP 2.5 considering how insanely bloated it’s become

and I find the new menu system annoying.

[_ck_]

One final addition to this that I didn’t think of mentioning earlier.

To use bbPress queries like these on a foreign (non-bbPress / non-WordPress) PHP page, all you need to do is include the bbPress core like this at the start:

<?php require('/local-path-to-bbpress/bb-load.php'); ?>

or to load WordPress core use this

<?php require('/local-path-to-wordpress/wp-config.php'); ?>

(change the ‘local-path’ bit to your local path)

and remember to use $wpdb on WordPress pages, vs $bbdb on bbPress pages.

[_ck_]

Yup “order by rand()” is very handy.

I used it for a mod for WordPress years ago to make a “random” category which is very useful.

It could even be done to make a “random topics” view in bbPress but not sure how useful that would be.

It’s fine for casual use but keep in mind for larger tasks it’s very slow and makes mysql purists shudder.

[_ck_]

FYI, the if ($i <= 4) { is not needed because you already do a LIMIT on the query.

Related topic:

https://bbpress.org/forums/topic/heres-how-to-show-bbpress-info-inside-wordpress-without-full-integration

[_ck_]

It won’t have a special user agent, you’d have to detect the width via javascript but it’s not even necessary.

If you resize firefox to 800×600 it doesn’t do that for me, and I even have large fonts turned on.

So make sure your minimum font-size in firefox isn’t set too high, or your zoom level isn’t too high.

[_ck_]

Good fix, I got distracted after I posted that and never did it myself.

There’s also a border issue on images but I think most themes have that problem and it’s another thing I have to enforce in it’s own stylesheet.

actually, you are causing it here:

#posts .post .content a img {

border: 1px solid #ccc;

}

You may way to limit it to topic pages and not any kind of table like latest-discussions.

[_ck_]

Very well done.

Here’s a demo:

http://bbshowcase.org/forums/?bbtheme=toonewsy

You must have display:block on images inside the #latestdiscussions table.

I’ll have to put an override in the topic icons plugin.

[_ck_]

They are using the trunk which is why I didn’t bother to answer.

I officially do not support anything past 1.0 alpha 5 at this point.

I simply do not have the time anymore to fix for every 1.0 release.

I will resume updating after 1.0 goes beta final someday.

I may release a plugin to make bbPress 0.9 work with WP 2.7 cookies

at some future date to allow people to use more plugins without problems.

[_ck_]

Either sessions or your cookies (that the captcha uses) are broken.

[_ck_]

There are only minor changes from bbPress 0.9 templates to 1.0 templates – you will just not have a few minor features that are new in 1.0 with a bbPress 0.9 template. You might have to make only a couple of minor adjustments after upgrading.

However the reverse is not true – a 1.0 template will not work with 0.9 – it breaks a great deal of backward compatibility.

[_ck_]

Just an addition that there apparently are some subtle problem with some of my plugins even on 1.0a6

I intend to try to fix things up to at least 1.0a6 but any bug particular to an alpha is low priority.

[_ck_]

The spammers figured out how to defeat the old Human Test so I updated it:

https://bbpress.org/plugins/topic/human-test/

and I will be updating it again later this month to make it even harder

[_ck_]

This is like CSS 101.

On every page in kakumei, the width is controlled by #main which is 760px

Make a new wrapper that superceeds #main (wraps #main, not replace it) and in side that wrapper make #main float:left, then create a new div for the sidebar which floats right.

Then adjust the width of main and the sidebar as necessary to fit your desired page width.

header.php

#wrapper open (forced width 960px)

#sidebar (float:right: 150px)

sidebar content

close #sidebar

#main (float:left 760px)

blah blah

footer.php

close #main

close #wrapper

[_ck_]

I tried for a little while to figure out how they were doing it and realized they are just counting CSS markers. I also tried to find the right people in Google to talk to about this to no avail.

I think they would worry about blackhat SEOs manipulating this so they aren’t giving details.

bbPress clearly gives such meta info at the start of each topic, so unless someone radically changes their templates, it’s already in there.

[_ck_]

Yeah they do that for vbulletin and phpbb too, so I suspect it’s a problem they have to work out.

[_ck_]

Google is probably still sorting out the algorithm.

Because templates can be customized endlessly, it’s hard to find patterns sometimes.

You’ll notice it only appears on some topics, not all:

http://www.google.com/search?q=site%3Abbshowcase.org+inurl%3Atopic+copy

[_ck_]

The problem with VPS is the system will lie to you as far as how much CPU is available to you at any given time. MySQL being at 90% may be a symptom, not the cause.

You can have just one program running but if a neighbor on the same node is hogging the disk with heavy disk access, processes like MySQL which need fast disk access to respond timely will start to overload. There isn’t a single VPS that has decent disk I/O management.

What you can try to do is give MySQL as much ram as you can afford. Also take a look at how many queries your bbpress pages are using via my bb-benchmark plugin, make sure they are below two dozen.

There are specific tools you can monitor your VPS with that I highly recommend:

1. This one is a MUST so you can show your host that you have bad neighbors

http://www.silversoft.com/loadavg

2. This one takes a little more install time but is very helpful too:

http://www.labradordata.ca/home/13

3. last but not least you want a mysql monitor like MyTop

http://jeremy.zawodny.com/mysql/mytop/

Keep in mind, if you discover (via loadavg) that the load time of day happens at the EXACT same time every day (like on the hour at 9am) that means your host is doing something stupid like backing up all the VPS on the node at the same time instead of staggering it. Some VPS hosts are more experienced than others. Some hosts will argue with you that your neighbors can’t be affecting you on a VPS, in which case the host is ignorant or an idiot, or even worse, a liar.

Oh and if you don’t have a php opcode cache installed (you didn’t mention it one way or another) be sure to install one: eaccelerator, xcache or apc (eaccelerator recommended for ease of install and general compatibility)

If all else fails, replace Apache with Litespeed or lighttpd or get a better host.

[_ck_]

They didnt post what version they are using, it may be a 1.0a6 bug

[_ck_]

This will hide forum #5 and only allow keymaster,administrator, or moderator to see it.

$hidden_forums['hidden_forums']=array(5);	// hide these forums, list by comma seperated number



$hidden_forums['allow_roles']['all_forums']=array('keymaster');		// these roles can always see ALL forums regardless

$hidden_forums['allow_roles'][5]=array('administrator','moderator');	// exact formal role name, *not* ability