[Sam Bauers]

Only if they choose to redistribute it. If they just run it as a service where the code is never sold to it’s customers – either as source or compiled – then they are under no obligation to release the source. I doubt it serves their interests to release the theme and in my opinion that’s fair enough and in the spirit of the GPL.

Besides this, it is arguable whether they would be bound by the GPL or not. As a theme strictly speaking isn’t a modification of bbPress (it’s just separate code that is compatible with the theme architecture) and the idea of “linking” as stated in the GPL is pretty vague when it comes to PHP applications. It was originally devised to cover more traditional application models where linking to libraries is more clearly defined.

[_ck_]

Correct me if I am wrong but technically under the GPL if they modified an existing template and other plugins to make it work, they are required to make the code available

But we’ll just admire it from afar I guess…

[_ck_]

Gotta love kiwis, looks great!

I doubt bbpress will ever have native image support (you mean inline right?) That’s just too much “heavily lifting” which is always deferred to plugins.

ps. “Tiny”MCE is such a misnomer. It’s 125k of code!

[Trent Adams]

It isn’t available and I doubt they would release it (for branding purposes). It is pretty wicked though

Trent

[Andrew]

Never mind, I think I just figured it out.

<?php echo $_SERVER['REQUEST_URI']; ?>

[Andrew]

Hi:

I’m integrating bbpress with Amember and am embedding a login form in the forum pages. I am looking for the bb_option that returns the current url. This way, after a login, I can redirect the user back to the original page.

It appears the bbpress login code is smart enough to parse the referring page. The amember code needs to be fed this information when the login form is called.

[chrishajer]

edwinfoo: it looks like there’s a problem with the CSS on your site. The #thread li referenced above by fel64 won’t work for you because it looks like you have renamed it to #thread1 (maybe just a typo in your theme.) So, the CSS for #thread won’t apply to #thread1. If you add CSS for #thread1 or remove the 1 from the end of the <ol id=”#thread” in your theme, it works fine (I just tried it.)

This <ol id="thread1" start="1"> needs to look more like <ol id="thread" start="1">.

If you need numbers there for each unique thread, you’re going to have to do it differently, not appending a thread number to the end of the id “thread”: that changes the id from #thread to #thread-(whatever number).

[Andrew]

I can live without integration but it would be nice to have shared header and sidebar code. I just wanted to log my observation in case someone else had the same problem.

I imagine with all the new focus on forum software these issues will eventually get mowed down.

[edwinfoo]

Mine is a integrated 0.8.2.1 installation and I’ve tried all the tips on this page and none have worked thus far

The design can only bear a 600 pixel width limit.

[fel64]

It means that your bb and wp aren’t integrated properly to use one set of functions. You need to put require('path/to/wp') into your bb config file.

[Olaf Lederer]

Sure this “upgrade” is not for current functionality. To make this function clear it would be useful to have a working example in the default template

there are so many unused functions in the include map, why is this unused function included in the default template (makes no sense to me)

@fel64, believe me I know the bbpress files maybe a little too much, hehe…

[chgogrrl99]

Hey Chris,

I owe you a huge apology…I wasted your time.

So, after trying all the various combinations you suggested, I remembered that when I first tried you original suggestion:

<table class=”forumlist” id=”forumlist-<?php forum_id(); ?>”>

that I had put it on two lines. So, the “id” line started with a black (rather than light green) “id.” I thought, “Oh, that needs to be green,” so I went ahead and added < to begin the line.

Obviously I’m learning this stuff as I go. Anyway, I went back, used you original method all on one line without adding the extra < and, guess what? It all validated.

I’m an idiot. Sorry for waisting your time and thanks for making it work.

Oh, also, I didn’t want the “Hot Tags” so I justed cut that entire Div out. Everything still seems to work and still validates, but I worry that I shouldn’t have done that. What do you think?

I signed up for adsense and I’m thinking of putting ad code where hot tags was

[_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.