It depends how much you trust editors with user records. I would tend to go with this.
Administrator – Key Master
Editor – Moderator
Author – Member
Contributor – Member
Subscriber – Member
As you can see, you don’t need to have one-to-one relationships.
I don’t think there is a reliable equivalent which will work everywhere.
If you are just looking for the current topic’s link then try topic_link() with no arguments.
Permalinks have worked for me on Dreamhost in the past.
You do need to use the same user tables for both WordPress and bbPress to achieve what you are after.
There is no performance difference as far as I know if you use the same key for all your sites. You start hitting restrictions when your total volume gets too high, in which case you might opt for the commercial Akismet license instead.
1.0-beta will have forum categories built in.
Categories will be available in 1.0-beta.
They are available in trunk now – although trunk’s installer is a little broken right now.
Place it in a folder called “my-plugins” (create it if it doesn’t exist). Then go to the admin area and activate the plugin.
@geld_lenen
That’s a fairly serious accusation and warrants an investigation if true. Can you be more specific please?
bbPress does a lot of filtering of user input to avoid these things. What part of bbPress was exploited? A topic, a profile?
Code injection in bbPress installs is usually a symptom of insecure shared hosting, not bbPress itself.
I’m pretty sure that’s not a problem security wise as far as bbPress is concerned.
That code you refer to is being rewritten for another reason at the moment.
You have to explicitly choose “Remember me” when you login. If that option isn’t there when you login then you need to update your template to match the default one in this regard.
I’m pretty sure this was a part of the last release.
Yes, WordPress is changing it’s cookie structure yet again.
We will be up to speed with that shortly.
Keep in mind though that including WordPress inside bbPress is an incredible overhead for what is just a modification to the presentation layer.
The most lightweight solution is to create your own theme in my-templates which extends the default theme. Any file that is not found in your own theme simply falls back to using the default, so your theme could consist of as little as a style.css file (which could itself simply import the default themes style.css – see kakumei-blue theme for an example of how to do that), a header file and a footer file.
What version of bbPress?
Trunk is a bit broken.
The last release (0.9.0.2) should be fine.
Actually, the bbPress secret can live in the database. But you are right that the WPMU one cannot, mostly for login compatibility between blogs within WPMU.
Obviously you should choose your own secret and salt values, not the one’s given above.
@seryi
Cookies in WordPress 2.5.1 are compatible with cookies in bbPress 0.9.0.2
WPMU 1.5.1 is probably only compatible with bbPress 0.9.0.2
@javalizard
You need to upgrade WordPress as well to fix the cookie incompatibility.
@marians
You’ve identified another reason that I had forgotten about. URL customisation that you are talking about is close to impossible under MultiViews.
Based on all these comments I think we will be dropping it. Thanks for the input everyone.
TalkPress is the name of the project to build a hosted version of bbPress. It is currently in development aiming for an initial beta release.
talkpress.com in it’s current state was funny back in January. It will probably change soon.
What versions of each are you running?
You can have that configuration of domains.
You need to declare the cookie domain in each to be “.bootstrappingblog.com” (note the leading dot).
I’ll let mdawaffe know as he controls access to that SVN repository.
We’ll probably add a “functions.php” for themes in the next version.
You might be able to get away with just using your header file in the meantime.
