There’s not a clear path honestly, since everyone’s installations can be markedly different. To guess at exact SQL queries you would need to run would do more harm than good.
If it was me, I would spend a lot of time analyzing the data in the 2 databases with something like phpMyAdmin, and come up with a plan on how to combine the two databases and WordPress/bbPress users tables together into 1.
The file_exists() checks increase exponentially with each miss in the hierarchy when a file isn’t in the first/second/third position, etc… So depending on the configurations that other theme developers would choose to adopt for their needs, it may or may not be an issue.
All of the options you’ve mentioned are what I’d suggest. Since you have two sets of user tables (WordPress/bbPress) there’s no way to automate the merging of them. You’ll either need to do it manually, or pick one set over the other.
Either way you’ll need to spend some time manually finishing what the importer cannot.
This will be fixed in beta 2.
I don’t think using something like that is a bad idea at all. I’d reverse the logic a little bit, and predefine the template hierarchies for the single, archive and else scenarios, and allow them to cascade as needed from several locations.
The long term performance issue is: the more possible files it looks for, the more file_exists() checks PHP runs, which is more access to the file system, and when those get into the hundreds of requests is going to be a pain point. Like many things it’s a balance between flexibility and performance, and finding the best times to make those compromises.
I could see something like this happening for BuddyPress 1.4, and possibly for bbPress 2.1. I’ll play with the idea after Beta 2 drops to see if it’s worth making the adjustment. It’s a bit late in the beta phase to make a change this large, but if the overall benefit is worth the change and it doesn’t break any existing installs, then it’s a possibility.
@kai920 – Not sure what you mean. Your forums should look like http://johnjamesjacoby.com
The default /forums view is controlled by archive-forum.php. There’s a bug in Beta 1 that’s affecting some installations that will probably fix the problem you’re experiencing.
No idea – never encountered that as a problem before. Interested to know what’s causing it though.
Can you tell where those posts are being created from? I.E. – front or back end?
@johan & depex – Similar answers to both of your questions. You should be able to use some kind of plugin to provide those capabilities, yes. But, nothing in the core of bbPress to allow you to set the scope of them yet.
Should be an easy adaptation. Would be awesome of someone to port that over.
@kai920 – Go to the tools/recount area of your stand alone installation, and run all of the recount functions there (just to be on the safe side.)
Confirmed. Working on a fix now.
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.
