I deleted the default admin account on my WordPress site after I gave another user admin access. I just found that I can’t access my plugin menu or settings in the integrated bbpress forum with that user(not deep integration). I have access to the database so is there any way to make my admin user a key-master again? If not is there any way I can get access to those menus again?
Using Wp 3.0.1 and BBp 1.0.2
Very nice work! Thanks for sharing it.
I love how you used the ability to only change certain files and let it fall back to the originals as the default. I don’t think many people realize you can do that.
Never mind! I’m just going to create a separate database 
Yeah it happened to me earlier when I try to reinstall. However, I’m sharing this with my WordPress database. How to fix?
Thanks Chris!
Somewhere, you either called the folder “forums” or typed that in to the installer. I get redirected when I try accessing some things (like the stylesheet.)
If you have nothing of value there yet (no topics or replies) I would just reinstall and be sure your URL and directory have the same name in them (i.e. a folder called bbpress, and the URL has bbpress on the end.)
To reinstall, you will need to drop the bb_ tables from the database, otherwise you will get an error “bbPress is already installed.”
Sorry, it should be /bbpress for both. BUT thats the weird thing, when I type in bbpress/bb-admin to access the admin, it takes me to the above URL.
How come you have bbpress in one URL and forums in the other? Did you specify the location as one, but actually have it in a folder called the other? Both the folder (directory) where you installed it, and the information in the installer need to be the same. I would suggest using forums in both places (because who cares what forum software runs there really, right?)
Hi John,
I don’t know why after all these years that there is a refusal to put a clear and defining sentace saying that this isn’t part of the default bbPress package. It casues so much confusion for new users.
bbPress is a totally separate standalone forum, that can integrate user sessions (login/log-out) with WordPress. Nothing more. Its important to keep that in mind because it’ll save alot of thinking from a wordpress point of view.
That said, theming bbPress is quite simple as long as you know 1 thing: bbPress won’t run WordPress commands/functions/API calls.
Copy your default bbPress theme (the rather lacking Kakumei), rename it both in folder and in the template information held in the style.css file contained within.
You now have your own bbPress theme. Congrats.
The next step is simply to copy/paste the HTML you want to replicate from your WordPress theme into your bbPress theme. If you’re not doing any special processing, I strongly suggest copy/pasting the loaded/outputed HTML from when you load your WordPress homepage in a browser.
If you want to copy/paste from your header.php file in your WordPress theme, remember and take out all of those pesky WordPress functions, and replace them with bbPress equivalent or hardcoded information.
If you’ve ever made your own WordPress theme, you’ll find bbPress follows a very similar path/structure.
Good Luck
Any theme file, yes. If the file is not present in your theme, the missing file from the default theme is used instead.
Copy the register.php from the bb-templates/kakumei/ folder into your theme folder. If you don’t have a theme file present in your theme, the file from the default theme is used. Since that’s happening now, go ahead and copy the register.php into your theme folder and make the modifications there.
Interesting… so assuming my templates were default… where would I look for the code to add this? I can get in there and add it if I knew what it looked like.
Oh 
I wish all us other users could have it like this.
I view this support forum as sort of the default showcase for what bbpress is.
While the WP backend is “pretty”, in WP it has to be because users are exposed to it for some crazy reason, and of course it breaks with the entire default theme of the site.
How much time do you spend in the admin section, does pretty really matter?
bbPress (standalone) solved the admin menu problem with users by making advanced profiles. Unfortunately bbPress (plugin) will revert right back to the WP problem.
That said, the admin section could be much more disconnected from the main program anyway, so it can be developed by different people at a different rate with different theme possibilities.
It might even be possible to “theme” the admin section like the regular site theme.
Yes you can, easily.
I have a mini-plugin for this somewhere around here…
Here you go:
<?php
/*
Plugin Name: Delete Own Post
*/
function delete_own_post($retvalue,$capability,$args) {return ($capability=='delete_post') ? bb_current_user_can('edit_post',$args[1]) : $retvalue;}
add_filter('bb_current_user_can','delete_own_post',10,3);
?>
Note that they can only delete for as long as they can edit.
Meaning after the 1 hour default, no more delete.
But you can change the timeout in the admin settings.
I’ve installed an integrated WordPress 3.0 (NOT MU) and the latest BBPress. When users register with WP they can not add any reply or start a new post in the forums.
I tested this with the default unaltered theme and same thing.
Looking in the DB I see that each member is a “member” in WP but there is no BB_METAUSERS table for bbpress. I think this isn’t required when an integrated solution is installed.
Any idea why all new members are set to “Inactive”?
J
Hello _ck_, thanks for the reply. Unfortunately this option is not working for me.
My steps were….MKDIR>my-plugins/>new folder>custom-registraton-email.php>copy and paste the plugin you provided>activated>still getting the same registration default email.
The plugin is Add bbPress Default Role. It’s three lines of code so you may be better just writing it into your functions.php file.
WordPress today cannot run a live site without caching.
You’ll get kicked off any shared hosting in a heartbeat.
This is a HUGE regression because there are times when a page cannot be cached. I was looking at mashable the other day – it uses over ONE HUNDRED AND FIFTY queries per page. It would be slaughtered without a super dooper amount of caching.
But bbPress 0.9 is fully capable of taking loads without any caching at all. I know of a few large sites that use it without any caching, it just doesn’t need it if properly configured until you get to slashdot level loads.
So in what fantasy world does anyone believe that adding the load of bbPress as a plugin to WordPress’s existing burden will ever make it faster than 0.9 ?
WP 3.0 already requires the increase of PHP’s default memory allocation per instance (over 32M in some cases). bbPress 0.9 runs in less than 1M (with a whole bunch of plugins at that).
If being more attractive to the WP masses was important, what should have been done is a project to make standalone bbPress’s integration with WP easier. Perhaps mimic WP’s template actions, etc. so WP templates could be used with less modification.
But like backPress, I’m afraid it’s probably too late.
I’m not saying this to be mean Matt, but the reality is Automattic is becoming a one-hit-wonder with everything being folded back into WordPress.
(and if a bbPress as plugin with WordPress backend goes down for any reason, failed upgrade, security hit, etc. now so will your forum)
Is there a better option than gravatar for making avatars? I like gravatar, but most novice users still can’t figure it out. Also – are there better options for profiles in general? Are there plugins where people can add real information to their profile pages, not just the bbpress defaults? I don’t need much, just a little more than is there now, like a bio and whatnot.
Oh wow. I’m an idiot.
Very sorry to put you through that – the version on bbpress.org is out of date!
It only does version 1, not version two.
I’ve just posted 0.0.4 which does version 2 (now set to default)
don’t forget to copy over the four define lines!
This is always updated faster than the copy in the plugin section.
https://plugins-svn.bbpress.org/freshly-baked-cookies/trunk/
When editing a reply, the “Notify me of followup posts via e-mail” text appears twice (once below the “Allowed markup” and once above.)
I think this is related to theme, I didn’t happen on my installation with Kakumei.
This means that the theme here doesn’t contain edit-form.php and is using Kakumei’s. In the patch I posted, the action (to add the checkbox) is removed in functions.php and is instead added at a custom location in Kakumei’s edit-form.php, and as functions of Kakumei aren’t loaded here, the default action isn’t removed and the checkbox is displayed twice. This doesn’t happen with post-form.php as it is present here.
Shared-hosts are the bread and butter of WordPress usage. The good news is servers are way more powerful than when I wrote the first bbPress, and we can take advantage of that to provide a richer experience.
I like the idea of plugin-centric development from a theoretical point of view, and obviously plugins have been at the core of WordPress’ success, but I think it can be taken too far and take away from the user experience.
It’s about taking responsibility. Even though you could break down almost every feature of WordPress into a plugin and distribute everything bundled, and even activate a bunch of them by default I think you lose a “buck stops here” for other developers to target. The uncertainty of testing the interactions of N factorial plugins is daunting and gets untenable quickly.
Better to draw a line in the sand and promise the user “these things will always work together.”
It’s a natural tension. I think the best way to split the difference is to keep the core lean and mean, and then to have a set of pre-packaged plugins that are included in the main download that can be turned on (or can even default to being on).
This gets my vote as well. Instead, I would prefer the next version of bbPress to have more powerful admin features (see Kevin John’s above examples for specifics).
I think most developers who run highly trafficked websites will prefer keeping stuff out of the core, to minimize bloat and to maximize scaling. Whereas most casual webmasters running a smaller forum will want as much in the core as possible.
It’s a natural tension. I think the best way to split the difference is to keep the core lean and mean, and then to have a set of pre-packaged plugins that are included in the main download that can be turned on (or can even default to being on). I think WordPress experimented with this direction last year? Not sure where it ended up though.
A few things were moved out of bbPress plugins into core, and it hasn’t really gone that well. “Subscribe to topic” was added to the core, and then promptly had a problem with spammed topics being blasted out over email. It’s a lot easier to apply a patch to a plugin than it is to get the patch approved in the core.
The “Page Links for bbPress” plugin was also moved into the core in 1.0. There were a number of code inefficiencies in that code that are now locked into the core. There was a recent patch released for the plugin version of Page Links (only for 0.9) that fixed this; that’s an example of how it can be helpful to keep non-essential stuff out of core.
