[_ck_]

One thing that’s probably holding that back and bugs me in that templates are not re-used in bbpress, is for example how post-form and edit-form should be integrated with maybe one or two conditional statements if necessary.

I guess ajax post deletes are a lot easier than ajax posting/editing.

Then there is the code block in front-page, forum.php & view.php which shows sub-forums, stickeys and posts. It’s virtually identical in each template but if you want to change one, you got to go to all three and change them in each place, the exact same code. It should be a sub-template, which of course I could hack in on my own but should be part of the core. Change it in one place, changes everywhere you see it.

[_ck_]

“get_topic_last_post_link()” and it’s dependency “get_post_link()” relies on two important things which can be easily thrown off in bbpress or it’s db

1. if you are using a plugin or other code to change the number of topics shown on the front page or forum pages vs the topic page, get_topic_last_post_link() will calculate the last post incorrectly. This is because there is only one universal setting in bbpress right now for the number of items per page (there should be an array in the core so limit can be different than limit and then get_topic_last_post_link() will know to look at the destination limit instead of where it’s coming from)

see my bug fix for custom limits for each page here:

https://bbpress.org/forums/topic/custom-topics-count-for-different-pages-that-doesnt-break-last-post

it basically forces get_post_link to recalculate

2. get_topic_last_post_link() relies on the post_position in the bbpress table – which can get messed up if there are deleted posts, moved/merged posts, or recounts

Recounts does not attempt to recalculate and resave the post_position. This would have to be written. It basically would have to look at all posts in a topic, sort them by the desired date order, and then renumber them.

[chrishajer]

Looks like it happened around r406 to address trac ticket 425? (the last place I can find topic-ajax.php is r384):

https://trac.bbpress.org/browser/trunk/bb-admin/admin-ajax.php?rev=406

https://trac.bbpress.org/ticket/141

09/22/06 20:47:15 changed by mdawaffe



* status changed from assigned to closed.

* resolution set to wontfix.



We're not even ajax posting anymore.

Should revisit this if we ever go back.

[_ck_]

Actually originally in my code, I was unserializing the data ONCE, then the array is passed globally, already in place. Serializing data is only bad if you are going to be constantly unserializing it in the same bbpress instance. I don’t do that (on purpose).

(update, actually I have to go back and fix the process with that, I did a quick fix around a bug and fetched $topic each time but that needs to be a global also – all the code used to be in one routine so $topic was only fetched once, but that’s changed – I can fix)

I used meta data because that’s what it’s there for. There is no need on a forum to create extra tables for stuff that won’t be used outside bbpress. I look at all the downsides of poll plugins like WP-Polls and tried to avoid them.

The goal was to use bbpress routines wherever possible for future tweaks. As I go back and cleanup bits of code I can already see where and how to make it more ajax-like (though that’s not a priority).

[dawnsbrain]

Yeah, it’s pretty niche, but there are a lot of art teachers out on the web, and not a whole lot of places for them to converse. bbPress has allowed me to provide the hands-down best-looking and best-behaving forum for them. I’m doing my best to get the word out now. I’ve had a few bites, but it’s slow-starting. Any ideas for further promotion would be much appreciated.

artteacherforum.com

Dawn Pedersen

Web and Graphic Design Teacher

Grades 9 -12

Sacramento, CA

[M]

Hmmm. Let me take a look.

Either $r1 and $rw need to be switched, or $r1 isn’t an array.

Edit:

Lines 358 – 360 should contain the following:

$r = (array) $bbdb->query( "SELECT * FROM ~$bbdb->menu~ WHERE ~set~ = 'active' ORDER BY ~order~ ASC" );



foreach( $r as $rw ) {

Replace the ~ with backticks. I don’t know how to escape backticks in bbPress.

[Null]

Hmmm got this error:

Warning: Invalid argument supplied for foreach() in /home/sites/site116/web/bbpress/my-plugins/bbmenu.php on line 390

the foreach:

foreach( $r1 as $rw ) {

Null

[_ck_]

I highly doubt most bbpress installers will continue to use the default template longer than a week or two. It’s a very sterile 1990’s computer room look, green/white, wide & empty. Ugh.

Reminds me of that old school continuous computer paper:

http://www.jwodcatalog.com/imgLg/753000NIB0342.jpg

I can’t wait until bbpress gets some critical mass of users so we have all those thousands of creative wordpress folks slaving away on themes.

---

On a programming note, I’ve got to figure out how to trash the post data that’s sent so when doing a refresh after voting the browser doesn’t nag the member that the post data will be resent (it won’t affect the poll stats if it does but still I don’t want that post data there). Probably have to do a redirect after submit which is a shame as it has to load bbpress twice then.

[aslan41]

hi

[_ck_]

Ah I see.

Well everyone can work on making it pretty – it’s very easy to do and I’ve laid it out fairly cleanly (css at the top).

As far as ajax, this will be my learning project, I only know the basics. But I have a strange style in that I like simple = better, so I’ll have to do some research. I also want to use the default bbpress javascript libraries unless I can do it somehow without dependencies.

Fortunately I have an idea on how to do it. Don’t hold your breath though, might be a couple weeks or more.

[mazdakam]

You should really change the default colors to something compatible with bbPress… it’s easy to change them, but still.

i agree with i! vey bad color

[howtogeek]

It works!

You should really change the default colors to something compatible with bbPress… it’s easy to change them, but still.

Very good work otherwise… I’ll play with it some more.

[raumgleiter]

I have the integration working. Got wordpress in the root and bbpress in a subfolder called /forum.

When I register on wordpress, the user is displayed as subscriber in WP and as member in bbpress. so all is correct.

But if I register on bbpress, then the user is “member” in bbpress but in WP it gets no role at all.

Second problem is that bbpress doesnt seem to send out any confirmation email although I can see new users in the backoffice.

BOTH plugins are installed and seem to be working fine.

[_ck_]

Since I can’t edit the first post here I’m just going to use my wp blog for updates:

bbPress Polls plugin

v0.11 is a bug fix:

http://ckon.wordpress.com/files/2007/08/bb-polls.txt?v011

[_ck_]

Installing it will definitely answer all your questions.

Many answers are yes. The current options near the top will give you an idea.

I designed it from the start to allow votes on multiple selections or single section – the poll creator can decide.

bbpress cleans up the topic meta on its own, so if the topic is deleted in theory the meta is deleted (but bbpress doesn’t really delete topics yet, it just flags the differently)

you can decide if polls close with the topic or not

you can also decide if the poll is shown on each page of the topic or just the first

only members can vote – I do not have any plans to implement non-member voting, it defeats the purpose and makes the code much more complex

Eventually I will do more than horizontal bars which will make a higher load (I am sure I can find an existing easy library). Bars are currently done in pure CSS which makes it lightning fast and completely customisable with colours and even rounded corners with images.

[Null]

Some questions:

Vote, more then 1 option possible option? (max setting like classic (just 1 option possible) 2 options, 3 etc

If a topic is deleted, does it clean-up the poll as well? (since a real deletion isn’t happening in bbPress, this wouldn’t be a problem for now)

What happends if a poll is deleted? (but topic still excists)

Who can vote? All? Members?

If a topic is closed, automaticly close voting aswell?

Results are in horizontal bars? Perhaps option to show them like a pie (or even vertical bars) Even better if a user can choose this when seeing the results:

Option result 1: ===============

Option result 2: =====

Option result 3: =========

Show as bars | Show as pie

Would like to see a demo, cause can’t test this at work

Greetz

[_ck_]

Oh… you’re hacking the core, that’s easy but not good.

I am desperately trying not to touch the bbpress core which was a huge mistake I did with wordpress and made it impossible to upgrade even when there were critical security fixes.

bbpress is in such a state of flux right now it would be crazy to hack the core, updates with major changes can be expected almost every other month.

I’ll put this on my scary growing list of things to look at. To be honest it’s not a huge priority but you might want to seriously consider my idea of messing with the topic_status flag. You already are halfway there.

[_ck_]

I am pleased to announce a new bbPress Polls plugin.

Your members can now add polls to their topics, or optionally you can allow *anyone* to add a poll to *any* topic, within a specified time period (hours) since the topic was started.

bb-Polls allows single answer or multiple answer polls.

No template edits of any kind.

There are no additional db tables added, it uses bbpress topicmeta only. Only one entry is created per poll, regardless of size or options (this allow very easy cleanup if desired for some reason).

This is a *very* early beta, however should be functional except for:

1. missing admin menu (coming soon – edit plugin directly)

2. missing administrative editing of existing polls.

3. missing some visual tweaks (plural case, etc.)

4. missing some more deluxe options (poll ending time, etc.)

5. missing multi-language support (coming soon)

If you can live with these limits and would like to help test and give me some useful, constructive feedback, please download:

http://ckon.wordpress.com/files/2007/08/bb-polls.txt?v010

(rename .txt to .php, install, activate, start a new test topic)

The beta is set so only moderators and above can create/see the polls. This will allow you to test without disturbing visitors.

Please note the visual styles may be WAY off for the default template or your own template. Unfortunately I am using a very customised template. You’ll probably have to edit the built in css which is kept clearly at the top. (the default styles will be fixed soon when I get a chance to do a trunk install this week)

Upcoming features include the ability to display all polls and the ability to display a poll anywhere within bbpress templates.

ps. I need to know if this works as in in the trunk version – I don’t see why it wouldn’t but you never know…

[howtogeek]

I haven’t tried the trunk yet either… I just opened my forum a week ago and I’m trying to keep up with all the traffic and add the most important missing features.

The one thing that is very frustrating is that administration and moderation in bbPress is not only virtually non-existent, but it’s not even all in one place. If I want to delete a user, I can’t do it from the admin panel, I have to go to their profile instead… annoying.

I want a plugin that lets me take a reply post and turn it into a new topic. That’s a sorely lacking feature. Your move-it plugin almost fits the bill, but I have to create a new topic first, and then move the post, and then delete my original post in the new topic, or just make it say “look below, moving post into topic”.

[Sam Bauers]

I think there is a bug in the naming of the hooks….

I’ve reported and patched it:

https://trac.bbpress.org/ticket/717

[netsleds]

Heres one. http://www.netsleds.com/netsleds_forums still working on an image upload thing that the members are patiently waiting for other than that bbpress is EXCELLENT!

[Null]

Hmmm got this error:

Warning: Invalid argument supplied for foreach() in /home/sites/site116/web/bbpress/my-plugins/bbmenu.php on line 390

the foreach:

foreach( $r1 as $rw ) {

Null

[_ck_]

I’d actually make this plugin for you as it doesn’t take much for it to happen – I just wanted to save some time by understanding how you are sending bbpress a predetermined future time and date rather than the current time and date for a new post. I haven’t looked at the core code but I didn’t think it was looking for time/date fields in a new post.

a quick look shows bb_new_post posting post_time as bb_current_time(‘mysql’) – so it’s not even checking if a different time has been submitted, it’s forcing it to use the time it calculates…

[_ck_]

The front page topics plugin was driving me crazy because I really did want to have a different number of topics for the front page, forum pages, view pages, while leaving the posts per topic page alone and not have to hack the core.

But there is a huge flaw in the fundamental design in that if you force bbpress to see a different number of topics-per-page, it will calculate the last post page entirely wrong, based on the page IT’S ON, vs the destination page.

ie. front page set to 50 topics, posts-per-topic-page set to 25, last post is #30 on the page -> bbpress will calculate the page number for the last post as PAGE ONE off the front page, because that’s what the topic count is set to for the front page.

This got me really annoyed so I researched the heck out of it and figured out this trick – it’s nasty but works (for 8.2.1 at least).

so in config.php you’ve got

// The number of topics that show on each page.

$bb->page_topics = 20;

now you can make a plugin with this, edit each page limit to your heart’s desire (anything without a $limit defined uses the config.php default)

function custom_topic_limit($limit) {

switch (bb_get_location()) :

case  'front-page':  $limit=45;  break;

case  'forum-page': $limit=35; break;

case  'tag-page':  break;

case  'topic-page':  break;

case  'feed-page':  break;

case  'search-page': break;

case  'profile-page': 	break;

case  'favorites-page': break;

case  'view-page': $limit=50; break;

case  'stats-page': $limit=50; break;

case 'login-page': break;

default:  $limit=20;

endswitch;

return $limit;

}

add_action( 'bb_get_option_page_topics', 'custom_topic_limit' );



function fix_post_link ($link,$post_id) {

remove_action( 'bb_get_option_page_topics', 'custom_topic_limit' );

$bb_post = bb_get_post( get_post_id( $post_id ) );

$page = get_page_number( $bb_post->post_position );

return  get_topic_link( $bb_post->topic_id, $page ) . "#post-$bb_post->post_id";

}

add_filter( 'get_post_link','fix_post_link',10, 2);

The magic is in fix_post_link where it trashes whatever incorrect calculation that “get_post_link” has now done because of custom topic limits, and relculates it after unhooking the custom_topic_limit.

No core hacks required!

[Null]

A plugin would be best I think.