[creeese]

Nevermind that last message! I figured out what I did wrong.

[mbileppress]

I also want to try to create my own bbpress plugin

[John James Jacoby]

I like it.

[John James Jacoby]

@rootside – Placeholders for the login and registration pages are in the current bbp-twentyten theme, but they don’t work yet. The goal is for the bbPress plugin to include these pages as WordPress page templates and short-codes, to allow for maximum flexibility in configuring your site.

[geld lenen nl]

Wow, thats indeed a real nice comment form. Really like the slide effect. Hope someone can integrate this into bbpress

[VirtualityStudio]

those are great instructions! i tried to reinstall and got the login page, but still the error that it can’t connect with the database. i’ll have to wait and see if it is a problem just because of the preview dns. hopefully by the morning the site will actually be up so i can see!

thanks for your help by the way!!

[Ryan Hellyer]

This ia big THANKS for the ninja-awesome inline documentation. It makes reading the plugin files significantly easier

Also, I see above that there may be an alpha released in the next week or two. Do you think that would be suitable for running on a live site? I’m not adverse to having to fix bugs and problems here and there, so long as I don’t find myself stuck eternally on some old version without a semi-easy upgrade path. I don’t mind minor upgrades on upgrading, templates malfunctioning etc., but losing usernames, passwords and/or posts/topics would be quite disastrous.

I’m contemplating launching a forum within the next month and would rather use some semi-dicey alpha software than having to use one software for a few months, then upgrading to bbPress once it’s more stable.

[VirtualityStudio]

Yes, I have the correct host in there… I even copy-pasted it in to make sure

I just hope it is something simple so I don’t have to start from scratch and lose everything.

[VirtualityStudio]

Yes, I have the correct host in there… I even copy-pasted it in to make sure

I just hope it is something simple so I don’t have to start from scratch and lose everything.

[xarzu]

I have a Forum/Blog that I have been trying to get up and running. Right now I want to tackle the problem of having a huge amount of spam being generated by people — or bots — who are trying to register.

It is a payed web site (to keep out the riff-raff) and people have to buy a subscription to the site. But, suprisingly, this does not stop my inbox from being flooded by “requests for a username”.

Here is what my inbox looks like:

Most of the time, the email addresses in these messages are fake. But sometimes they are not but when I email these persons back, I am ignored. So they really are just spammers looking for a way of posting ad content on my web site for free.

The Registration page has a CAPTCHA Code required entry field:

http://www.arguemax.com/wp-login.php?action=register

But I wonder if the bots are sophisticated enough to get past that.

The user has to click on the “I accept the agreements” field but the agreements field clearly tells the user that they have to buy a subscription. If they do not click on that check box they get this:

One way I want to try to keep from getting all this spam is to make it such that the registration button is inactive until they click on the subscribe button

https://www.paypal.com/en_US/i/btn/btn_subscribeCC_LG.gif

How do I go about making that happen?

[gravity2]

I’m a newb, guys, and just wanted to share with other newbs who might have problems with require_once at Dreamhost.

/*the following line of code got the forums to appear correctly but then admin didn’t work. Note: registration does not work here now–email address not accepted.

require_once(‘../wp-load.php’);

*/

/*The program told me: Warning: require_once(../wp-load.php) [function.require-once]: failed to open stream: No such file or directory in /home/my_db_username/foo.com/forums/bb-config.php on line 66

Fatal error: require_once() [function.require]: Failed opening required ‘../wp-load.php’ (include_path=’.:/usr/local/lib/php:/usr/local/php5/lib/pear’) in /home/my_db_username/foo.com/forums/bb-config.php on line 66

So let’s try the full path and see if admin works. Otherwise, we’re going to see if we can load the bbpress admin functions in the main install.

*/

/*first using the /home/my_db_username path*/

require_once(‘/home/my_db_username/foo.com/wp-load.php’);

/*this works to display the forum correctly. Checking the admin side: admin side also working. Note: don’t work on stuff late at night if you’re going to miss simple stuff like this */

YMMV. Hope this helps somebody.

[Recker]

So i’m trying to Deep Integrate my WordPress with BBpress, everything is fine until now I get:

Parse error: syntax error, unexpected $end in /hermes/web03/b619/moo.defendersofthefallen/KaoTech/Forum/bb-config.php on line 72

In my bb-config.php line 72 is ‘ ?> ‘

You can see it for yourself at http://www.kaotech.co.uk/Forum

I’m sure I entered the code correctly

/* Deep integration */

if ( !defined('ABSPATH') & !defined('XMLRPC_REQUEST')) {

define('WP_USE_THEMES', false);

include_once(dirname(__FILE__) . '/../wp-blog-header.php' );

header("HTTP/1.1 200 OK");

header("Status: 200 All rosy");

I had to start on line 2 instead of line 1 as ‘ <?php ‘ was the start of the file, and the same tags were closed on line 72.

Am I missing something obvious or? Anyhelp would be great!

Thanks!

[Erlend]

I’d love to use a standalone bbPress, but that option was long since abandoned I stand by the reasoning behind the plugin route though, I still think it’ll make our lives a whole lot easier.

Thanks for the pointers John. It’s also comforting to know that BuddyPress forums will be seeing some speed improvements in 1.3.

[Erlend]

I’d love to use a standalone bbPress, but that option was long since abandoned I stand by the reasoning behind the plugin route though, I still think it’ll make our lives a whole lot easier.

Thanks for the pointers John. It’s also comforting to know that BuddyPress forums will be seeing some speed improvements in 1.3.

[Mark McWilliams]

I have been testing the bbPress Plugin on Windows, well I was up until about a month ago when I hit a few PC problems, but like JJJ said … much has changed since then!

[_ck_]

Each topic already carries the name of the person that started it, so this is very easy to do without a plugin.

Simply edit your front-page.php and forums.php templates and put

<?php echo $topic->topic_poster_name; ?>

where you’d like it.

also see this tag

https://bbpress.org/forums/tags/topic-author

[_ck_]

Each topic already carries the name of the person that started it, so this is very easy to do without a plugin.

Simply edit your front-page.php and forums.php templates and put

<?php echo $topic->topic_poster_name; ?>

where you’d like it.

also see this tag

https://bbpress.org/forums/tags/topic-author

[John James Jacoby]

Forum performance inside of BuddyPress is improved in 1.2.7 and will be further improved in 1.3 (which still includes the bbPress stand-alone version.)

Having BuddyPress load all of its code and process everything that it does is the bottleneck in your circumstance. You’d be better off loading bbPress standalone properly themed, then the bbPress plugin, and lastly inside of BuddyPress groups (regardless of standalone/plugin.)

But, I think it’s a horse a piece.

The more you need to load is the slower it’s going to be, and the more important caching becomes. The bbPress plugin will respond to W3TC much better than bbPress standalone and BuddyPress will, since it uses the existing WordPress object cache.

[John James Jacoby]

Forum performance inside of BuddyPress is improved in 1.2.7 and will be further improved in 1.3 (which still includes the bbPress stand-alone version.)

Having BuddyPress load all of its code and process everything that it does is the bottleneck in your circumstance. You’d be better off loading bbPress standalone properly themed, then the bbPress plugin, and lastly inside of BuddyPress groups (regardless of standalone/plugin.)

But, I think it’s a horse a piece.

The more you need to load is the slower it’s going to be, and the more important caching becomes. The bbPress plugin will respond to W3TC much better than bbPress standalone and BuddyPress will, since it uses the existing WordPress object cache.

[Gautam Gupta]

mobious74: Try going to Settings -> Permalinks and press save changes.

[_ck_]

There is no need to minify PHP comments, they are dropped by opcode caches.

However reducing query count is not going to be easy.

I’ll do a 3rd party analysis on the queries (and file count) next week or so, I suspect there is going to be little that can be done to reduce the load because of how this is now being done. It is likely any bbPress plugin install is going to have to be heavily cached on any reasonably active site, just like WordPress now absolutely requires a complicated cache like W3 Total Cache.

But what people don’t realize is you cannot cache an active forum like a blog, they work very differently. Blogs are write-once, read many times and then the comments can be isolated with periodic updates. But on a forum it’s write-many-times and constantly changing. So there will always be many cache misses and the mysql engine will get a huge workout.

Try using WP3 these days on an active site where there are cache misses, the server will fall apart. You cannot rely on the miracle of caching and ultra-fast hardware to get around fundamental design problems.

[Ryan Gannon]

The size of the codebase is largely due to the amount of phpDoc and inline documentation. I expected there to be a lot of eyes on this code from both bbPress and WordPress audiences, so almost everything is described in detail.

And I certainly appreciate it, but is there an easy way to minify it then?

[chinab2cc1]

lz,thank you very much!!!

[chinab2cc1]

lz,thank you very much!!!

[John James Jacoby]

The query count is high and needs and audit. We’re using internal WP functions for 99% of queries, so we thoroughly reap the benefit of the WP object cache.

The size of the codebase is largely due to the amount of phpDoc and inline documentation. I expected there to be a lot of eyes on this code from both bbPress and WordPress audiences, so almost everything is described in detail.