[chrishajer]

They’re included in the 1.0 branch. I suppose it depends on the template you use to display the avatar.

[Marius-]

I want BBPress to be a standalone program. But I want it to be possible to include it as a page in WordPress.

[Marius-]

Is Avatars integrated as basic functionality?

[Anonymous User]

I would love to see bbPress as a WordPress plugin.

[vpsBible]

well, I guess the title is sufficient!

any news gratefully etc, thank you.

[zaerl]

This is one of the most important thing of GPL (the famous “free as in freedom” and not “free as in free beer”.) http://www.gnu.org/philosophy/selling.html

[Gautam Gupta]

Please download the plugin again and upload it properly in the plugins directory. As you can see on the trac, there is an includes folder in the plugin – https://plugins-dev.bbpress.org/browser/after-the-deadline/tags/1.6

[Ryan Hellyer]

You are totally incorrect.

There is nothing in the GPL license which prohibits you from selling GPL licensed themes.

WordPress.org even has a page dedicated to promoting the sale of various GPL themes … https://wordpress.org/extend/themes/commercial/

[gerikg]

I found this:

http://phpxref.ftwr.co.uk/bbpress/nav.html?bb-plugins/bbxf/exporter-bbpress.php.source.html

Does do that help any coders?

and Sam’s post on the subject:

https://bbpress.org/forums/topic/exporting-bbpress-to-phpbb2#post-18830

[chrishajer]

I’m not sure why, but the fonts look fine and comparable to other sites here, for me. This is with Chrome 5 on Windows or Linux. FWIW.

CTRL+ takes care of font resize if I need it without any trouble. But I’ve never had to do that here.

Now THIS site has really small fonts on my system: http://faustltd.com/

For some reason design and architecture firms always seem to want those tiny fonts.

[k.fallman]

word .. i agree

[_ck_]

Don’t get me wrong, I am not against paid, premium themes for bbPress.

There are now a handful out there, which is a good sign.

But I want to point out something to a couple of the authors which I will not name at this time.

You should not start with an existing free theme that is GPL and modify it if you are going to sell it. (added: without making it GPL)

(edit: changed “cannot” to “should not”, moral vs legal)

GPL requires you to disclose the source if you are going to distribute derivative works. This means, for example, if you start with the kakumei theme and improve it, you cannot sell it to others. You can give it away and maybe charge for support, but in itself has to be free.

(But on the other hand, this does NOT mean you have to give away your work if you modify a theme for your own site. GPL cover that, it says if you don’t distribute, you don’t have to make source available.)

TL;DR If you are going to sell a theme, start from scratch, not another free theme or you’ll get in trouble eventually.

[kevinjohngallagher]

I think in the long run, that rather than porting bbPress to a WordPress plugin as a “straight port”, there will be a halfway house of using WP3.0’s custom post types and taxonomies. I’m guessing at this, but haven seen some attempts at this on the beta already, it seems to make alot of sense.

EDIT: found justin tadock’s example @ http://justintadlock.com/blog/wp-content/uploads/2010/04/forum-post-type.png

(sorry for the number of spelling mistakes, i simply can’t read these hideously small text they’ve forced on us by using font-size in pxels)

[kevinjohngallagher]

Wasn’t BBXF abandoned _ck_ ?

I’m going on memory rather than fact here (so am happy to be wrong), but wasn’t the last bbxf bit of code added before or around the time that bbPress0.9 came out?

It may still work (fingers crossed), but I’ve not seen anyone mention it here in a good 18 months.

[gerikg]

I noticed something with the WP integration setting in the bbP dasboard. When it’s filled out it uses the wp_user & wp_meta tables, when it’s not used it uses bb_user & bb_meta tables. If you started your bbp with the integration bb_users & bb_mate are never created. I don’t know if that information is useful. It’s something to think about because of people who have an existing bbpress and wants to add WP.

Check you tables in your SQL and see what’s listed under the bb_user & wp_user tables.

[gerikg]

Thanks you two, I forgot I asked this question before:

https://bbpress.org/forums/topic/anyone-used-bbpress-exporter-01a

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