[frooyo]

cough cough, an output cache would be awesome, cough cough

[frooyo]

By the way, the download counter if very cool.

https://bbpress.org/download/counter/

[frooyo]

@jurasiks

https://bbpress.org/documentation/upgrading/

[frooyo]

@_ck_

I completely agree that alpha/beta labels should be respected.

But it’s been now in development for YEARS and for most users – bbPress simply works.

At some point, you have to just call it “stable”. Why not now?

[frooyo]

@jonhiler

I totally understand that _ck_ has done a tremendous amount of work related the to plug-ins.

But her telling people to simply not use the new release causes more damage than harm to the community, no?

[frooyo]

@jurasiks

In my opinion, of course I can’t speak for Sam, because it was ready.

Also, now that it’s marked as stable 1.0 – more people will be willing to use it.

[frooyo]

@_ck_

Everything you describe is a reason TO USE 1.0. The more people who use it, the better it will become because more people will report any noticed issues etc.

Telling everyone to wait a few months will then just cause NO ONE to use it. Then in a few months, the bbPress core is no better than when it was initially released because the community never got involved.

Simply look at how much involvement the community jumped in when Sam changed the name to Release Candidate.

There was more activity in the last few weeks than in probably the last 6 months.

(Also, you’re post smells of so wishes that 0.9 never changed. You can always fork 0.9 and start you’re own forum product. Maybe call it ckPress)

[frooyo]

@Sam

Thanks for the 1.0 release !!!

Quick question. I don’t believe what you changed in the core is still the desired result.

I only have 1 forum, and that forum is called = “All”.

I have the following code in my post-form.php template

<label for=”forum_id”>Category:

<?php bb_new_topic_forum_dropdown(); ?>

</label>

It’s printing/echoing to the screen the forum name (“All”) –> see image below

http://img22.imageshack.us/img22/4105/categoryy.png

The generated HTML is:

<label for=”forum_id”>Category:

<input type=”hidden” name=”forum_id” id=”forum-id” value=”1″ /><span>All</span> </label>

It seems to me that if someone only has 1 forum, that you should simply have the hidden input and NOT print the forum name in any SPAN element at all.

Do you agree?

[frooyo]

@johnhiler

Is there any way of doing this beside using a CSS “display: none”. Seems like a hack way of working around this.

[frooyo]

@Ramoonus

Actually, I don’t believe people have tried converting SuperCache over yet. Because everyone is under the mentality that bbPress is “already fast enough”.

I would like to take on the challenge to converting the plug-in myself. What I don’t understand is why people are giving me a hard time for attempting to create a plug-in. I’m simply trying to better the bbPress community.

As such, all I’m asking for is a little bit of assistance and that’s:

– What is the hook to perform an action immediately after a new Post/comment?

– What is the hook to perform an action immediately before rendering the frontpage?

– What is the hook to perform an action immediately before rendering a topic page?

[frooyo]

@_ck_

What’s so difficult about it?

Let’s assume we only output cache for non-logged in users, just like SuperCache.

You only need 2 hooks.

1. A hook after a POST is submitted to re-cache both the frontpage and topic page

2. A hook before rendering both the frontpage and topic page to check to see if the cache is present.

Am I missing something here?

[frooyo]

@johnhiler

If you have some info on how I would create the SuperCache “hooks” into bbPress, that would be greatly appreciated.

[frooyo]

All

I would like to attempt to convert WordPress’ SuperCache plug-in to bbPress.

I’ve never created a plugin before.

Does anyone has any reference docs or pointers on how I would create the hooks needed for SuperCache on bbPress?

[frooyo]

In case anyone is curious, I created the following plugin to remove the Occupation and Interests user profile meta data.

<?php

/*

Plugin Name: My Profile Fields

Description: My profile fields for my lovely forums

Version 1.0

*/

function my_profile_fields( $fields ) {

unset( $fields ); /* removes the Occupation profile field: */

unset( $fields ); /* removes the Interests profile field: */

return $fields;

}

add_filter( ‘get_profile_info_keys’, ‘my_profile_fields’ );

?>

[frooyo]

Hmm … looks like it’s hardcoded in the bb-include/functions.bb-core.php

/meta_key => (required?, Label, hCard property). Don’t use user_{anything} as the name of your meta_key.

function bb_get_profile_info_keys( $context = null ) {

return apply_filters( ‘get_profile_info_keys’, array(

‘first_name’ => array(0, __(‘First name’)),

‘last_name’ => array(0, __(‘Last name’)),

‘display_name’ => array(1, __(‘Display name as’)),

‘user_email’ => array(1, __(‘Email’), ’email’),

‘user_url’ => array(0, __(‘Website’), ‘url’),

‘from’ => array(0, __(‘Location’)),

‘occ’ => array(0, __(‘Occupation’), ‘role’),

‘interest’ => array(0, __(‘Interests’)),

), $context );

}

Anyone know of a good way to remove Occupation and Interests without having to modify the bb-core.php file (to make future upgrading easier)

[frooyo]

@johnhiler

Thanks, I’m looking into the database right now myself.

If you find anything, please let me know. Back to looking myself

[frooyo]

No plugin.

It’s a clean RC install.

[frooyo]

All

Since I’ve never developed a plugin for bbPress before …

Does anyone mind pointing me in the direction of where I should begin.

I would like to attempt to port WordPress Super Cache (output cache) plugin to bbPress for non-logged in users.

[frooyo]

@r-a-y

Are you using the WP Super Cache (output cache) with success?

If so, I would be EXTREMELY interested in know how you got it to work.

[frooyo]

@Sam

Does your message imply that if we use trunk, then WordPress static caching will work in bbPress?

[frooyo]

You have 2 options.

1. Limit it on the client side using JavaScript

2. Limit it on the server side using PHP.

If you limit it on the client side, it’ll be the easiest to implement but if the person turns off JavaScript in there browser – the person will still be able to post greater than 3000 characters.

If you choice option 1, you’ll want to create some type of “maxlength” functionality for the TEXTAREA attribute in the post-form.php.

I haven’t used it but you’ll want to use something simply like:

http://www.javascriptbank.com/javascript/form/validation-limitation/textarea-maxlength/detail/

[frooyo]

@Markus Pezold

Thanks but this is not exactly what I’m looking for.

I do NOT want Anonymous posting.

What I simply want to do is display the HTML textarea field to either create a post or reply to an existing post to non-logged in users.

Then, once that user clicks submit – it then asks them to either login or create an account.

I don’t believe this is driven by bbPress but it’s a demostration of what I’m talking about.

http://www.streeteasy.com/nyc/talk

Notice how at the bottom of the page, you can “Start New Discussion”, then once you submit the form – it prompts you to login.

[frooyo]

Does anyone have more details on what type of caching mechanism was added to the recent RC?

Per Sam blog post:

>>”Some new issues came up around WordPress integration, caching and SQL query performance which were simply too important to leave out of the final 1.0 release.”

It seems like he is inferring that some type of caching mechanism has been added.

[frooyo]

@_ck_

Like massbase said, the blog announcement from Sam says:

>>”Some new issues came up around WordPress integration, caching and SQL query performance which were simply too important to leave out of the final 1.0 release.”

That seems to indicate to me that Sam did add in some type of caching mechanism into bbPress 1.0

bbPress 1.0 Release Candidate 3

Did I misinterpret what Sam wrote?

[frooyo]

@massbase

Since you have some free time (and it sounds like you understand the inter workings of bbPress), would you mind taking a shot at converting the WP Super Cache plugin for use with bbPress

Again, the key here is that it really only needs to work for non-logged in users since they will generate the most traffic (most load on the server).