Yeah. You need to have quotation marks around any font names containing spaces.
(edited)
That would be font-family: "Anything but Comic Sans MS for the love of god";
Note you can also get a whole bunch of font declarations into one statement: http://www.w3schools.com/css/pr_font_font.asp
Those are both the right places. How are you adding the font?
The slug is why-my-kittens-suck.
Slugs are used in pretty permalinks. That bb has two conventions, 1 and slugs, means nothing; they’re just used to denote the difference between using the topic id and the topic name in the url.
Permalinks are a fixed URL for accessing the same resource.
http://example.com/blog/?page=2#post-214 for example is _not_ a permalink because page 2 will probably change and #post-214 may no longer be on it. http://example.com/blog/?p=214 _is_ a permalink because post 214 will always be at /blog/?p=214. Pretty permalinks are permalinks that don’t look dynamic: no ?, = or & in there. It looks like a bunch of directories. For example, instead of /blog/?page=2 you’d have /blog/page/2, instead of /blog/?p=214 you’d have /blog/post/214 or even /blog/2006/11/24/why-my-kittens-suck.
No. Unlike '/bbpressfolder/' (I presume), 'wordpressuser' and 'wordpresspass' are not placeholders for your actual value: they are the literal values you will have there. Check your wordpress cookie; those are what they use. A part of the structure is:
wordpressuser_site-unique hash=your username
wordpresspass_site-unique hash=hash of your password
With his settings, bb should now be using that too.
Don’t grab trunk in an attempt to fix this problem, as that uses phpass password hashing which would break your user tables for wordpress. It may work with wordpress trunk, but, you know, with two trunk releases you may have problems. Be careful.
You’d have to change some core code.
Wouldn’t it be best to mark the entire topic link up? Sounds good, though.
Anyway, for enhancements add a ticket on https://trac.bbpress.org/ and mark it as such. 
Sorry, obviously didn’t pay good enough attention.
Most bb themes right now are hand-rolled. Contact the site owner.
Admin Can Post Anything will work if you remove the line that reads something like this:
remove_filter('pre_post', 'addslashes');
I had the same issue with bbsync and that fixed it. Since I used _ck_’s ACPA code, I assume it’ll work for you, too 
You could apply the style you want for only the first li to every li, then use the + selector to modify it for all li following another li (in effect letting you style only the first one, although it’s annoying that you may have to cancel styles).
li {
font-weight: bold; }
li + li {
font-weight: normal; }
should make just the first li bold. This I think works on every browser, even IE6.
The http://developer.mozilla.org/en/docs/CSS::first-child rule is of course the proper thing to do, but (if I recall correctly) doesn’t work for IE6. (This is what I would do … but I generally have no mercy for IE6 users anyway.)
It’s only possible for topics right now, but hopefully there’ll be meta for everything in the future.
livibetter, if you can separate the logic code from the presentation it’d be even better. You can always put a hook into the template and put the code into a plugin, or use the query filter to find when the topics are being looked for.
Look out for the fact that this will, as far as I know, give you 30 extra database queries per page, that it normally takes about 10 to show a page, and that db queries tend to be the main bottleneck on servers. This will work, but to get rid of those 29 unnecessary queries you need more subtlety.
> This question has been answered on irc by livibetter & trentadams thanks guys.
Why don’t you post it here, where other people may find the answer when they’re looking for it?
You may want to think quite carefully about doing this, as it’s not the simplest of tasks. The key issue is that bbpress does not have the data you want at the time you want it.
Basically bb only looks into the bb_topics table to see what the latest topics are. That tells it what the last post id was, what the last poster’s name was and all that, but it doesn’t tell it what the content of the last post was. To do that, you need to grab the ids of every last post being displayed, then write a database query to get the data from bb_posts. That can (*can*) be done in a single query though I think, much as bb grabs all the topics at once, so it’s not too bad. Then you have the data and can play with it however you want.
So it takes some neat hooking and querying.
Comment duplication fixed, ns gotten rid of as far as I can tell! o/
Actually Ichimanako, I don’t have this problem, I’m not sure why you’re involving me? And the thread you linked to has me posting ‘upgrade to trunk to fix this’ near the bottom.
sheatsb, out-of-date documentation. I didn’t realise people actually read that. You don’t need the files, you don’t need the tag, it’s improved since then.
AlexHertz, it would have been better etiquette to just ask in your original topic if it can be done with bbsync. Starting two debates is rude because it’s spam, but also counter-productive because, well, you’ve got two small debates.
_Any_ functionality can be added to bbsync. It doesn’t do what you’re asking for, however. In addition, ‘moving comments to the forum’ would be pointless, because – and this is core bbsync functionality – replies in the forum show up as comments.
No. If I have news, rest assured that I’ll post them here. Subscribing to the RSS feed may be easiest for you.
Nope. To integrate, the easiest method is to use the wp database.
Nope. Whenever I figure it out.
Feel free to be pushy. I’m still doing it for myself.
At the same time, I do run my own site on bbsync so I am inclined to get it fixed as soon as I can.
