Leaving the folders where they are is actually easier programatically, and almost as tidy (they all turn up together alphabetically). I also think it’s easier to explain. So I’m not really convinced to throw them all into one folder, as satisfying as that may be.
Just remembered, if WordPress is loaded then bbPress relies on the setting of WPLANG in WordPress to determine which language to use.
This will all probably require some more work.
It should be possible to load both language files, in fact some changes were made to WordPress to address the problem specifically.
Can you link to the language files you were trying to use?
* Side note: We should probably move where languages are stored. A my-languages directory would probably be the way to go.
@iservers
Well, that’s different… 
But I just realised you are using bbPress 0.9 – the bb_mail() function has been replaced in 1.0-alpha with one more like wp_mail() in WordPress.
It was replaced in part because people had problems sending from Windows environments. You have probably just pinpointed the cause of that. Just a few months too late unfortunately!
For now I would just hack the core of 0.9 if I were you – it is unlikely to see any more updates. The replacement function in 1.0 should take care of this, although I would appreciate it if you could test 1.0-alpha for the same problem if you have some time.
Well, basically I’m not sure how much more time it’s going to take to get things right for the final 1.0 release.
I could set a date, but then if it wasn’t met there’d be a whole new set of expectations and complaints to manage.
bbPress 1.0 will be released after the “1.0-rc” (release candidate) versions, which will come after the “1.0-beta” versions which will come after the current “1.0-alpha” versions.
Basically there is still very new or experimental stuff in the 1.0-alpha releases. Once that newer functionality is tied down we’ll be able to move to 1.0-beta which should only contain cosmetic changes and optimisations. Then once those are complete we’ll move to 1.0-rc, during which we will generally only do bug fixes. Once the bugs are ironed out, we’ll go to a final 1.0 release. Hopefully the minor point releases can be kept to a minimum after that.
How long is that piece of string? Maybe one maybe two months. It actually depends on people testing more than anyone coding, although if we can get more people contributing patches to core it would be great too.
So in summary…
No, bbPress is not slow like GoDaddy says.
Someone brought this up on the IRC channel the other day. Seems like it’s Windows specific. Please add a ticket in Trac.
There are no plans nor do I think their should be.
The premise of Smarty is screwy to me.
There is some idea that out there somewhere are “template developers” that aren’t allowed to touch “teh sacred PHP”. So we need an abstracted templating language so that they can do loops and conditionals in their HTML templates.
I don’t believe these people actually exist and that if they do, they should just use PHP and be trained to a point where they are trust-worthy.
99% of Design should be held in the CSS now anyway. The code/display separation thing has moved up a level these days.
@johnjamesjacoby
I suspect that user just never visited the bbPress portion of your site.
There are four ways a user will get their role set in bbPress once the role map is setup:
- If they register through bbPress (will also give them a role in WordPress)
- If they register through WordPress, then visit bbPress whilst logged in
- If they register through WordPress, then logout, then log back in through bbPress at some stage
- If they register through WordPress, then an admin re-saves the role mapping in bbPress
@the_Wish
I’ve tracked your “.” prefix issue down. There should be a new version of the plugin available soon to correct this problem.
Having Google Alerts set up to tell you when your company gets mentioned is a pretty standard PR move these days.
There is probably one or two people at GoDaddy who look at all these and then route them to sales or service or whatever.
If they follow through I’ll be impressed then, not enough to use their service, but still.
I’d rather not fork bbPress to create a plugin version but I would be interested in seeing a plugin created for WordPress that basically loaded bbPress into WordPress for you. johnjames is right about having to keep our integration options open beyond a simple plugin.
Also, perhaps you missed the announcements about full integration returning in the recent alpha versions?
Do you know what transport is being used on the broken installations?
wp_remote_get() now uses the HTTP API library, which is supposed to try different ways of retrieving a remote HTTP resource. It is possible that the method the problem server is selecting to use looks like it is valid to WPMU but in fact isn’t for some configuration reason.
Beyond that I really can’t help without more specifics about your setup, mainly what transport method the HTTP API is using.
Sounds like a bug to me, please report it in Trac http://trac.bbpress.org
PHP mail() only uses SMTP when PHP has been directed to use an MTA by default like in your case. There are plenty of situations where this isn’t the case, like on a lot of shared hosting services. In these cases the only way to send mail is to programmatically connect to an SMTP server. This is possible in 1.0-alpha versions using the plugin that chrishajer pointed out.
I wish it was as easy as changing that one line, believe me. Also, if your MTA is not accepting that very standard form of email address then it is really a config issue at the MTA. There is no reason it should be rejecting an RFC compliant email address like that one.
bb-config.php shouldn’t need a LOGGED_IN_KEY definition – you may as well remove it.
BB_NONCE_KEY is a new key for making unique nonce values – this doesn’t affect cookies.
@johnjamesjacoby
In your wp-config.php file, right after you include bbPress you should probably clear out all filters and actions so that nothing in bbPress alters WordPress unexpectedly. Use this code right after the include to do that:
// Remove filters and action that have been set by the included bbPress
if ( defined( 'BB_PATH' ) ) {
$wp_filter = array();
$wp_actions = array();
$merged_filters = array();
$wp_current_filter = array();
}
I’ve also briefly tested the deepest integration possible with a cross include; including BBP into WP config, and WP into BBP config, thus allowing all functions in all areas.
You are a braver man than me.
@johnjamesjacoby
This is what I like to hear!
People having issues with cookies etc need to remember to configure the WordPress plugin and also follow it’s instructions to modify the wp-config.php file in WordPress.
Further to this, you should clear out any manual settings you have made to bb-config.php in bbPress and re-check your settings in the “WordPress integration” page in bbPress admin.
Then clear all your cookies and retest.
@TechGnome
Good luck, be sure to report back when it’s done and please share anything you can.
@johnnydoe
That would be hard to keep up with.
We rely on plugin devs to look after their own code basically. Expect renewed interest when the final 1.0 is released.
Except unicode for usernames, that will be fixed by allowing unicode display names in bbPress 1.0
@mshakour
I’ll contact you about adding this to the language repository.
Also, any changes that you need made to core to get full RTL working please add patches to Trac https://trac.bbpress.org/
You shouldn’t be forced to make a modified redistribution just for RTL text. I’m sure the changes required wouldn’t be overwhelming.
We do unicode display names in bbPress 1.0, but not usernames.
