[kevinjohngallagher]

Ash mate, you know how much I like you and your work, but that poll is never going to give even close to an accurate figure. To start with you don’t know why people are voting for each one, or how often, or who’s voting.

I mean, Matt came on here and said that 0.9’s not been looked at in a long time and BAM 1.1 starts to get more votes. Matt forgets to mention, the 1.0 branch has had the same number of releases in the last year as the 0.9 branch: namely 0 !!

How much the 0.9 version has actually gone through testing and how much we can be confident it being secured.

Well it’s had 2 years more testing than 1.0 in the wild, and generally (apologies in advance) by people who are happier coding/debugging/ working without a GUI than the folks using 1.0 branch. Plus, the WP forums were running 0.9 until last August (at least), so it was known to be very secure then.

I know it may contain bugs, any code can but my curiosity lies in the testing & use it has gone through already.

A sh*t load more than 1.0.

Rememebr 1.0 was (another) rewrite decreeed from “above”, and we cancelled all Beta testing, and it took 10 alphas to even get useable (pres Alpha6 isn’t compatible with after-alpha-6), and broke most plugins etc. The process of getting 1.0 out the door also led to some of the real wizards leaving the project behind (see Chip Bennet, Justin Tadlock, JJJ, _ck_ etc), and released it in a week, and we released an update to 0.9 at the same time as 1.0’s last update

In my opinion, as someone who uses both; 1.0 only has 2 things going for it: The Admin section and it has more Actions/Filters.

Replicating actions/filters into 0.9 is easy. As _ck_ said, getting a nice looking UI into 0.9 is a mini project.

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

1.1 has some good work, nae, some great work.

It also has some rusheed work, to get it out the door for testing.

It has at least 1000 lines of changed code last I checked (and that wasn’t today or yesterday) and we still have 10 tickets open – all before we release for Alpha testing, and all before we get a new package of BackPress released (in theory) after WP3.0.1’s release.

If we finished all of those tickets this week, and packaged an Alpha testing release for Monday, there is no way 1.1 will be released before September. Infact, we’re looking at a late-September/October release at a minimum, unless we skip testing and bug fixes (again).

Lets take our time and look at 0.9 objectively when 1.1 is close to coming out. Rushing into forks is just as dangerous as rushing into WP-reliant plugins

Ash mate, you’re a very smart guy. Go grab a busy forum and duplicate it on your machine, and convert to 0.9. You’ll very quickly see some of the small issues with it, but you’ll also be amazed at just how quick and robust it is.

[Ashish Kumar (Ashfame)]

@_ck_

How much the 0.9 version has actually gone through testing and how much we can be confident it being secured.

I know it may contain bugs, any code can but my curiosity lies in the testing & use it has gone through already.

If considered a fork, I think we need a few people on whom the people can count on for security updates.

What do you think?

[XU3E]

For example “test” and it find nothing…

[solved] It looks like it was fault at user role capabilities. But I am not sure.

[kevinjohngallagher]

_ck_,

More truly excellent work.

I offered a different solution though, it’s a geneology plugin thats currently with a few folks for testing. It is far from as elegant as this (though it’s scope is wider).

One of the things that I’ve “diskiked” about bbPress is lack of support for heirarchies. I know you’ve written some excellent code for finding the last poster for forums with sub forums before, but like the code above, they’re all workarounds.

It also makes it difficult for theme developers to get on board when wanting to call basic API functions for “last poster” for a forum or topic etc. At some stage, I’d love a discussion on small things like this where we could improve bbP0.9

[_ck_]

I’ve noticed that depending on the site configuration, many times plugins or template designs will require information about the first poster in a topic or the last poster.

The problem is that bbPress unfortunately (even in 1.1) only caches the post authors that are on the physical page you are on. So it causes two “out of flow” queries (one for user, one for usermeta) for each of those authors (first, last).

This means up to four needless queries are added depending on the topic page number (not first or last is the worst hit).

Even worse there is no direct filter/action on that process so it cannot be affected directly.

However I’ve come up with a workaround using a trick,

by catching the actions before and after the process.

I’ve only tested this on 0.9, but in theory should work in 1.1

if (is_topic && !is_bb_feed()) {

add_action('bb_topic.php_pre_db','usercachefix_load');

add_action('bb_topic.php','usercachefix_unload');

function usercachefix_load() {add_action('get_forum_where','usercachefix');}

function usercachefix_unload() {remove_action('get_forum_where','usercachefix'); global $posts; unset($posts['first'],$posts['last']);}

function usercachefix($x) {global $topic,$posts; $posts['first']->poster_id=$topic->topic_poster; $posts['last']->poster_id=$topic->topic_last_poster; return $x;}

}

Make it into a mini-plugin and give it a try.

You really only need it if you are showing info about the first and/or last poster on every page of the topic.

You should see the query count go down by two to four queries on the page.

Or use bb-benchmark to more closely examine the queries and look for multiple calls to the user-table and usermeta-table.

[nickaster]

So… anyone got a clue what might be missing here? Here’s the test forum – http://www.triplepundit.com/forum … I suspect I’m missing something in one of the templates?

[XU3E]

Filtering (searching) of users in admin is not working properly… Yeah, is not working at all.

The Latest version with BP and WP 3.0.

[Marius-]

Smartest thing I´ve ever said.

[Marius-]

So Social It is what causes this problem?

How come all other topics looks okay? But this topic suffers, and all others created afterwards?

I just created three test topics which all suffered from the same bug.

[zaerl]

Of course. I was ironic.

[kevinjohngallagher]

Well, bbPress as a plugin is official bbPress fork.

Ha

It’s really not.

It’s a totally new progam with the same name.

[Milan Dinić]

There’s an official bbPress fork?

Well, bbPress as a plugin is official bbPress fork.

[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

[zaerl]

offical bbpress fork

There’s an official bbPress fork?

[XU3E]

This is realy good plugin but Its not working properly with new versions bbpress. _ck_ doesnt support it anymore because his own branch for 0.9.

Its fantastic oportunity for someone skilled to take this for keeping update with offical bbpress fork.

Perhaps… it should be implement in bbpress core or bb-plugin.

[Erlend]

@Gautam

By that you mean front-end posting with the native WP editor, right? Not an included, new editor, the way bp-wiki or scribu’s editor currently does it?

Because when I’ve applied a plugin to extend the WP editor, that should apply to the front-end editing as well.

Thanks for the hint about image uploads with P2, I hadn’t noticed the feature. I’ll probably have to do a fresh test install though, because it’s buggy on my current one. Will report back my experiences later.

[Greg]

Matt, you are partially correct. A lot of this is about where the line is drawn. But I guess I also added another line. This has been the topic of discussion in WP before, but I think the concept of a *core plugin* is important.

A core plugin is released along with the real core and is held to the same release criteria (testing) as the real core.

Maybe this is semantics and you would just call a core plugin part of core. If so, that’s great, but I would still suggest that we talk about three things…

1. the real core

2. core plugins

3. general plugins

Referring back to your original framework, I think two of the criteria for core apply to the real core:

– essential for robustness

– something we want to promote

If it is something the majority (80%+) will appreciate then it could be released in the real core OR as a core plugin (e.g. akismet).

The benefit of a “real core + core plugins” approach is that it eliminates the conflict when something has both majority appeal AND connects to a service (again, akismet example).

It also eliminates a lot of the angst people have about additional bloat in the real core, or about the quality concerns for important plugins.

Bottom line: you can have your cake and it it too. A core plugin does not add bloat, AND it is released with all the QA of a feature in the real core.

[_KB_]

@kevinjohngallagher thanks dear, I’ve done it already, its a part of integration, But I really surprised why its won’t work for me??

but I’m curious that may be _ck_ tell me new thing.

OK, I’m going to disclose my config files and cookies, check it dear buddies….

for wordpress,

http://pastebin.com/embed_iframe.php?i=hPpMiDyZ

for zptest students

http://pastebin.com/embed_iframe.php?i=jcS2377M

If you need more things, I’ll share it..I really want to fix it….Thanks

[Joe Gibson]

Z – I got on a bbPress plugins page and found your ‘Open in new window’ plugin but the rascal doesn’t seem to work. Tried it in both ‘bb-plugins’ and ‘my-plugins’. It activates just fine. Is there a trick I’m missing?

Thanks,

Joe

[Joe Gibson]

Z – Thanks, the ‘s’ did it. Very appreciated.

The one last thing that would really make this editor the cat’s ass would be opening links in a new window. Is there a PHP version of “Target=_blank” we can slip into the code?

Joe

[yetanotherlogin]

To have WP send my admin password, I edited php.ini to use my ISP’s SMTP server instead of “localhost” (no SMTP server on this test host), restarted PHP-FastCGI, and clicked on the WP “Lost your password?”, but I get this:

“The e-mail could not be sent.

Possible reason: your host may have disabled the mail() function…”

So can’t get the admin password back. Anyway, since it doesn’t complain about the password and just loops back, I assume it has to do with the WP/bbPress integration?

[_KB_]

So, here exactly What I want,

Suppose I’ve planned to run multiple discussion boards, and I’m using

http://zptest.info/ ( WordPress )

http://zptest.info/students/ [bbpress 1]

http://zptest.info/teachers/ [bbpress 2]

http://zptest.info/management/ [bbpress 3]

I’ve done:

-1: Shared User Integration ( Works )

-2: Shared Database Integration ( Works )

-3: Shared Cookies Integration (Not Works, that’s what I want)

I’ve followed all instruction from bbpress Integration tutorial

Now cookies not works, you can test it at zptest.info

user: test

pass: test

(I can send also admin’s or ftp detail, if anyone really interested)

cookies are conflicting, sometimes not logout from other boards.

Suggestion:

I’m hopping there should be a plugin, just for set cookies for multiple boards in same domain.

People just do, user integration, and database integration.

then install ( cookies plugin ), that’s all,

Come on, _ck_, you can do it,

Thanks

KB

[Ivaylo Draganov]

phpinfo() tells me that PHP is Version 5.2.13

Now, pretend I am crazy and tripple check the settings at the top

LOGGED_IN_KEY

LOGGED_IN_SALT

The two keys and salts are the same. Keys I get from wp-config.php and salts from wp-admin/options.php.

take a REALLY good look at the cookie data – it changes between bbPress and WP but really only two parts should change, the expire date and the hash. So between the last | in the data

How the hash forms is still not quite clear to me, but obviously that’s where the issue lies. I notice that it’s different every time I log in (no matter from which side). I if log in/out of WP 10 times I get 10 different hashes. But maybe that’s the normal way.

Other things to note:

* I am using year long cookies plugin on the bbPress side

* bbPress has a trailing slash in these settings:

$bb->wp_siteurl = 'http://dev.example.net/';

$bb->wp_home = 'http://dev.example.net/';

whereas WP has them without the slash:

define('WP_HOME', 'http://dev.example.net');

define('WP_SITEURL', 'http://dev.example.net');

* as you can see I am doing this on a dev subdomain and not on the live site. Even though I did test it on the live site(with the main domain) too and the result was the same

* the lines you mentioned in the plugin did not match: I had that code on lines 70 and 83

* define('AUTH_COOKIE_VERSION', 2 ); should be added at the top of _freshly-baked-cookies.php, right? I did not exist there in the plugin download, so I added it before starting the tests

Thanks a lot for helping out

[yetanotherlogin]

Hello

This is the first time I’m setting up WordPress and bbPress, so it could be something very obvious, but from reading the tutorial, I couldn’t figure out what to enter at Step 2 – WordPress integration:

CHECKED Add integration settings

CHECKED Add cookie integration settings

WordPress address (URL) This value is required to continue.

? http://192.168.0.8:8787/wordpress/

Blog address (URL)

? http://192.168.0.8:8787/wordpress/

WordPress “auth” cookie key

?

FYI, on the test host, I have WP installed in /var/www/wordpress/ and bbPress in /var/www/bbpress. The two applications shared the same database in MySQL, since I assume it’s easier that way and they use a different prefix when creating tables.

Considering this context, does someone know what to type above

Thank you for any help.

[Erlend]

But you certainly are not going to get anyone who is NOT using WordPress to install WordPress just to create a forum. There are far better options out there.

You’re probably right. Yet allow me to give an example of how major plugins like bbPress and BuddyPress complement WordPress in a way that greatly adds to its appeal (i.e. grows the customer base beyond those interested in WordPress)

Much like WordPress, our project (jMonkeyEngine) is a continuation of someone else’s work. When we picked up the reins of the jmonkeyengine.com website, we were stuck with three separate content systems (SMF, DokuWiki, WordPress) and a mess of custom code. We looked at several options, like:

– Extend SMF (no doubt the heart of our community activities) into a full-scale CMS

– Tie all systems together with a solution like Atlassian’s Crowd

– Replace our custom front page with Joomla! and use JFusion to tie all four tightly together.

– Replace everything with a widely extended Joomla!

We practically tried all of those options and more in practice, either in testing environments or on our live site. Meanwhile I’d been looking at complete ‘community solutions’, like Elgg, OpenWack, JomSocial, BuddyPress…

(I definitely looked at Drupal as well, but they just didn’t seem to have anything near as simple as say JomSocial that just goes ‘boom, now you can start build your community).

Then bbPress came to BuddyPress, and I made a decision. I proposed an overhaul and we got moving:

http://www.jmonkeyengine.com/forum/index.php?topic=13934.0

The only reason we’re not spamming press-boards with ‘look at us!’ links yet is because we made the decision to move everything over at once, and that includes the risky decision of adopting the BuddyPress-Wiki plugin (every other essential has been covered by core features) to replace our DokuWiki. With D.P. Cartwright’s dedicated help we’re just about there though.

Erm, point ahoy!

So the point I’m trying to make is, we never stopped to consider WordPress as a CMS, until BuddyPress arrived as the major complement to fulfill our every need in one package, as opposed to 20+ plugins. Having used WordPress for my own portfolio page and general sandbox play I already knew how intuitive (extremely so when compared to Joomla!) and easy to extend it is. When the last remaining piece of the puzzle arrived, the choice was a no-brainer. I imagine many will come to the same realization with bbPress.

I know I did not prove you wrong; I just figured people might find this brief case study interesting.