[_ck_]

The problem is every website has different needs.

Some have only 10 visitors a day but the site operator wants every feature including the kitchen sink. They don’t care if it takes several seconds for their page to render as long a they have every fancy feature available and they can just use wp-super-cache to deal with the load.

But other sites have thousands of visitors a day and when a page takes too much cpu time or mysql time to render, then you multiply that by hundreds of simultaneous connections. Then you fail and your host kicks you off or you have to buy a bigger server.

WordPress started lean and mean, 1.5 was good, 2.0-2.1 was a great product. Then they started throwing in the kitchen sink. Then with every next release started breaking compatibility with every release, changing cookies, changing admin structure. 3.0 is a scary creature indeed.

There is no doubt in my mind that a bbPress plugin under WordPress is going to require 1 megabyte of code executing per instance with plugins in a realistic environment. The site operator with 10 visitors per day won’t care because they have every feature the could want in one package. The operator with an active, growing user based is going to have to constantly upgrade their server to handle the problem.

Active forums don’t deal well with caching, unlike blogs.

Blogs are write once, read many times.

Forums are write many times, read many times.

Different environment, different needs.

But performance should always be designed into software.

[Rich Pedley]

[edit: thanks for the feedback ]

Yeah, the option settings is a pain, they finally added that into WordPress, so I’m hoping it’ll be added into bbPress as well at some point. I copied the form from akismet, thought that way I’d get it right first time

And yes I did use that, nice starting point – hadn’t realised what was being passed to the trusted (must have missed that part). So yeah that’s trivial enough to add in.

One reason I didn’t add in the trusted was that I totally missed it after intending to put it in! This was due to my not being able to add a user profile field in the form of a select. So I’ll re visit that and see if I can utilise radio buttons instead.

Wasn’t sure what post_status were… so is it:

0 for standard posts, 1 for deleted and 2 for spam ?

I’ll work on it …

I’ve released a few WordPress plugins (and have loads of small unreleased ones), I’m not saying I’m good, but have experience. Plus it is why I have moved back to bbPress after years of using other forums, I should be able to code plugins for it!

[k.fallman]

I didnt know WP loaded everything, thought it was built smarter than that. Anyway, how much is everything ? 1 sec more wait ? is it acceptable for mainstream users ? The only thing i care the most of is a 100% user integration / login, but it could maybe be solved by a “addon” betwen WP & bbPress ?

[_ck_]

Very nice! Welcome to the world of bbPress plugin authorship!

I see you jumped on my suggestion from the other day about trusted users.

Isn’t it crazy how it just takes 10 lines to do the actual process but 100 more for the admin menu? This is why I hate admin menus, lol.

Some performance pointers:

Scanning the table for the user post count is non-trivial (you can only use one index at a time in mysql and you are already using poster_id and post_status so there’s a scan somewhere). So once you know to trust the user (unless they are set to “never trust”) might as well save that in meta and let them by the next time without a scan.

Also, you don’t appear to be looking at the already trusted status being given to the filter. If $trusted is already set true, don’t even bother with the rest as it’s probably admin or mods.

Here’s a feature idea:

instead of just counting post_status=0, why not gather the counts for all the status

$bbdb->get_results("SELECT post_status,count(*) as count FROM $bbdb->posts WHERE poster_id = $user_id GROUP BY post_status ORDER BY post_status");

Then you’ll know status 0, 1 and 2

2 should be empty, not even set for virtually any approved user.

If they have one, or more than one post status 2, then they should not be trusted.

Optionally they have a very high status 1 count in comparison to 0, something is up with that because it’s a bunch of deleted posts, so maybe not trust them either.

ps. another trick I use it to check if the user can ‘throttle’. If they can, they are already trusted in a sense because they are being allowed to post as fast as they want.

pps. Don’t forget you can also examine the membership age of the user, here’s a hint, it’s in user_registered

floor((time()-bb_gmtstrtotime( $user->user_registered ))/86400)

should be the age in days

[Rich Pedley]

elf Akismet download link.

Adds an extra settings page to enter a numeric value for number of posts before a user is considered trusted. After which they will no longer be checked by akismet.

A field is also added to the edit profile page for you, setting this will ensure akismet always checks them.

My first bbPress plugin, so I’d appreciate feedback.

[Rich Pedley]

Looking back at WordPress it look like it may not have been added into bbPress as yet. Ahh well one page for one setting is bit OTT but looks like I’ll have to stay with that for now.

[_ck_]

paulhawke, there is nothing “clean” about wordpress design. The code may have been cleaned up over time, but the result after 5+ years is there is a ton of code.

But the critical part is it loads EVERYTHING, regardless of the task at hand, all functions, all options, all plugins. Only the admin area is excluded from the load. But even the admin functions in plugins are loaded because there is no api structure to load those portions only in admin. (I’ve attempted to address that last problem in some of my later plugins for bbPress).

Loading a bbPress page as a plugin for WordPress will require the same process, EVERYTHING has to load, but now it will be worse.

This is why caching is critical with WordPress or it gets slaughtered when there are many requests. As soon as bbPress 1.0 was retooled to use backpress, it inherited the same problems as WordPress.

bbPress as a plugin will have the same problems as with backpress, but now even more so as all the wordpress plugins are loaded. It’s deep integration regardless if the user wants it or not. You will not be able to use bbPress functions without all of WordPress loaded because it will be substituting for backpress.

It’s forced deep integration, easiest way to explain it, and that’s a very bad idea.

[paulhawke]

I’m running into an issue writing the “import” side of things – my first thought is to create a plugin that mimics what is in WordPress. I found myself creating the infrastructure that is already present in the main body of WP.

Writing both import and export tool really would be a lot simpler when bbPress is a WordPress plugin. Why make it like the WP one, when we can utilize the real one?

[paulhawke]

Coming at this as a software engineering problem I cant see why a both/and rather than either/or situation shouldn’t prevail. Let me explain, as it’s not particularly outside the box for it to happen.

I write a lot of automated tests for the code I produce day-to-day and that means I need to isolate the most important pieces of business logic from how they are invoked. For instance, a given request comes into the a webservice telling it to create a user for the system. I would separate the code that handles the webservice part (pulling parameter data from the incoming HTTP request, etc) from the code that then creates the user. I would isolate the steps, wrap automated unit tests around each, and be done.

Applying the same thing to bbPress, there is some core code that handles the management of forums containing topics, that contain posts by users. This code is packaged into a clean unit of deployment – the WordPress plugin – and there is absolutely no reason why the code shouldn’t also have a second wrapper that allows for its deployment stand-alone from the main body of a WordPress installation.

Just as I might have a webservice making calls to a body of well-tested code in my day-job, I dont see why a cleanly written WordPress plugin shouldn’t make calls into the tested bbPress core code. The body of WordPress code provides additional services that another wrapper could also provide – the core of bbPress should be unaware of the actual physical storage mechanisms being employed, or how it’s being invoked (assuming its written correctly).

At the end of the day the conversion to a WordPress plugin should bring health to the codebase – a level of focus on what is most important (managing structured conversations in a forum/topic format), and an abstraction from what is not important (that is, the underlying physical storage, web-hosting, etc).

[k.fallman]

Interesting reply here

http://weblogtoolscollection.com/archives/2009/12/11/bbpress-lives/#comment-1321795

[Tellyworth]

Howdy,

It looks like the Live Comment Preview causes unexpected API calls to Akismet – a separate API call each time the preview updates (i.e. almost every keystroke).

I assume this happens because the preview plugin calls the pre_post filter, which in turn triggers bb_ksd_check_post().

I imagine there may be other plugins that cause a similar problem. Would like to help fix it but I have only a superficial understanding of the bbPress code. Suggestions for the Right Way to do it?

[k.fallman]

I think bbpress should be available as both a plugin and standalone forum. There are so many WP users who is only missing a forum part to their blogs, and remove bbpress as their best option, now when its getting better & better to integrate with WP, would make a lot of people sad ( including me ).

If bbPress have a plugin / standalone installer – it will rule !

[circuit]

I have just posted about this. Exactly the same thing. Sudden error, no change, users getting 404s when posting links. I also use that plugin but I hear this is happening when posting all links. I can’t really check it right now as I’m away from home.

Please let me know if you have any ideas, this is really really bad news.

https://bbpress.org/forums/topic/suddenly-getting-404-errors-on-bb-postphp-bb-editphp

[zaerl]

So will your plugin be compatible with bbPress 1.03 or is there another solution already integrated in bbPress 1.03?

My plugin works in 1.0.2 which is the official release. When the new bbPress will come (it’s in alpha stage right now) I will update it if necessary. Given what I have seen it will work at 99% without changes. At least if devs don’t add a ‘/post/*’ rewrite rule.

Will my old anchor-links stop working after activating your plugin?

Yes. That are just links. I don’t modify any template function but I just add another way of addressing the posts. Obviously if you deactivate the plugin all the posts permalinks will spawn a 404.

[_ck_]

MT made me learn perl and practically got brain damage from it back in 2003.

Then MT pulled that nonsense in 2004 and I jumped ship like so many others.

In hindsight MT did me a huge favor.

Best wishes to vbulletin users, I hope we can come up with a smoother conversion method for them.

[_ck_]

If you have id 1 you can use my fix-admin-access plugin.

But any user id can be made keymaster.

Might not just be delayed email, might be blocked by any number of antispam devices by accident.

If you can, try an email address that would be served directly by the server itself – though I have found gmail is pretty darn smart about not blocking most emails (hotmail is the worst).

[tanmccuin]

I’ve been using the BBvideo plugin for a couple years now, haven’t changed anything in my site recently, though i did do some work in the site route (not the bbpress folder.)

this morning a user told me that when they try’d to post a vid, they got the following error.

Forbidden

You don’t have permission to access /discuss/bb-post.php on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

even if i’m logged in as admin, i still get the forbidden.

2 things. all the vids previously uploaded, still show up (IE, the link, gets converted to an embed vid.) so the plugin seems to be working… and if i disable it, but still paste in a link to say http://www.youtube.com/watch?v=IYsTV2C9zaM, even though the plugin is disabled, it still spits back a forbidden error. Yet, if i just write in random text, without a link reference… it posts fine.

Completely baffled.

Thoughts?

[Tomcraft1980]

damn.

So will your plugin be compatible with bbPress 1.03 or is there another solution already integrated in bbPress 1.03?

Will my old anchor-links stop working after activating your plugin?

Best regards

Tom

[John78_98]

Hi,

In the forums page, I want to create a map and if user click on a particular region, then it should lead into the forums for that region. Let’s say I have four different regions.

I know this is a wild dream. Can I even setup something like this using bbpress and wordpress combination?

Thanks

[circuit]

you may need to change all usernames to lowercase so that both mu and bbpress accept them. i remember doing that when i upgraded.

[Rich Pedley]

aye looks like several instances.

[circuit]

a-ha.

When the WordPress ‘bbPress Integration’ plugin is upgraded it wipes all the options from the plugin.

Will resolve and leave open in case anyone else gets this problem.

[circuit]

our forum is here:

http://www.copsandrobbers.net/messageboard/

It has been working fine for about a year. Yesterday I removed a few plugins relating to ping.fm on the WPMU side which shouldn’t affect anything in bbpress (although you never know…)

Now users are reporting that they can post, reply but the second reply fails with a 404.

They also cannot edit the post.

I have checked via FTP and both of these files are present:

http://www.copsandrobbers.net/messageboard/bb-edit.php

http://www.copsandrobbers.net/messageboard/bb-post.php

Any help would be appreciated

Please feel free to log in and post on the test thread.

[_ck_]

Hmm, my font-size increase trick is no longer working, someone changed the stylesheet.

The default font-size is ridiculously small.

Did someone seriously hard code the font-sizes into PX instead of percent or em?

Ah this will fix it in Stylish

* {font-size:98% !important;}

[_ck_]

Here is the bbPress discussion from the Q&A session after Matt’s keynote at WordCamp

http://bbshowcase.org/forums/topic/347