[_ck_]

Huh?? “call it something new and fork it” ??

Um, but “1.2” itself is a fork without being renamed?

Forks of the original standalone bbPress serve the community by giving them somewhere to turn to since they are being abandoned. In less than a year they will find this forum completely useless for assistance.

So I consider fork announcements a badly needed public notice/service.

Kevin feel free to duplicate this topic on my site if need be, as well as any anyone else making a fork announcement of their own.

[_ck_]

Spotted this today

http://www.google.com/buzz/gautam.2011/8CJfjUXFwEH/Forking-bbPress

[_ck_]

KSES is too slow to use for realtime output.

It’s used by WP/bbPress *before* the post is saved permanently (pre_post filter)

But bbcode is stored as bbcode, not converted HTML.

So it has to be converted to html each time a post is shown (post_text filter).

So KSES is too slow for that.

(plus I don’t want to use an external function with regex matches, which makes it ten times more complex)

[_ck_]

Okay there are two different people in this conversation.

But no, you cannot change the post order in a topic, at least not correctly and consistently. bbpress internally uses post-position and hard codes the post order.

The system would have to be redesigned.

My user-wall already avoids this problem and allows posts in any order and any spinoff I might create from bbpress will also have this ability.

But for now, no bbpress can’t do that correctly.

[_ck_]

Wait, are you talking about on TOPIC pages or on forum/front page.

The default order in bbPress is newest topics show up at the top on forum/front page, but newest posts show up last on topic page.

Because you said “posts” I assumed you meant topic page.

Or are you saying you want to link the “last poster” to the last post in a topic? That’s already done on freshness?

[_ck_]

I’ve now added experimental support for bbPress 1.x

starting with version 0.0.4

Looking for feedback from those running a realworld, robust 1.x setup as I only have a test install.

Personally I also think it looks better in 0.9 but that’s just me.

It cannot damage anything during testing as it’s a read-only kind of plugin (for now).

[_ck_]

They did something wrong and bbpress defaults to “anonymous” when it can’t find the user. Probably means they didn’t do a global or something like that.

[_ck_]

I really like how you turned forums back into pseudo categories, very minimalistic.

Is it just my setup or are there no images at all on the page?

Or are you blocking base images based on referer (a bad idea).

[_ck_]

Some but not all of my plugins work in 1.0, I just don’t list them as working with 1.0 and I don’t offer support officially under 1.0

Note that absolutely no existing plugin will work under 1.2/2.0 (though some will probably be able to be modified if the author choses to do so).

[_ck_]

You’d be much more likely to get someone with buddypress experience on their support forums, not sure if anyone can answer that questions here since it’s deep integration.

[_ck_]

Since the original source is no longer available

and the theme is GPL I am mirroring it here:

http://bbshowcase.org/themes/cf-vanilla.zip

(Note the original poster’s link is no longer running bbpress)

[_ck_]

Better places than here for css advice but this one is easy

http://www.w3schools.com/css/css_background.asp

no-repeat is what you want.

[_ck_]

Yeah the two common mistakes when editing PHP files is to mess up the closing or to put whitespace after the closing which then causes “headers already sent” error.

The new preferred technique is to leave the closing off altogether, because PHP doesn’t care and it prevents errors like that – which I will probably adopt in my future code for plugins etc.

[_ck_]

Sorry I missed this, anything that appears before all the headers is likely any other file you modified in bbpress startup process. Since the most likely file is bb-config.php which is often edited, you might have left two closing marks

?>



?>

So the first one closes that PHP file, the second one gets displayed as plain text before the header.

[_ck_]

Kakumei doesn’t have post numbering from what I see, neither does inove.

Take a peek inside your post.php template and tell me what’s between

<div class="postnumber"> </div>

It’s also possible that it is in topic.php instead.

[_ck_]

Huh. The post numbering did reset. That is strange.

What theme is that – I’d have to see the post.php to see what function they are using between <div class="postnumber"></div>

I see a few people using neoease for bbPress but I can’t find it anywhere? Where did you get it? Or is that inove with your own modifications?

[_ck_]

I mean just to try it from admin after you alter the count on purpose.

You should not be hacking the admin functions, recount are in their own file anyway.

[_ck_]

you can try an experiment to change the 20 to 21 and/or the 80 to 81 (I see you deleted posts the so the 80 is now 69)

then do a bbpress recount

see if it changes or not

if it doesn’t change, try the manual way

if the manual works but bbpress does not, then there is a bug in how bbpress is doing it that is causing a silent error and it fails

[_ck_]

the deleted post will always causing missing numbers

that is because in your template the number is based on post-position which is never updated

the important part is that the count changes from 21 to 20

the question is why when you run the direct recount within bbpress itself, it did not change that 81 to 80, but the manual query changes 21 to 20

if you want those numbers to be continous on the page, you’d have to change your template but it doesn’t affect how bbpress works

[_ck_]

That query IS working properly on my test copy.

I purposely changed the topic_posts on a topic from 46 to 99.

Then ran this

INSERT INTO bb_topics (topic_id, topic_posts)

(SELECT topic_id, COUNT(post_status) as topic_posts

FROM bb_posts

WHERE post_status = '0' GROUP BY topic_id)

ON DUPLICATE KEY UPDATE topic_posts = VALUES(topic_posts);

and it reverted it back to 46

So try changing the 80 to 81

then try the above query and see if it changes it back to 80 or not?

[_ck_]

Actually I can simulate the problem on a test copy.

I’ve just got three other things going on right now so this is taking me longer than the few minutes it should have taken to investigate

[_ck_]

Yes but I didn’t want you to do that.

We need to find out why the post count is failing to update.

Or you will just keep running into the same problem over and over.

Actually I guess I can simulate the problem on a test copy.

[_ck_]

Thinking out loud here, don’t do anything yet on your own.

This is Sam’s new routine in 1.0.2 based on my alternate recount for bbpress 0.9

$sql = “INSERT INTO $bbdb->topics (topic_id, topic_posts)

(SELECT topic_id, COUNT(post_status) as topic_posts

FROM $bbdb->posts

WHERE post_status = ‘0’ GROUP BY topic_id)

ON DUPLICATE KEY UPDATE topic_posts = VALUES(topic_posts);

“;

I will investigate further…

[_ck_]

Okay what is happening is that the new recount in bbpress 1.0.2 is failing.

It’s getting the correct number of posts, it’s just not updating the table.

I am investigating (while trying to do 3 other things right now, lol)

[_ck_]

I forgot to add the topic_id=12 and group by on my queries sorry.

Well the numbers are coming from post position.

But still something is very wrong, because bbpress is showing 81 as the post count.

You need to run the exact query that the recount function uses.

SELECT topic_id, COUNT(post_status) as topic_posts FROM bb_posts WHERE post_status=0 AND topic_id=12 GROUP BY topic_id

See if that gives 80 or 81