[_ck_]

In plain english it essentially replaces the need for things like “Sticky:” to be hard coded into templates. Long overdue but at least it got put in there finally.

However when making templates for backwards compatibility, you’d have to detect if that function exists before relying on it.

The only themes I’ve seen that uses it already outside of the built-in default is “K2 for bbPress” (and now my “FutureKind”).

It allows tricks like I’ve done to replace “sticky” with a post-it-note-like yellow rectangle. But it also could be filtered via plugin to change it to a little graphic icon, etc. which was impossible before the function existed.

[chrishajer]

There is a difference between id and class. Maybe you’re using one or the other.

This is a class:

.forumlist {

font: whatever;

}

This is an id:

#forumlist {

font: whatever;

}

You’re using <table id="forumlist-1"> but your css doesn’t contain markup for that (it has forumlist, not forumlist-anything. There is markup for #forumlist, but without numbers. Maybe you could do something like <table id="1" class="forumlist"> or something? That way, the forumlist class doesn’t need to be unique, since each city will sort of look the same, and the id is unique to each city. You still need to add the proper tags in your CSS, #1, #2, #3 for the ids and .forumlist (which is already there I believe.)

Hope this advice is accurate. Let us know if it works.

[lookfab]

Thanks very much for the kind words.

WordPressl, I mock up a few different design options in PhotoShop and when I’m happy there I move to the code. Since this was my first exposure to bbpress I ended up iterating between PS and the code a lot as I got to understand bbpress better. The challenge was to keep the flavor of the blog, but still make it clear to the user that they are somewhere different.

The mechanics of the template are similar to the default theme. The different look is achieved mostly through the CSS stylesheet. One major change to the layout is to add a floating div for the sidebar on the left. All the rollovers are CSS. I do the tabs simply in php by checking which forum the user is in and displaying the tab bar appropriately. Most of the other changes are actually about hiding some of the power of bbpress.

I’m glad the “tabs” resonate. I had a full working site in beta without them, but just wasn’t happy. The breadcrumb is a little subtle (particularly for folks who are new to a forum), and with only 4 forums and no sub-forums seems like overkill. But without the breadcrumb the user is lost once they’re in one of the forums or topics. The tab solves that and makes it easy to get to any forum from almost everywhere.

[mikelothar]

I hate to bump this, but i’m kinda stuck at the moment with the coding until this issue is solved. Alternatively, where would i expect to be able to find this code in the core files?

[Burkie]

have tried the default rewrite rules

<IfModule mod_rewrite.c>

RewriteEngine On

RewriteBase /

RewriteRule ^forum/([^/]+)/page/([0-9]+)/?$ /forum.php?id=$1&page=$2 [L,QSA]

RewriteRule ^forum/([^/]+)/?$ /forum.php?id=$1 [L,QSA]

RewriteRule ^people/([^/]+)/page/([0-9]+)/?$ /topic.php?id=$1&page=$2 [L,QSA]

RewriteRule ^people/([^/]+)/?$ /topic.php?id=$1 [L,QSA]

RewriteRule ^location/([^/]+)/page/([0-9]+)/?$ /tags.php?tag=$1&page=$2 [L,QSA]

RewriteRule ^location/([^/]+)/?$ /tags.php?tag=$1 [L,QSA]

RewriteRule ^location/?$ /tags.php [L,QSA]

RewriteRule ^profile/([^/]+)/page/([0-9]+)/?$ /profile.php?id=$1&page=$2 [L,QSA]

RewriteRule ^profile/([^/]+)/([^/]+)/?$ /profile.php?id=$1&tab=$2 [L,QSA]

RewriteRule ^profile/([^/]+)/([^/]+)/page/([0-9]+)/?$ /profile.php?id=$1&tab=$2&page=$3 [L,QSA]

RewriteRule ^profile/([^/]+)/?$ /profile.php?id=$1 [L,QSA]

RewriteRule ^view/([^/]+)/page/([0-9]+)/?$ /view.php?view=$1&page=$2 [L,QSA]

RewriteRule ^view/([^/]+)/?$ /view.php?view=$1 [L,QSA]

RewriteRule ^rss/?$ /rss.php [L,QSA]

RewriteRule ^rss/forum/([^/]+)/?$ /rss.php?forum=$1 [L,QSA]

RewriteRule ^rss/people/([^/]+)/?$ /rss.php?topic=$1 [L,QSA]

RewriteRule ^rss/tags/([^/]+)/?$ /rss.php?tag=$1 [L,QSA]

RewriteRule ^rss/profile/([^/]+)/?$ /rss.php?profile=$1 [L,QSA]

</IfModule>

[chrishajer]

Can you post your modified rewrite rules, the ones that did not work? You should be able to make any link with topic.php appear in the URL as people.

[Sam Bauers]

> so an existing forum with 1000 users will have to instruct every single one to clear their cookies

Not necessarily, it just may be an issue if your cookies weren’t expired already.

> I wonder if this has to do with the hard coded hash I have set in bb-config.php

> How does this affect a setup with a shared login from wordpress where you have to match the same hash it has?

You will need to also run WordPress trunk to match the cookies and hash methods up. WordPress has also migrated their cookies and password hashes in trunk.

> hope there was a good reason to fiddle with it

Judge for yourself, we followed WordPress’ lead:

https://trac.wordpress.org/ticket/5367

[_ck_]

Ugh, so an existing forum with 1000 users will have to instruct every single one to clear their cookies – meaning at least 50% won’t understand and try to contact the forum operator personally.

I think there is a better way – perhaps an upgrade plugin that can detect the out of date hash and instruct the client to delete the old cookie and redirect back to the login.

Actually, wouldn’t bbpress replace the hash data in the cookie upon login? None of this sounds right – I created a new user under 1075 and was still unable to login.

I’ve gotten build 1006 to work properly so I guess I will try another investigation into the upgrade from there tonight. I wonder if this has to do with the hard coded hash I have set in bb-config.php

How does this affect a setup with a shared login from wordpress where you have to match the same hash it has? I had the integration working just right, hope there was a good reason to fiddle with it.

[Olaf Lederer]

Hello,

just updated my forum to the latest version (0.831) and found this new function in several template files:

bb_topic_labels();

after uploading the file I can’t see what’s changed, what is this for a function?

Olaf

[mazdakam]

it has conflict with code tag so i decide to disable it

[mazdakam]

Nice i am now use it

works great

[Sam Bauers]

You know that both cookie and password hashing have changed? You may need to clear your old cookies manually to make way for the new ones. Send a mail to the dev list or hit us on IRC in the #bbpress channel and well work out what’s going on.

We’re acutely aware of how spammers attempt to “fool” Akismet. There are steps being taken now to help improve the processes involved in combatting this. Remember that we are users of Akismet too, so have an interest in keeping it ahead of the game.

The nature of Akismet’s purpose means that back-end code needs to remain closed. If spammers knew how it worked, it would likely make it possible for them to game the system. Of course it is opt-in, so if you don’t like it then you don’t have to use it. Controlling the data that is passed to Akismet is controllable from the client end using plugins that can limit it’s behaviour. These already exist for WordPress, bbPress ones could be easily developed too. If there are hooks missing to make that possible then we’ll add them.

[_ck_]

I’ll probably be forced to join the dev list to try to solve this but I just tried moving from 951 to 1075 and I cannot get the logins to “stick” (ie. logs in and then acts as if it is not logged in)

Seems like the old cookie path issue but I’ve looked the cookies and the code and everything seems healthy. Even created a new user with 1075 and that user cannot login either.

eta: 1006 does not exhibit the login issue

ps. don’t kid yourself with Akismet stopping spam. Spammers just escalate their deviousness on what they can get through it. My wordpress.com blog gets spam almost daily now, bleeding right through Akismet. And Akismet hasn’t been given peer-review for privacy/security issues such as passing every single message entered on every single blog and bbpress through automattic – even for private posts and private sub-forums. Won’t make for good headlines when people start to think about it.

[Sam Bauers]

You are right, 1075 is probably the most stable release for “cutting-edge” users, but we would appreciate testing of trunk during integration of BackPress.

We do intend to experiment with PingBacks and TrackBacks in topics via XML-RPC, and you could be right about spam, but we won’t know until we try. We will build out the spam tools provided by Akismet to try and meet the challenge of spam at the same time. There are also other ways in which we can utilise XML-RPC besides those two features which you may not have considered, we already have some cool ideas about user integration and content aggregation that should be driven by the needs of the hosted project. I hope you don’t leave us just for giving it a whirl

The “Press” names are mostly about branding and the they need not be taken literally. We can leverage a lot of good-will by associating with WordPress, and we intend to create better ways to integrate the two projects, regardless of where they are installed or hosted.

[Sam Bauers]

Things may be a bit confusing at the moment with two new and different names flying around. I’ll do my best to clarify things and we can use this topic for everyone to ask questions on the subject and provide input.

For those who are interested, the first thing to do is read this post (and the articles it links to) in the blog:

The future for bbPress

That post is pretty vague about things. So let me be more specific here. First, I’d like to make it clear that bbPress is not being replaced or abandoned or drastically changing direction. As for the two new names that have been mentioned, I’ll cover them below.

BackPress:

bbPress has a lot of shared code with WordPress. BackPress is the name of a new project which is attempting to normalise this shared code into a set of generic files that will simply plug in to both projects (and potentially others). This allows us to leverage the testing and improvements made to this shared code without the overheads of manually merging changes. This way we can spend more time on bbPress’ unique code and extending new functionality.

TalkPress:

It has been public for a while that Automattic intends to create a hosted forums service based on the bbPress project code. The intention is to make this work much like the existing WordPress.com hosted service for blogs. Matt Mullenweg let it slip that the working name for the project (and not necessarily the service) is TalkPress. We probably won’t talk much about it here, but I can say that the majority of the code written to create this new project will be released as open source. Regardless of the name of that service when it launches, the name of this project, “bbPress”, will not change.

As for the upcoming work for bbPress, I’m happy to elabrorate here:

bbPress code:

Along with the inclusion of BackPress into trunk, there are other things going on. We are in the process of implementing a new taxonomy structure for tags. Improving bbPress’ object cache to make it compatible with various WordPress object cache plugins. Replacing the fairly ordinary “favourites” system with a much more flexible and useful topic aggregation tool, and later on we will be incorporating a set of functionality based around the XML-RPC tools available in WordPress such as pingbacks and trackbacks.

bbPress.org website

The bbPress.org website is due for a clean up. Most importantly, the extend area will be upgraded to include a plugin repository similar in functionality to the one that exists on the WordPress.org website. There is a possibility that we will also launch a theme repository based on the same system. A little later on, we plan to re-design the whole site.

I hope this clears things up a little and I’m happy to answer any questions here. I can’t think of anything, but it’s possible that there may be some things that I can’t say about the hosted service project. Feel free to ask though.

[Sam Bauers]

Repost from the dev mailing list:

As of the last commit at this time (revision 1076), trunk is in an experimental and unreliable state. We are attempting to abstract some functions and classes for easier sharing of code between WordPress and bbPress. This shared code is called “BackPress”, and we’ll probably be mentioning it a few times here and there in Trac and other dev discussions.

[rslater]

not sure how to apply that code.. can you assist

[fel64]

global $bb;

if( isset( $bb ) ) {

//...

}

[d00d13]

“I guess I will go with one of these: https://codex.wordpress.org/Plugins/Forums&#8221;

Where’s the beef?

[chrishajer]

Why not just remove the links to the RSS feeds that appear in the template files? Doesn’t that accomplish what you want?

Like in topic.php in your template you have this link:

<a href="<?php topic_rss_link(); ?>

Just remove that, and remove links like it from the other template files. What am I missing?

[chrishajer]

There is not supposed to be a folder names “topic” – that is done with mod_rewrite on Apache. Can you try disabling mod_rewrite in your config.php and see if it works?

$bb->mod_rewrite = false;

If your forum works after that, then you need to do some work with your .htaccess and rewrite rules, or just leave non-pretty permalinks. But try that first, I think that’s why you’re getting 404 errors.

You didn’t mess up anything I don’t think.

[Andrew]

The most important thing is that I remove the ability to get RSS. Removing autodiscovery is a secondary issue. The template files are easy to modify, I am not worried about that. The private forums plugin did a good job and there is very limited code in there dedicated to RSS. There must be a way to just shut it down with a simple filter plugin.

[chrishajer]

You edited the path out of the error message, but did it include the health_blog part, as well as forum? So it looked like /something/health_blog/forums/forum.php ?

/usr/local/www/vhosts/healthstatus.com/htdocs/health_blog/forums/forum.php

Maybe it’s one directory off or something?

One thing weird about the link to a forum: the URL looks like:

http://www.healthstatus.com/health_blog/forums/forum/healthstatus-forums

when they should look like

http://www.healthstatus.com/health_blog/forums/healthstatus-forums

(I think – is there an extra “forum” in there?)

Can you turn off the mod_rewrite in .htaccess and try it without permalinks? If it works, maybe the rewrite rules are borked.

Try this: $bb->mod_rewrite = false;

[chrishajer]

The bug you have run into is fixed in the latest trunk release, or you can see this thread and this post specifically about the change to make:

PHP Error Messages

It’s been discussed before as well:

https://bbpress.org/forums/topic/warning-invalid-argument-supplied-for-foreach-in-bb-settingsphp-on-line-173

https://bbpress.org/forums/topic/installation-problem-cannot-modify-header-information

It’s just a php warning, and your server is configured to show warnings, so you see it. It does point to a problem with the code, but even with the warning, everything still works fine.

[mikelothar]

Hi

I’m trying to make a new theme for bbPress but i’ve run into a problem. If a user is not logged in, and viewing a topic, he is being told:

Reply

You must log in to post.

The problem i have is that i do wish to have this text shown, but i want to customize it to fit with my theme. And this text is not to be found in the theme files. My guess is that bbPress adds the text from the core files.

Is there a way to add some code to the theme files, without modifying the core files, so that this can be shown the way i would like it to be shown?