bbPress.org

Here’s a mini-plugin I whipped up to fix the behavior of bbPress where a sticky that is made to “stick to front” (aka “super-stickies”) gets removed from its original forum.

Instead, now it will show as a regular sticky in its original forum but also as a super sticky on the front page.

<?php

/*

Plugin Name: Super Stickies Fix

.................................................................................................................

*/

function super_stickies_fix($where){return str_replace("topic_sticky = '1'","topic_sticky > 0",$where);}

add_filter('get_sticky_topics_where','super_stickies_fix');

?>

Tested in bbPress 0.9, in theory it should work fine also in bbPress 1.x

You can remove the line of all dots, it’s just there to fix the wrap problem for code on bbpress.org 2.0

Chris,

Akismet issue again!

Also do you check for modlook tag here? https://bbpress.org/forums/tags/modlook

I’m trying to install bbpress on my site.

I have wordpress installed at the root, have uploaded the bbpress folder and started the config.

Once I’m at the last step I get a page of white text on a white background with the attached errors (Theres several pages of the fwrite() errors)

At the bottom of the page it states the installation completed and the log shows no errors.

This is a virtual host, IIS6

Warning: fopen(C:InetpubvhostsXXXXXhttpdocsbbpress/bb-config.php) [function.fopen]: failed to open stream: Permission denied in C:InetpubvhostsXXXXXhttpdocsbbpressbb-adminincludesclass.bb-install.php on line 1044



Warning: fwrite(): supplied argument is not a valid stream resource in C:InetpubvhostsXXXXXhttpdocsbbpressbb-adminincludesclass.bb-install.php on line 1051



Warning: fwrite(): supplied argument is not a valid stream resource in C:InetpubvhostsXXXXXhttpdocsbbpressbb-adminincludesclass.bb-install.php on line 1051



Warning: fwrite(): supplied argument is not a valid stream resource in C:InetpubvhostsXXXXXhttpdocsbbpressbb-adminincludesclass.bb-install.php on line 1051



Warning: fwrite(): supplied argument is not a valid stream resource in C:InetpubvhostsXXXXXhttpdocsbbpressbb-adminincludesclass.bb-install.php on line 1051

How do you change the name in bb_new_topic_link()

or it’s okay to just do

<a href="?new=1">New Topic</a>

Hi all.

We have numerous sites running on WP but this is my first go at bbPress. Even if I I’ve heard the community so dissapointed with the slow development of bbpress (as opposed to WP) and even if I am very concerned that WP 3 is “round the corner” and everything might change… I decided to give it a try for a new site very forum orientated + small review section (which I plan to do via a wp review plugin).

By mistake installing via SVN i installed and configured 1.1 alpha from the trunk which was not originally my intention. Everything seems fine for now… so my question is if I should revert to the 1.0 stable branch (are there many differences with the 1.0 branch) or this apha version is “safe enough” to get going.

Also if anyone has details about if bbpress-wp integration is changing dramatically on WP3 and I am just wasting my time… please let me know.

Many thanks.

I’m having problems with images not appearing properly in my bbpress install. The url is http://forum.allykatdesign.com. The header image is not appearing and the thumbnails in the themes>appearance section are also appearing as broken links.

Any help would be greatly appreciated.

When I change the user roles in WordPress the change does not transfer over to bbPress, and vice versa. I can still change the roles, but I have to do it as two places, which makes the whole integration worthless.

Registrations in WP transfer over to bbPress (and vice versa) and logging in to WP let you login to bbPress so the cookies are working correctly. However new WP registrations does not assign a role in bbPress (unless I use the plugin).

I have assigned the role map. I am using the bbPress Integration plugin. Not using deep integration. I have done pretty much every thing I could think of, but it’s not working.

I’m using WP 2.9.2 and bbPress 1.0.2. WP and bbPress is sharing the same database.

I just integrated my wp with bbpress and its working wonderfully, however, now i’m wondering if I should still be using the “automatically upgrade” feature in wordpress when they release a new version of it. I routinely do that. I currently have the most up to date version, but I’m wondering if I do that in the future if something will break now that I have this integration setup.

The integration instructions I followed were here:

http://wpbbpthemes.org/integration/

We have our bbPress forum hosted at Network Solutions [unfortunately]. When we activated SSL in bbPress, any SSL-secured page would immediately go into an infinite redirect loop to itself. After a little PHP debugging, I determined that the cause was two-fold:

1. $_SERVER does not exist, for some reason, at NetSol.

2. $_SERVER always returns 80 at NetSol, even when accessing the site via https. It should return 443.

This causes the two conditions in the is_ssl() function to fail, so the function incorrectly returns false. When the secured page redirects itself from http to https, bbPress still thinks it’s an unsecured page and redirect back to itself again… and again… and again.

We had no choice but to hack the core, which is bad because it will get overwritten when we upgrade bbPress. is_ssl() resides in /bb-includes/backpress/functions.core.php. I added a condition to simply look at the scheme of the URI and return ‘true’ if it is ‘https’.

I added this line to the first line of the function:

Then this add’l elseif condition:

Has anyone else ever experienced this at NetSol?

Hi there, after installing and integrating bbpress on our WordPress site, the “news” page which is the blog portion of the site only shows partial content, of the last post created, not showing any of the “blog” stuff like date, author, sidebar, etc. Here’s the address if that may help: http://www.apps4good.ca/news

Would appreciate any help!

Thanks,

Ian

PS. I’ve installed bbpress again with no integration at /forums (previously /forum).