@renai42 – Thanks for the feedback. The great thing about bbPress being open-source is you’re able to fix the things you don’t like on your own with Subversion patches via our Trac.
Sorry you’re finding the CSS to be complicated. There are some compromises we made to be able to make bbPress as good as it can with every possible WordPress theme available. As such, some CSS rules are more strict than others, and we tend to have things wrapped in ID’s to allow groups of content to be styled and/aggressively reset.
The staff here are volunteers, every one of us. We operate under the assumption that if you’re in the code, asking code questions, that you’re comfortable taking on something new and foreign. I’ll defend the code here though, since bbPress’s code is nicely documented and orderly.
Volunteer community members represent the project, but they also represent themselves. If someone’s made you feel bad, that’s between you and them. We’re all adults here, and it doesn’t benefit anyone to talk above or below anyone else; when it happens, it weeds itself out pretty quickly.
Regarding CSS specifically, it’s in the name: it cascades down. This means you’re able to add whatever rules you’d like in the stack, and the browser will interpret those new rules in kind. If it’s not obvious enough to you, that just means you learned something new today. That’s not anyone’s fault, or anything that anyone should be upset about on either side.
Again, thanks for your feedback; if you’d like to talk privately about a specific matter or person, contact me privately (a Google search should bring up multiple ways to do this.)
Saying that it’s obvious isn’t really fair. WordPress works in specific ways for specific reasons; blindly, forcefully overriding it isn’t something to take lightly.
I’m looking at the 404 issue.
This will be fixed in 2.2. It’s fixed already in /trunk.
In my imagination, it’s just the new default thing. Let’s get it working first, see how dramatic it is, and go from there.
Should make it part of the default theme. Thought there was a ticket already; if not, make one and feel free to patch it up. 🙂
Go to yoursite.com/topics ?
Unsticking this. Doesn’t seem like a lot of activity, though I’m still willing to help anyone that wants to take this on.
Punting several tickets to future release to get 2.2 out sooner. 2.2 will focus on user profiles and user roles and capabilities.
You may want to update your bbPress 1.0 forums to 1.1 first, then try again.
If it’s not on the same server, there’s no way to import the data. Copy the DB over, migrate the data, then delete the old DB tables.
I’ll update this topic when it’s available. Until then, assume it’s not.
For what it’s worth, bbPress.org uses less than 500 extra lines of HTML and CSS to look how it does compared to an out-of-the-box install. Pretty minimal planning and effort goes a long way.
It’s probably because they aren’t being assigned any role or capabilities, or they’re given a role that bbPress doesn’t know of. bbPress 2.2 should address some of these types of potential issues, but someone would need to look at your installation to be certain.
Exactly. You’ll want to update to bbPress 1.1 first.
Sounds like a weird bug that 2.2 will address soon.
@trendy0 – exactly right.
It’s not that it’s incompatible, it’s that supporting hundreds of combinations of multiple pieces of software is not something I’m able to do. There isn’t much that’s changed since 2.0, so I’m curious what the problem actually is.
Turn on WP_DEBUG, and see what errors are happening. Check your error logs on your server. There’s plenty of ways to get more detail, you’ll just need to do some investigation. If you find a bug, I’ll fix it.
It’s also capability based, and this is all addressed in 2.2.
All sounds pretty weird, and nothing bbPress would have caused directly; it doesn’t touch media at all.
You’ll want to use WordPress’s actions to manipulate the output of the form. There are also actions on the submission side you can hook into to verify the form data.
I’m working on this now for bbPress 2.2, which I’ll most likely fast-track to address this exact issue. I consider it all a big bug, if not just quickly behavior.
Sounds like you’re running out of memory, or some plugin conflict. bbPress is also only really intended to work with current WordPress versions; once you start mixing and matching versions, you’re on your own to troubleshoot.
This doesn’t seem like a BuddyPress issue. I’ve seen other installs have this issue too. Working on a fix for 2.2, and will possibly backport it to 2.1.3.
