[vanesta]

Thanks Chris. Any pointer would be helpful in defining _COOKIE settings

Regards

Victoria

[_ck_]

If I missed such a large site in the top 100 be sure to let me know.

Sometimes it’s hard for me to find certain sites given how much bbPress is being customized.

(I had written a whole thing here but I accidentally closed the tab and restoring it never brought the text back unfortunately.)

You should never adopt a program based on one person, especially if that person doesn’t do it for a living and even more important since that person doesn’t work for the company that made the program in the first place

To be clear I am not abandoning bbPress, at least not until I find something better and I am not actually looking for something else right now and what I have seen over the past year has not impressed me much. Besides, there are other talents around here and they are slowing releasing more and more impressive plugins or porting them from WP. A couple years from now people won’t even remember me.

My biggest problem with 1.0 is how bbPress was on a course with 0.9 to correct many of the legacy mistakes that WordPress had made, and suddenly with a whim by Matt, bbPress has turned around 180 degrees and steered itself neck deep back into the muck and mire via BackPress. It’s now burdened with many more layers and required compatibility and it will never be any more lightweight than it is now, which is not so fantastic anymore.

Another big problem growing with 1.0 is how instead of taking any feature that is outside of the API functionality and making it external as a plugin, it is being poured directly into the core, setting itself up for more legacy failure, like WordPress. Sam wrote some really great plugins as an independent but now as a core developer he can just slide it right into the core. It’s far easier to modified the core to get new features done fast but it should be resisted at all costs. You’ll notice that WordPress doesn’t have any official plugins outside of akismet and “hello dolly”, it’s a very clear but invisible company policy – “we don’t make plugins, put it into the core”. bbPress is now headed down the same path and it’s not necessary.

Things like:

gravatars

voices

topic page icons

should not be in the core. Instead any necessary action and filter hooks needed to accomplish such features should be carefully created and then the features should be made as plugins that can be enabled or disabled as desired. bbPress already comes with a “factory” plugin directory, it should be put to good use.

bbPress 0.9’s greatest strength was as a lightweight framework.

1.0 is not just a framework anymore, it’s starting to tell you how it should look and feel, and that is bad, because there are dozens of other forum programs out there that will do just that.

[rich! @ etiviti]

ok, nevermind – figured things out. I found a bb_break_password function but since that is hooked into the blocked role. I just made a new one with a different $secret and cleared the auth cookie after changing the email (also sent out an email to the old address notifying of the change and initiated bb_reset_email on the new email)

it would be great if a feature like this was incorporated into bbPress for the future.

[vanesta]

Both installation on WP (2.

WP1 is on domain.com, and WP2 is on sub.domain.com (same domain name)

Both allow single sign on between WP1 and WP2 with this on wp-config.php

define(‘COOKIE_DOMAIN’, ‘.domain.com’);

define(‘COOKIEPATH’, ‘/’);

define(‘AUTH_SALT’, ‘6428746726478264’);

define(‘LOGGED_IN_SALT’, ‘74829749827489237424’);

define(‘AUTH_COOKIE’, ‘7482647263478623478’);

define(‘SECURE_AUTH_COOKIE’, ‘985847584758475’);

define(‘LOGGED_IN_COOKIE’, ‘98752975897435894375894’);

define(‘TEST_COOKIE’, ‘8947519875894758495’);

So I basically override the cookie also.

Now I installed BBPress (1.0)

These WP-CONFIG setting won’t work even I added BB_LOGGED_IN_COOKIE variable

It only works with BBPress if i use these only

define(‘COOKIE_DOMAIN’, ‘.domain.com’);

define(‘COOKIEPATH’, ‘/’);

define(‘AUTH_KEY’, ‘xxxxxxxxxxxxxxxxx’);

define(‘SECURE_AUTH_KEY’, ‘xxxxxxxxxxxxxxxxx’);

define(‘LOGGED_IN_KEY’, ‘xxxxxxxxxxxxxxxxxx’);

define(‘NONCE_KEY’, ‘xxxxxxxxxxxxxxxx’);

define(‘AUTH_SALT’, ‘xxxxxxxxxxxxxxxxx’);

define(‘LOGGED_IN_SALT’, ‘xxxxxxxxxxxxxxxx’);

But if I add anything with _COOKIE bbpress + wp signed on won’t work, if I take it out, it will with with BBPress but multiple WP single sing on won’t work

Thanks guys

Victoria

[rich! @ etiviti]

Hopefully I did not miss this somewhere else…

The one thing that bothers me is the lack of “security” around an email address change (besides the system allowing duplicates). I’d like to force a password change (generate a random) which is emailed to the new address to thwart ill intent.

I see the functions

function bb_reset_email( $user_login ) {

function bb_reset_password( $key ) {

but this hinges upon the

If you don't want to reset your password, just ignore this email. Thanks!

which the exact thing I want to avoid.

What would it take to verify the value of newpwdkey

bb_update_usermeta( $user->ID, 'newpwdkey', $resetkey );

and noting if there is a value stored, disable the login until bb_reset_password is executed via the link in the email.

*i’m ok with hacking the core files for the time being and merging with upgrades with my own markers.

[laimonas]

It was doing a similar thing or me, would not advance to step 1. After some debugging, it turned out that I didn’t have php-mysql installed. bbpress code detects it but the error message was getting lost and simply the response was redirected back to step 0.

Doing apt-get install php5-mysql did the trick.

[taboo]

Hi,

I started investigating possibilities of translation bbPress to Polish. This language along with quite a few non-germanic languages has quite complex plural forms (3 forms instead of just 2). Not getting into much detail, because of the way functions.bb-core.php hardcodes seconds, hours, days… names it’s hard to do a proper translation.

To do it right I’d need a function that uses “%d month” and not just “month” or “months” as defined here:

// array of time period chunks

$chunks = array(

array(60 * 60 * 24 * 365 , __(‘year’) , __(‘years’)),

array(60 * 60 * 24 * 30 , __(‘month’) , __(‘months’)),

array(60 * 60 * 24 * 7, __(‘week’) , __(‘weeks’)),

array(60 * 60 * 24 , __(‘day’) , __(‘days’)),

array(60 * 60 , __(‘hour’) , __(‘hours’)),

array(60 , __(‘minute’) , __(‘minutes’)),

array(1 , __(‘second’) , __(‘seconds’)),

);

Any help would be very much appreciated.

[Ashish Kumar (Ashfame)]

try wp-admin/options.php instead of wp-admin/options-general.php

thats what works in WP

[jasonbyer]

Where do I change the SMPT server… my host has given me the server info, but where do I change it in the bbpress code?

[Detective]

Here’s another tip:

I mentioned in another thread that I had problems logging in WordPress. If someone logged inside WordPress, the cookies were valid in both WP and BB but the user was unable to post in BB. The problem was that BB was authenticating the username in the cookie against a lowercase version of the user_login value. I manually changed all user logins in the database to their lowercased version and everything worked correctly

[deadlyhifi]

I’ve set up WPMU with subdirectories, rather than subdomains. I was having issues logging into multiple blogs e.g. http://www.blog.com/blog2

I found that removing the following from the wp-config.php file

define('SITECOOKIEPATH', '/wp-admin');

define('COOKIEPATH', '/');

sorted the issue and hasn’t broken sitewide login and cookie support.

Thought it may help someone

[rich! @ etiviti]

that is true. i modified the main register.php page (not the template – as i have a special flow for registration outside the standard bbpress way) and checked against the profile_info_keys and registered the error. But I guess one could override bb_new_user and throw a new error for a duplicate too

But, i’m not sure how one would go about handling the updating of a profile, on the main profile-edit.php page, i see this hook but its after the error codes have been checked. So I guess one could hack this page for the time being for a duplicate email and handle appropriately

if ( !$errors->get_error_codes() ) {

do_action('before_profile_edited', $user->ID);

[Ipstenu (Mika Epstein)]

You have to put them all in (and this is mentioned during the install and integration)

define('BB_AUTH_KEY', 'xxx');

define('BB_SECURE_AUTH_KEY', 'xxx');

define('BB_LOGGED_IN_KEY', 'xxx');

define('BB_NONCE_KEY', 'xxx');

define('BB_AUTH_SALT', 'xxx');

define('BB_LOGGED_IN_SALT', 'xxx');

define('BB_SECURE_AUTH_SALT', 'xxx');

[_ck_]

$page will be greater than 1 if you are on a paginated set of pages for any kind of view, topic, etc.

so do a

global $page;

and then if ($page>1) { blah }

but search engines like google are already aware of bbPress and index it well

[johnhiler]

Ah ok, I was just wondering if there was an implication that 0.9 doesn’t have a working integration with WordPress! Thanks for clarifying.

I definitely agree that it’s not as seamless as it could be…

[_ck_]

My point exactly about access. On a single server setup you might as well give more resources to mysql, it’s much more practical. The idea is to try to eliminate the bottleneck to mysql when you have contention among many clients. You won’t likely get that in a single server setup if mysql is done right.

The memcache layer in wp/bbpress is only one step above the mysql layer and the only thing you are saving is a few cpu cycles from when it decodes the serialized data from mysql to memory. It certainly doesn’t help at all the fact that bbPress 1.0, like WP, now does a gazillion copies of an object in memory as it references data, instead of using pointers like 0.9 does – all those copies add up, you can actually time the 50% decrease in performance on each ROW when displaying the front page with 25 topics and it gets magnified with each plugin used.

http://www.mysqlperformanceblog.com/2006/08/09/cache-performance-comparison/



Cache Type 	 Cache Gets/sec

Array Cache 	365000

APC Cache 	98000

File Cache 	27000

Memcached Cache (TCP/IP) 	12200     <<<<====---

MySQL Query Cache (TCP/IP) 	9900

MySQL Query Cache (Unix Socket) 	13500    <<<<===---

Selecting from table (TCP/IP) 	5100

Selecting from table (Unix Socket) 	7400

Maybe someone should write an interface into the wp/bbpress memcache object manager to use APC/eaccelerator shared memory instead on single server systems. Apparently that would be significantly faster.

[Satish]

I see that TinyMCE editor adds <p> </p> tags after each line. How can I convert <p></p> tag to <br /> tag ?

If this has been solved in any other threads, then please give me the link. I searched a lot before posting it here.

Please help…its very urgent.

[ArnyVee]

Understood. Thank you ck

[_ck_]

The people who have them working under 1.0 are likely using an older theme, either from a previous version of bbPress or a 3rd party template.

[r-a-y]

Ugly hack for now…

I commented out two lines in functions.bb-template.php:

Line 272:

if ( empty( $h2 ) && false !== $h2 ) {

Line 280:

}

Would be nice to get a better workaround that doesn’t require hacking a core file.

[clarklab]

d’oh! this works:

<?php global $topic; echo "$topic->forum_id"; ?>

should’ve mentioned I was on a topic page

[clarklab]

I tried inserting

<?php global $forum_id; echo $forum_id; ?>

just to test if I could grab the value and I could not. I tried it in a few places with no luck. What am I doing wrong?

Also thanks for all the plugins. I’ve got like a dozen of them running on my install.

[ArnyVee]

That’s strange. I didn’t deviate from the instructions, but they still aren’t showing. Darn, those are two very important plugins that I wanted to work. I guess I’ll just have to be patient until December.

[rich! @ etiviti]

both worked fine for me on 1.0 out of the box, no edits.

[r-a-y]

BBCode Buttons and BBPress Smilies work on bbPress 1.0 for me.

I’m having trouble with one of _ck_’s plugins, but I’m not exactly sure if it has to do with her plugin, bbPress or our server.