[chrishajer]

I thought the options for sticky were like this:

[Stick topic (to front)]

Where “to front” sticks it to the front page, and “Stick topic” just sticks it in its own forum. I haven’t done it in a long time so I am unsure if that is the case any more or not. If it’s already stuck, I think you have to “Unstick topic” then re-stick it to the front page.

[Ipstenu (Mika Epstein)]

It’s meant to mark the page as it being a sticky post. You can move it around on your template. I have mine show up after the number of replies so it would be Forum Rules (1 post) [sticky]

Look for <?php bb_topic_labels(); ?> in your topic.php file.

[Ipstenu (Mika Epstein)]

globetrotterdk, you have to look into your wp-config.php file.

On bb-config.php I added in:

define('AUTH_SALT', 'AUTHSALT');

define('LOGGED_IN_SALT', 'LOGGEDINSALT');

Which is exactly the same as in my wp-config.php file. And, obviously, it’s not actually set to AUTHSALT but something like UYwE&#93&We3#

[epiphone]

Hi there,

My bbPress forum (0.9.2) has been theme and databased intergrated, I’ve just decided to test sticky topics, and this occurs on a sticky topic:

http://www.james-blogs.com/forum/topic.php?id=3

What is this [sticky] code doing, Is this meant to be how a sticky topic is identified to someone or is broken bbcode?

Regards,

James

[zulan]

I follow this with great interest since I have almost the same problem. I dont even see the admin admin, I only have one admin and that is my account since if I try to use it I get to edit my profile. I’ve tried entering the path http://www.zulan.se/bbpress/bb-admin/ but it only takes me to the first page

I have checked my AUTH_KEY, SECURE_AUTH_KEY AND LOGGED_IN_KEY and they are for sure the same since I havent changed them. So both my wp and bb config says like this:

define(‘AUTH_KEY’, ‘put your unique phrase here’); // Change this to a unique phrase.

define(‘SECURE_AUTH_KEY’, ‘put your unique phrase here’); // Change this to a unique phrase.

define(‘LOGGED_IN_KEY’, ‘put your unique phrase here’); // Change this to a unique phrase.

[Myron Tay]

I can’t believe I’ve not seen phplist around before. Thanks!

[TrishaM]

I actually have a closely related but slightly different need – I need bbPress to NOT strip out the target if I manually enter it into an <a> tag and, ideally, to also not strip out the rel=”nofollow”

This plugin does add the rel=”nofollow” to links, but I wouldn’t want that added to my internal links, just external ones. But it is not adding the target=”_blank” and bbPress is still stripping it if I add it manually. Again, I wouldn’t want it added for internal links, just external (we want ALL internal (on-site) links to open in the same window, but want ALL external links to open in a new window).

The only way I know of to get this granularity of control is to do them manually, but dang it bbPress keeps removing them.

I agree totally that it’s not good to mess with core files, and I try to avoid it at all costs, but this is a very important issue for us – so if there is no plugin to add this level of control, how can I modify my file(s) to do this? I would happily add a functions.php to my theme and put it there, but am not a good enough coder to write this function myself.

Any suggestions?

[danbbpress]

I just installed this plugin http://bbpress.org/plugins/topic/post-notification/ that automatically adds new posts to an author’s favorites. However, in order for the post’s author to receive a notification email for a new post he/she must also turn on email notifications in the admin area.

My question: is there a way to change the code to have these email notifications turned on by default?

[_ck_]

Also, if you’d like to dynamically add some text to the left (or even the right) of the page links without hacking all your templates, you can use this trick:

// add "pages:" to page links

function text_topic_pages( $text ) { if ($text) {$text="pages: ".$text;} return $text; }

add_filter('topic_pages', 'text_topic_pages');

add_filter('forum_pages', 'text_topic_pages');

This way the word “pages:” appears before the page number links only if there actually are any pages for the results.

[_ck_]

update: I’ve now included this functionality in the topics-per-page plugin so use that instead which is maintained and not this mini-plugin which will not work properly with 1.0a

Here’s something I had made a mental note of quite awhile ago but forgot to do, add pagination to the front-page for the latest discussions. You can see a demo near the bottom of http://bbshowcase.org/forums/

(the following two functions are included in the 0.0.4 version of topics-page-page plugin, so don’t use them if you have that)

add_filter('get_latest_topics_limit','front_page_pagination',999);

function front_page_pagination($limit="") {

global $page;

if (is_front() && $page>1) {$limit.=" OFFSET ".($page-1)*bb_get_option('page_topics');}

return $limit;

}

function front_page_pages() {

global $page, $bbdb;

echo get_page_number_links( $page, $bbdb->get_var("SELECT SUM(topics) FROM $bbdb->forums"));

}

1. add to your front-page.php template

<div class="nav"><?php front_page_pages(); ?></div>

AFTER

<?php endforeach; endif; // $topics ?>

</table>

2. If you use rewrite slugs you MUST add the following rule to your .htaccess file

RewriteRule ^page/([0-9]+)/?$ /forums/?page=$1 [L,QSA]

anywhere before </IfModule>

where /forums/ is the path to your bbpress install.

[chrishajer]

You can create a full plugin out of it, then activate the plugin, or _ck_ likes to create a single plugin for all the miscellaneous tweaks or mini-plugins, then add this to that file. Adding this to a file of other mini-plugins means you cannot activate and deactivate this independently. That works for tweaks you will always want to use.

A plugin header will need to look something like this:

<?php

/*

Plugin Name: bbPress Tweaks

Plugin URI: http://www.example.com

Description: Various tweaks to bbPress

Author: You

Version: 0.1

*/

Add the above code after that, and call the file bbpress-tweaks.php, put it in my-plugins, then activate it in the bbPress admin. It should look like this when you’re done:

<?php

/*

Plugin Name: bbPress Tweaks

Plugin URI: http://www.example.com

Description: Various tweaks to bbPress

Author: You

Version: 0.1

*/

function meta_keywords() {

global $tags;

if (!empty($tags)) {

$keywords="";

foreach ($tags as $t) {

$keywords.=$t->raw_tag.', ';

}

echo "n".'<meta NAME="keywords" CONTENT="'.trim($keywords,", ").'">'."n";

}

}

add_action('bb_head', 'meta_keywords',;

?>

[vadi]

Where can the above code be stuffed, _ck_?

[vadi]

Won’t be changing the domain name, just moving to a new host – but for the time being, the domain name will change temporarily.

Unfortunately I couldn’t find any import/export plugins, and I searched for them again just now… was hoping for a more fail-safe solution than exporting and importing the databases

[Ipstenu (Mika Epstein)]

Jorja Fox: Online and the Forums are finally done.

I’ve had the blog up for a couple years (it got taken down and revamped when it crashed my server with bad code and bad bandwidth usage). No ‘hacks’ involved, though I did tweak some plugins.

Using:

• Akismet
• Allow Images (commented out two lines to allow for images without blowing up code)
• Bad Behavior (the generic file provided by the creator, with a plugin header added to allow it to be pluggable)
• bbPress Smilies
• Comment Quicktags for bbPress (added in my spoiler tags)
• Mass Edit – Moderate Posts
• Spoiler Tags
• Unread Posts

The design is based on the Dignity Theme, and then hacked to kingdom come to make it, among other things, variable width.

[_ck_]

Actually it’s

Options +MultiViews

note the plus.

But multiviews is not the preferered way of doing it and some hosts don’t support multiviews.

Instead, use the method in step #3

Oh and most importantly,

$bb->mod_rewrite = true;

will only do numbers.

$bb->mod_rewrite = "slugs";

does the full topic title.

[_ck_]

timskii, that makes a nice little plugin:

function meta_keywords() {

global $tags;

if (!empty($tags)) {

$keywords="";

foreach ($tags as $t) {$keywords.=$t->raw_tag.', ';}

echo "n".'<meta NAME="keywords" CONTENT="'.trim($keywords,", ").'">'."n";

}

} add_action('bb_head', 'meta_keywords',;

[chrishajer]

Then something is not working

[_ck_]

I believe 1.0 has 404 support like WP does but the unthemed die page is something I’ve complained about for over a year now to no avail. They just don’t want to add a hook for it so you would have to hack the core to change it unfortunately. It’s really unprofessional.

essentially in functions.php

find function bb_die( $message, $title = '' ) {

and change

bb_install_header( $title );

to

bb_get_header();

then change

bb_install_footer();

to

bb_get_footer();

One easy way for them to solve this is to move bb_die into pluggable.php, so Sam if you are reading this?

[agitainment]

Hi, there.

I have been able to get numeric pretty permalinks to work on my bbpress site (http://agitainment.com/ics/forum/) but not the name-based permalinks, which is what I’d like to have.

I’m using 1and1 hosting, and I followed the setup at http://bbpress.org/documentation/faq/#pretty-permalinks. I added Options -MultiViews to the top of the code generated by /bb-admin/rewrite-rules.php in my .htaccess file (as detailed at http://bbpress.org/forums/topic/dropping-multiviews-support#post-16050). In addition I have set $bb->mod_rewrite = true in my bb-config.php. My forums are in the same database as WordPress.

Any idea on how to get the name based permalinks working?

Cheers.

[_ck_]

You can make my bb-benchmark work on WordPress with a few changes.

Most notably you’d have to add the line:

add_action('wp_footer', 'bb_benchmark_output',999);

if (bb_current_user_can( 'administrate' ) ) you just have to take off the bb_ part and make it current_user_can

Oh and all $bbdb has to be changed to $wpdb

It won’t be able to calculate the timing between sections until all the hook names are added which unfortunately I don’t have the time right now to lookup. But it will still show you overall times and mysql queries.

[_ck_]

You are getting an error with admin_email because in bbPress 0.9 they decided to change it to from_email with no support for the old variable (bad move). That plugin obviously never got updated.

[_ck_]

That’s better but your query counts are still too high.

Way too high.

You could post the list of queries from bb-benchmark here and I can take a look at what’s causing that.

eAccelerator is probably the way too go.

It’s a tad slower than Xcache but it’s far more stable.

Assuming you are using a 2ghz+ cpu that is only lightly loaded, you should be seeing page render times around 100ms on an optimized setup with proper mysql and php opcode caches.

[peterve]

have a look at the forum now (http://forums.corelan.be:8800)

runs a lot faster now, doesn’t it ?

I have made a couple of changes to the php.ini file :

register_long_arrays=off

output_buffering=4096

variables_order = “GPCS” (still need to verify that this doesn’t break stuff)

disabled

engine=on

closed & saved the file, and php runs must faster now

(windows 2008, IIS7)

Also, one of the plugins that I’m using (EnhancedRegistration) was reporting repeated errors in my php log file

“bbPress ER: Failed to send report”

I looked up the function, replaced the bb_get_option(‘admin_email’) with a static email address, and now the errors went away as well

Not sure whether this has improved the code as well, but it certainly couldn’t hurt, could it

wtih regards to the opcode cache : what would you recommend using ?

[_ck_]

By the way, even when we fix the plugin problem, your setup could benefit greatly from a PHP opcode cache (eaccelerator, xcache, APC, etc.) We just have to find one that’s compatible with Windows and IIS which will take some research. It should cut your page times in half, on both bbPress and WordPress.

Here’s one possibility:

http://www.sitebuddy.com/PHP/Accelerators/eAccelerator

That site has pre-built windows binaries for eAccelerator as well as good install directions.

[Ipstenu (Mika Epstein)]

I ‘fixed’ it by commenting out the following lines:

// remove_filter( 'pre_post', 'encode_bad' );

// add_filter( 'pre_post', 'allow_images_encode_bad', 9 );

// add_filter( 'pre_post', 'allow_images', 52 );