[chrishajer]

Copy the register.php from the bb-templates/kakumei/ folder into your theme folder. If you don’t have a theme file present in your theme, the file from the default theme is used. Since that’s happening now, go ahead and copy the register.php into your theme folder and make the modifications there.

[nickaster]

Interesting… so assuming my templates were default… where would I look for the code to add this? I can get in there and add it if I knew what it looked like.

[Marius-]

Oh

I wish all us other users could have it like this.

I view this support forum as sort of the default showcase for what bbpress is.

[_ck_]

While the WP backend is “pretty”, in WP it has to be because users are exposed to it for some crazy reason, and of course it breaks with the entire default theme of the site.

How much time do you spend in the admin section, does pretty really matter?

bbPress (standalone) solved the admin menu problem with users by making advanced profiles. Unfortunately bbPress (plugin) will revert right back to the WP problem.

That said, the admin section could be much more disconnected from the main program anyway, so it can be developed by different people at a different rate with different theme possibilities.

It might even be possible to “theme” the admin section like the regular site theme.

[_ck_]

Yes you can, easily.

I have a mini-plugin for this somewhere around here…

Here you go:

<?php

/*

Plugin Name: Delete Own Post

*/

function delete_own_post($retvalue,$capability,$args) {return ($capability=='delete_post') ? bb_current_user_can('edit_post',$args[1]) : $retvalue;}

add_filter('bb_current_user_can','delete_own_post',10,3);

?>

Note that they can only delete for as long as they can edit.

Meaning after the 1 hour default, no more delete.

But you can change the timeout in the admin settings.

[WP Realty]

I’ve installed an integrated WordPress 3.0 (NOT MU) and the latest BBPress. When users register with WP they can not add any reply or start a new post in the forums.

I tested this with the default unaltered theme and same thing.

Looking in the DB I see that each member is a “member” in WP but there is no BB_METAUSERS table for bbpress. I think this isn’t required when an integrated solution is installed.

Any idea why all new members are set to “Inactive”?

J

[RedBull]

Hello _ck_, thanks for the reply. Unfortunately this option is not working for me.

My steps were….MKDIR>my-plugins/>new folder>custom-registraton-email.php>copy and paste the plugin you provided>activated>still getting the same registration default email.

[deadlyhifi]

The plugin is Add bbPress Default Role. It’s three lines of code so you may be better just writing it into your functions.php file.

[_ck_]

WordPress today cannot run a live site without caching.

You’ll get kicked off any shared hosting in a heartbeat.

This is a HUGE regression because there are times when a page cannot be cached. I was looking at mashable the other day – it uses over ONE HUNDRED AND FIFTY queries per page. It would be slaughtered without a super dooper amount of caching.

But bbPress 0.9 is fully capable of taking loads without any caching at all. I know of a few large sites that use it without any caching, it just doesn’t need it if properly configured until you get to slashdot level loads.

So in what fantasy world does anyone believe that adding the load of bbPress as a plugin to WordPress’s existing burden will ever make it faster than 0.9 ?

WP 3.0 already requires the increase of PHP’s default memory allocation per instance (over 32M in some cases). bbPress 0.9 runs in less than 1M (with a whole bunch of plugins at that).

If being more attractive to the WP masses was important, what should have been done is a project to make standalone bbPress’s integration with WP easier. Perhaps mimic WP’s template actions, etc. so WP templates could be used with less modification.

But like backPress, I’m afraid it’s probably too late.

I’m not saying this to be mean Matt, but the reality is Automattic is becoming a one-hit-wonder with everything being folded back into WordPress.

(and if a bbPress as plugin with WordPress backend goes down for any reason, failed upgrade, security hit, etc. now so will your forum)

[nickaster]

Is there a better option than gravatar for making avatars? I like gravatar, but most novice users still can’t figure it out. Also – are there better options for profiles in general? Are there plugins where people can add real information to their profile pages, not just the bbpress defaults? I don’t need much, just a little more than is there now, like a bio and whatnot.

[_ck_]

Oh wow. I’m an idiot.

Very sorry to put you through that – the version on bbpress.org is out of date!

It only does version 1, not version two.

I’ve just posted 0.0.4 which does version 2 (now set to default)

don’t forget to copy over the four define lines!

This is always updated faster than the copy in the plugin section.

https://plugins-svn.bbpress.org/freshly-baked-cookies/trunk/

[Gautam Gupta]

When editing a reply, the “Notify me of followup posts via e-mail” text appears twice (once below the “Allowed markup” and once above.)

I think this is related to theme, I didn’t happen on my installation with Kakumei.

This means that the theme here doesn’t contain edit-form.php and is using Kakumei’s. In the patch I posted, the action (to add the checkbox) is removed in functions.php and is instead added at a custom location in Kakumei’s edit-form.php, and as functions of Kakumei aren’t loaded here, the default action isn’t removed and the checkbox is displayed twice. This doesn’t happen with post-form.php as it is present here.

[Matt Mullenweg]

Shared-hosts are the bread and butter of WordPress usage. The good news is servers are way more powerful than when I wrote the first bbPress, and we can take advantage of that to provide a richer experience.

I like the idea of plugin-centric development from a theoretical point of view, and obviously plugins have been at the core of WordPress’ success, but I think it can be taken too far and take away from the user experience.

It’s about taking responsibility. Even though you could break down almost every feature of WordPress into a plugin and distribute everything bundled, and even activate a bunch of them by default I think you lose a “buck stops here” for other developers to target. The uncertainty of testing the interactions of N factorial plugins is daunting and gets untenable quickly.

Better to draw a line in the sand and promise the user “these things will always work together.”

[citizenkeith]

It’s a natural tension. I think the best way to split the difference is to keep the core lean and mean, and then to have a set of pre-packaged plugins that are included in the main download that can be turned on (or can even default to being on).

This gets my vote as well. Instead, I would prefer the next version of bbPress to have more powerful admin features (see Kevin John’s above examples for specifics).

[johnhiler]

I think most developers who run highly trafficked websites will prefer keeping stuff out of the core, to minimize bloat and to maximize scaling. Whereas most casual webmasters running a smaller forum will want as much in the core as possible.

It’s a natural tension. I think the best way to split the difference is to keep the core lean and mean, and then to have a set of pre-packaged plugins that are included in the main download that can be turned on (or can even default to being on). I think WordPress experimented with this direction last year? Not sure where it ended up though.

A few things were moved out of bbPress plugins into core, and it hasn’t really gone that well. “Subscribe to topic” was added to the core, and then promptly had a problem with spammed topics being blasted out over email. It’s a lot easier to apply a patch to a plugin than it is to get the patch approved in the core.

The “Page Links for bbPress” plugin was also moved into the core in 1.0. There were a number of code inefficiencies in that code that are now locked into the core. There was a recent patch released for the plugin version of Page Links (only for 0.9) that fixed this; that’s an example of how it can be helpful to keep non-essential stuff out of core.

[RedBull]

I am trying to locate or even find out if it is possible to change the “New User” registration email. The default one gives no instructions regarding changing your password etc.., Any help would be greatly appreciated.

[Matt Mullenweg]

It should be even more seamless than it is now, possibly even included with the default BuddyPress package. (But I’ll defer to core BP people there.)

[ZKuJoe]

I was using WordPress for a while but I prefer forums over blogging software so bbPress was the best of both worlds! I just altered the default theme to look more like a blog. Let me know what you think.

http://www.jmd.cc

[_ck_]

honestscott, any update on this?

Even 1.x should not be causing slow queries, something might be misbehaving.

My Super Search plugin DOES do a very heavy non-indexed query, it’s unavoidable. But unless you have a large forum with frequent searches, I am not sure that would get you in trouble.

The good news is if you’ve moved to a VPS (I assume that’s what “semi-dedicated server” means) you have direct control over a few important things you didn’t have before. It means we can make sure your MySQL cache is on (it’s off by default on many setups for some strange reason) and you can install an opcode cache like eAccelerator which will cause a fantastic reduction in load and improve speed.

[_ck_]

Currently there are only four settings and all but the first are optional.

Edit the top of the plugin to see them:

$browsertimer['log']='/browsertimer/browsertimer.log';

That is where the log is kept.

Obviously the directory must be chmod 777 on your server.

For that reason I STRONGLY recommend you put it ABOVE the web root.

The default setting will do that:

dirname($_SERVER['DOCUMENT_ROOT']).'/browsertimer/browsertimer.log'

but since it may confuse people, adjust it as you will.

ie. /home/username/public_html/

is the webroot on many servers but not all by any means

you could in theory make

/home/username/browsertimer/

and chmod 777 that directory, and it will work with the default setting.

$browsertimer['filter']=true;

This setting just throws away entries longer than 20 seconds or less than 100ms which are typically bogus. For example Google has a nasty habit now of parsing javascript no matter how obfuscated it may be to extract URLs, and sure enough it will follow the browser timer, giving you really high, weird numbers.

$browsertimer['pages']=false;

This allows you to control what pages are timed.

I’d leave it alone for now but someone may have specific interest in mind.

$browsertimer['geoip']=false;

This is where the geo-location magic happens, it’s optional, and will tell you what country the visitor is in with about 90% accuracy.

false = country lookup off

or set it to ='ip2c';

and download this program called IP2C

http://admin.firestats.cc/ccount/click.php?id=74

extract these two files and put them in the same directory:

ip2c.php

ip-to-country.bin

(ip-to-country.bin is very large, it’s one big database)

[Joe Gibson]

Z –

“It doesn’t understand strikethrough cause that tag (the obsolete ‘s’) isn’t enabled by default on bbPress.”

So, is there a way to turn it on?

And I understood that the ‘Code’ button was for generating backticks, but what are backticks used for since the buttons cover pretty much everything?

And, for that matter, why isn’t this site using it?

Thanks,

Joe

[zaerl]

I have inserted the “code” button for the simple reason that the backtick character is difficult to be typed on a keyboard that isn’t the “standard” U.S. ASCII. This is true for the vast majority of the keyboard layouts worldwide.

The only disappointment is that it doesn’t seem to understand strikethrough fonts.

It doesn’t understand strikethrough cause that tag (the obsolete ‘s’) isn’t enabled by default on bbPress.

I provide support for standard tags: strong, em, a, img, ul, ol, li, blockquote, code and the non standard img that is widely used.

My plugin do not enable new tags (and implicitly new buttons) in current version 0.3.2 but it does in 0.4 (trunk). I have taken my position regarding the future of bbPress and so I will not upload new plugins and/or updates (https://bbpress.org/plugins/topic/zaerl-editor/page/2/#post-5992). Anyway if you need the new zaerl Editor with custom buttons and other fancy features write me a couple of lines. za AT zaerl.com

[_ck_]

@Marius, but everyone downloads different ones.

I’d never want to see even a handful of my plugins built into bbPress by default.

As much as people express the desire for a program to do everything they want out-of-the-box, it’s a VERY bad idea with software. Makes things too bulky. WordPress today is a perfect example of what happens when you give into that desire, you get bloated, overloaded, slow code.

But sadly they don’t believe in plugins – I’m kinda surprised even akismet is not hard coded into WordPress.

bbPress should have been a lightweight framework, half the size that it is now, that maybe shipped with a dozen plugins that are OFF by default. Too late now though.

[Marius-]

Which is a strong indication that a huge majority of BBPress users wants the functionality offered by many of your plugins. Which should make it obvious that many of them should be built straight into BBpress by default.

[kevinjohngallagher]

Morning Peter,

It’s cool if you disagree. I’m confident we could all pick something in WordPress in the core that we think should still be a plug-in; and of course there is no right answer. What I’m not sure you’re aware of though, and you might be, is just how different the “overhead” between bbPress and WordPress is.

bbPress0.9 loads and runs at 10 or under SQL queries per page. Including the front page. Thanks to certain DB/query tweaks, and some wonderful _CK_ code, I have that at 8 SQL queries on one of my smallest intranet forums.

This is in comparison to the same 8 queries generated by the new wp_nav_menu in WP3.0. In fact the wp_nav_menu calls a not totally-in-expensive INNER JOIN for each post-type reference in the menu. It’s not a set 8 calls, without judging anything based on what it will become, if wp_nav_menu starts to accept custom post types natively, that’s going to shoot way up.

In a flat comparison, the default theme of WP3.0 with no plug-ins running, generates 19 SQL queries. Twice as much as bbPress0.9.

As someone mentioned earlier, the new bbPress plug-in would be lighter or sleeker. If it takes more SQL calls to generate the header and footer of WP than it does to load an entire bbPress forum – how does that work?

(I do realise that not all SQL queries are equal, but I do think it’s quite a good initial benchmark. Especially if you look at SAVEQUERIES output and see what sort of query each is, and its execution time.)

Additionally, as someone with your background with WP, I would love to hear your take on the caching issue. For two of my websites that have relatively ok traffic, caching is essential on WP. There are plug-ins that do this brilliantly, so thats no worries. But thats very much a “1 to n” nature. Forums are an “n to n” nature; and really don’t lean well with caching, especially in the flat-file constant-updated format.

How would one percieve that to affect WP based websites with a forum plugin of this nature attatched?

=================================

I think there is a viewpoint that is being missed here.

People are falling into 3 groups:

1. Need a forum that works with WordPress
2. Need a standalone forum, but some WordPress integration is ideal (sign in/users)
3. Needs a standalone forum.

There appears to be a presumption is that we’re all in Group 1 and that we’re fighting change. That’s not the case at all.

I’m actually in favour of there being a WordPress forum plug-in. I think loads of people here will be. I also think that with JJJ working on it, and Justin Tadlock’s second attempt out there in the wild that it will go really well. I wish it the best of luck, and if we can offer advice or war stories or anything to help out – we’re here. We’re here because we support FOSS

The issue arises here is if you’re in Group 2, you have a decision whether to “upgrade” to running everything through WordPress or not. It’s just been presumed that’s your actual goal. At this point in time, we’d like some information (positives/negatives at a minimum) and info on how this decision has came about. People in Group 2 could move into Group 1 easily if given more information than:

“everything is going to be A-okay”

“Like it or not, this is the hand we’ve been dealt…”

But the users in Group3, the people who chose this as standalone forum software and didn’t make that decision based on WordPress – they’re being thrown out on their ear. With no warning. JJJ has stated, and I think we all appreciate that he’s taken the time to sit and answer some questions, that bbPress1.1 will be it’s last. Well, thats announced as bbPress1.1 is 1 trac ticket away from being released. How much warning is that??

If you’re in Group3, and large chunk of our support questions come from people who are, you will now be ‘forced’ to run WordPress if you want to stick with bbPress.

==============================================

I suppose what I’m saying is this. Changes in Life and in FOSS happen. Some we like, some we don’t. But there has to be a carrot with every stick, or people start to feel publicly flogged.

I want JJJ and Pete and anyone who helps them to succeed in achieving their goals. But I’ve scanned this forum page, and the emails they were kind enough to send me, and right now, if you didn’t come here specifically to use a forum inside WordPress… I can’t see the carrot.

There are people here alot cleverer than me, and alot better at wording than myself, so if i’m missing the carrot, please do a Denzel “explain it to me like a 3 year old”.