[_ck_]

Is it possible you have lost the proper integration and WP is making one cookie name and bbPress is making the other?

[_ck_]

https://bbpress.org/plugins/topic/bb-topic-views/

https://bbpress.org/forums/tags/views

[_ck_]

I really can’t build an entire custom plugin for you.

What you are trying to do will require API functions because the profile link doesn’t exist until it’s calculated. You’ll have to use the get_profile_link functions and send it the user id.

bb_get_profile_link($result->ID)

[_ck_]

I think somehow you have the same cookie name but a new hash, meaning the contents are different while the name is the same. That would make it look like it’s attempting login but fail until the cookie is deleted.

[_ck_]

Ah I see it was even pulled from the download page, which bothers me of course.

It’s always available via trac too:

https://trac.bbpress.org/changeset//tags/0.9.0.5?old_path=%2F&format=zip

or the branch might have a few fixes someday in the future

https://trac.bbpress.org/changeset//branches/0.9?old_path=%2F&format=zip

[_ck_]

If the new cookie has a different name, you should not be having a problem because bbpress should not even be looking at the old cookie?

You are getting a header error because you would have to put it at the very, very top of header.php before doctype – if that doesn’t work, you’d have to add it via a mini-plugin, put it into a file called function.php in your template folder

add_action('bb_send_headers','delete_old_cookie');

function delete_old_cookie() {

setcookie('wordpress_logged_in_REPLACEDcabef','',time()-3600);

}

[_ck_]

There have been tag problems even here on bbpress.org with 1.0 and the problem may be related.

Try it with javascript disabled so the ajax doesn’t kick in and you can see the actual error perhaps.

[_ck_]

This will show avatars

add_action('topicmeta','voices_named');

function voices_named() {

global $bbdb, $topic;

$results=$bbdb->get_results("SELECT ID,user_login FROM $bbdb->posts LEFT JOIN $bbdb->users ON poster_id=ID WHERE topic_id=$topic->topic_id AND post_status=0 GROUP BY poster_id");

$count=count($results);

if ($count>1) {

foreach ($results as $result) {$ids[$result->ID]=$result->ID;}

bb_cache_users($ids);

$list="";

foreach ($results as $result) {$list.=bb_get_avatar($result->ID, 16).$result->user_login.", ";}

$list=trim($list,", ");

echo "<li>$count members active on this topic: $list</li>";

}

}

[_ck_]

I actually had it tested in 1.0, if it’s not working in your theme and it’s a custom theme, make sure you have a do_action('topicmeta') somewhere in there.

Adding avatars makes it much more complicated, I’ll give a shot at the code in a minute.

[_ck_]

If the old cookie has a different name than the new cookie that’s easy, make a plugin to set the time for it in the past.

If it’s the same cookie name old and new, and it’s a problem of the hash for the value inside being wrong, there is nothing you can do.

If you can detect when a cookie is being sent but failing to authorize you could delete the cookie like the first method I mentioned. You’d have to replace a function or two from pluggable.php

[_ck_]

In 1.0 you could use xmlrpc to do that and convert a plugin from WordPress if such a creature exists.

Your best bet is to use a service that is optimized for mobile, maybe like flickr and then use a plugin to post it elsewhere.

[_ck_]

I have to say that while I may not agree with some of the politics around the 1.0 release, the amount of effort Sam has put into 1.0, especially over the past few months, is simply amazing and very impressive. Converting the entire bbPress core to use the WordPress core was not a trivial task.

[_ck_]

You could easily modify the “topics per page” plugin to work differently depending if a user is logged in or not.

In fact the plugin could be modified to allow each user to choose how many topics per page and how many posts per topic, now that I think about it.

Not sure if it’s working on 1.0 though, probably not.

[_ck_]

If you add this code into a file called functions.php and put it into your theme folder, it will show the active names in the topic (if there is more than one person) It uses one extra query but it will also will work on 0.9

add_action('topicmeta','voices_named');

function voices_named() {

global $bbdb, $topic;

$names=$bbdb->get_col("SELECT DISTINCT user_login FROM $bbdb->posts LEFT JOIN $bbdb->users ON poster_id=ID WHERE topic_id=$topic->topic_id AND post_status=0");

$count=count($names);

if ($count>1) {echo "<li>$count members active on this topic: ".implode(", ",$names)."</li>";}

}

[_ck_]

Same problem because favorites are stored serialized in user meta.

Both of these issues can be addressed via a plugin however.

[_ck_]

You replace the new files over the old files.

After you replace the files you just go into the admin panel and if it needs to update the database it will tell you. Not all upgrades require a db change but most do.

If you downloaded the changed files like I posted elsewhere be sure to see Sam’s note about the backpress files too, they are not included automatically anymore when you get it off trac because backpress is considered a separate program.

[_ck_]

@Gautam: the auto-upgrade feature in wordpress requires you to make your directories world-writeable which is very dangerous. Also it “phones home” with all your install info, which I am not certain everyone wants to happen. I suspect it’s unfortunately going to come to bbPress eventually but I wouldn’t be in a rush for it.

[_ck_]

Oh I totally forgot about backpress now being automatically dropped in.

I guess the changed files is not a good idea anymore.

I still recommend people install SVN as a client if they can on their server, makes life much easier.

[_ck_]

Slightly on topic, Matt is in INC magazine this month:

http://www.inc.com/magazine/20090601/the-way-i-work-matt-mullenweg.html

[_ck_]

A reminder to those using 0.9 not to upgrade to 1.0 yet as many of my plugins (and others) do not support 1.0. I will not be addressing plugin upgrades until December.

1.0.1 changes:

https://trac.bbpress.org/changeset?old_path=tags%2F1.0&old=2294&new_path=tags%2F1.0.1&new=2309

to download changed files only:

https://trac.bbpress.org/changeset?format=zip&new=2309&old=2294&new_path=tags%2F1.0.1&old_path=tags%2F1.0

The meta issue seems the most serious to me.

[_ck_]

1.0.1 posted 20 minutes ago.

https://trac.bbpress.org/changeset?old_path=tags%2F1.0&old=2294&new_path=tags%2F1.0.1&new=2309

to download changed files only: https://trac.bbpress.org/changeset?format=zip&new=2309&old=2294&new_path=tags%2F1.0.1&old_path=tags%2F1.0

[_ck_]

This is what it looks like in Firefox. I don’t have the problem in IE.

I think the login button is too large and doesn’t scale maybe

http://img21.imageshack.us/img21/4106/food1r.png

[_ck_]

Read Only Forums has not been tested or fixed to work on bbPress 1.0 which is why you are probably having problems. If any of my plugins work on 1.0 it’s mostly luck at this point.

As far as hosting, I wrote this little bit last year:

http://ckon.wordpress.com/2008/12/18/some-tech-tips-to-find-a-better-wordpress-or-bbpress-host/

[_ck_]

Interesting. Well since you are on a shared server, the mysql performance can be very uneven. A better host will cut the page time in half.

I’m still getting This page generated in 0.40 seconds, using 26 queries. so one of my plugins might be causing the remaining extra queries. I suspect it’s Read Only Forums because the others should not be activating on the front page.

[_ck_]

Try deactivating bbPress Moderation Suite for a minute, I want to see if it reduces the load at all. You can see the queries count yourself if you do a “view source” in your browser and scroll to the very bottom where it says:

This page generated in 0.53 seconds, using 34 queries.