I’ll take a look at it. This will most likely change in the future, and we’ll shift registration and user related functions over to use WordPress.org.
Any chance I can get some screen shots of what’s going on? Some of this is anticipated behavior.
There’s are a few ‘context sensitive widget’ type plugins available for WordPress that would probably be the best places to start.
Confirmed issue in Beta 1. Will be fixed in Beta 2.
Are you using Beta 1, or using the SVN checkout? Since you’re actively finding smaller bugs as you go, it’d be helpful if it were possible for you to switch to running the SVN checkout and get the updates as I commit them.
Added a wrapper to user.php.
The style of this template comes straight out of the TwentyTen theme.
Favorite topics are public in bbPress 2.0, and always have been in previous versions.
Is it possible the reason why they’re appearing for you when you’re logged in, and not for other users (or logged out users) because those topics exist inside a private or hidden forum?
I did find a possible undefined variable situation that could cause an error value to be returned instead of topic ID’s, so if the topics exist in public forums, that code change might fix it.
@dotaleague – There will probably never be a 1.3 version of bbPress. The next standalone version will be 1.1, which will most likely get released along side 2.0.
@dotaleague – There will probably never be a 1.3 version of bbPress. The next standalone version will be 1.1, which will most likely get released along side 2.0.
Fixed in SVN, will be fixed in Beta 2.
Forums *are* categories where topics live. A forum is just a grouping of topics, similar to a traditional WordPress category.
Beta 2 will eliminate the Forum breadcrumb issue you describe.
Never seen anything like this before. You might be able to use the WordPress post-by-email feature, along with bbPress 2.0, and pull something off that way. It’s a neat idea, and something that would still need to be developed specifically for your needs.
Never seen anything like this before. You might be able to use the WordPress post-by-email feature, along with bbPress 2.0, and pull something off that way. It’s a neat idea, and something that would still need to be developed specifically for your needs.
There shouldn’t be too many theme changes anymore. I’ve tried to keep as much logic out of the themes as I could, but in some places there’s a compromise between theme logic and hardcoding things into the plugin. If there’s anyplace where that balance is missed, I’m all ears.
There shouldn’t be too many theme changes anymore. I’ve tried to keep as much logic out of the themes as I could, but in some places there’s a compromise between theme logic and hardcoding things into the plugin. If there’s anyplace where that balance is missed, I’m all ears.
Rather than having a totally separate template file for each topic, why not run some kind function to check which topic is being served, and then use get_template_part to grab the piece you need from your own custom folder? That would prevent you needing to litter the root of your theme with tons of custom files.
Rather than having a totally separate template file for each topic, why not run some kind function to check which topic is being served, and then use get_template_part to grab the piece you need from your own custom folder? That would prevent you needing to litter the root of your theme with tons of custom files.
@Morgan – You should just be able to remove the database tables prefixed with “bb_” and that’s it. You don’t really even need to do that, since the size of those tables is likely very small. That along with possibly your admin user having the “Key Master” user role rather than the “Admin” one. Otherwise, the two platforms don’t really touch each other at all when they are integrated.
I’ll look into this tonight.
The bbp_is_topic() function should definitely exist, as long as bbPress is active. Can you confirm that you still have bbPress active on this site?
@anointed – In a word, no. 
WordPress custom post types only know to look for their files in the root of the theme folder, and the same goes for page templates as well. For now if you want a totally customized theme, those files need to live in the root. I did my best to minimize the number of files in the root, and instead split them up into template parts in the /bbpress folder (because I want the same thing you do.)
It might be possible to hook into the template loader, see what the request is, and force it to look into a different folder, but there’s no possible way to do it at all with page templates; it’s actually purposely disallowed to prevent the theme from having to scan every file inside every subfolder to find them.
@anointed – In a word, no. WordPress custom post types only know to look for their files in the root of the theme folder, and the same goes for page templates as well. For now if you want a totally customized theme, those files need to live in the root. I did my best to minimize the number of files in the root, and instead split them up into template parts in the /bbpress folder (because I want the same thing you do.)
It might be possible to hook into the template loader, see what the request is, and force it to look into a different folder, but there’s no possible way to do it at all with page templates; it’s actually purposely disallowed to prevent the theme from having to scan every file inside every subfolder to find them.
@Halle – The importer can’t merge two sets of user tables together, it can only pick which set to use. In situations where both WP ad bbPress have two different sets of users, you’ll need to do some manual labor in the DB to make things exactly how you want them.
@jarledb – One of the unique challenges of creating a plugin with a large volume of users is catering to the 80% of users that want to turn it on, and not really mess with it. Different people will want different kinds of login and registration areas on their sites, and everyone with an opinion about where to put them why, is right. Some say sidebar, some say in the content area to draw attention to it, some say tuck it in a drop down menu, etc… All great ideas, but what’s the majority? The majority want it easy, and I think widgets are the easiest way to go right now without making everyone have a login/register page on the forum index of their sites.
Regarding ip-banning/anti-spam, you’re probably safe to hold off for a little bit. There’s no doubt these solutions are going to be needed eventually, and if someone takes the liberty of making an awesome plugin to help out, I’m all ears on how I can help bbPress core work better with it. 
