Yeah, in your theme’s template file register-success.php. It’s not bad grammar, it’s actually a bug; it should read
Your registration as Username was successful.
I’ll go submit a trac ticket.
Make that “I’ll go have submit a trac ticket which are #669.”
I have translated (mostly) .pot file from 0.8.1 version to Serbian Latin (utf-
.
Download from: http://www.aplus.co.yu/deliver/
There are some phrases that are not translated as I was not sure where are they used. I’m using this on my vine forum and will refine it there, during use.
I noticed that .pot file is not complete, as some phrases are outdated or wrong (ex: “…is proudly powered…” is not the same phrase as in the theme), but it’s fine, most of the time.
Hopefully developers will update the .pot file in the trunk.
Sneaky, sitting on some code to look through error logs here but it’s working at what you might call a sub-optimal level in several respects. Gonna brood on it some more, sorry to still leave you waiting. Will upload it when it works.
@davidbaldwin, the titles and rss are on a toggle, basically, when the page loads up, I check to see if bbpress is running:
global $bb;
if($bb){
if it is I switch the title to bbpress using bb_get_title(), and switch the feed to bb_feed_head();
Your registration as was successful. Within a few minutes you should receive an email with your password.
Now I’m not picky but the first two users that signed up pointed out that there is a typo in the mail sent to new users…
as was successful ???
and where in the code can I modify this?
Thanks
Let it be known that I am a complete tool! I’d left the WP functions include line in the config file, back from when I was trying to integrate the WP head and footer (since just duplicated them in BB). For some reason this was causing the sluggishness and problems with IE.
Doh. Nice to get to the bottom of that! 
That’s pretty weird. Have you tried going to bb-admin/themes.php? That’s its default location.
Reinstall won’t help you!
When you log into bb, you also log into WordPress, but not the other way around, right? Trouble logging in is usually a cookie problem.
Add this to your config.php:
$bb->cookiepath = '/';
$bb->cookiedomain = '.example.com';
and this in your wp-config.php for wordpress:
define('COOKIE_DOMAIN', '.example.com');
define('COOKIEPATH', '/');
I think that those are all the things you need to set. Give it a go.
To get www.community.example.com you need to set up a subdomain. This is usually done in your control panel. Bear in mind that some hosts have restrictions on numbers etc.
Hi,
Can someone recommend if I should do a re-install?
WP is currently installed here: http://www.website.com/community/wp
bbpress is currently: http://www.website.com/community
Even though I managed to get the 2 sites integrated – i can see the same users on boths sites but am having problems logging in. And I know I need to do something to config.php but can;t quite figure it out. Or would a bbpress re-install solve my issues?
Also how do I setup something like http://www.community.website.com?
You advise will help a lot. Sorry I’m new to all this and this has been rather fasinating to me becos I’m a chef by training You cannot imagine the good you guys have done!
Thanks heaps
“The black, green and white really works.”
-> I agree!
I’m thinking that literally translating “tags” is not a a good idea because in spanish it doesn’t sound very meaningful. Same with wordpress “categories”, it sounds strange.
I’d like to suggest anyother word but I still haven’t found a good one
Hey, I really like that! It looks great. The black, green and white really works.
The link colour is a bit confusing though. Tag links are light blue when hovered but nothing else is? They’re text colour normally? The biggest change (backround to black) is when you hover over the table row, yet you’ve still gotta hover over the actual title. Then people’s names are always light blue yet only sometimes links, while the actual link under their name is text colour. It confuses me 
I think you’d be better off just sticking to green and black, because that does work really well and it’s one damn cool design.
Hey, fel 64!
Then this is a bad new because it is not smart at all changing core files.
However I have a half working “B plan”
You can get rid of that streams.php error by pointing the ‘BBLANG’ to the wordpress .mo file.
You have to change bbpress config.php like this;
define('BBLANGDIR', '/wp-includes/languages/es_ES.mo');
The problem is that when you copy the bbpress .mo to the wordpress .mo it doesn’t translate anything but the wp itself.
Translation files come in two files; a .mo file and a .po file that I think is the source code.
Perhaps you need to add anything to this .po file but I didn’t find out yet.
No…
I do what this. Sub-forums is not at all what I want… I want to be able to create categories and then put forums and sub-forums in them 
Thanks for posting the solution, then
Well, it seems adding this to the root file causes the problems viewing in IE:
AddHandler application/x-httpd-php5 .php
Removing that line means I can view the forum without problems in IE, but then stops WP admin from working properly (why I added it in the first place).
Any way of stopping a child dir (the forum dir) from inheriting that rule from the parent dir, or should I just add the line to the WP admin dir .htaccess file?
Hi Trent – thanks so much for checking it out. Yes – that’s the only line in the .htaccess file:
Options +MultiViews
Any ideas why some links work and others 404?
Some permalinks are showing up fine and some are not for me. What do you have in your .htaccess file in the /forum/ folder? Is it just:
+ Options Multiview
That seems to work for me. Without having a seperate .htaccess file for your bbPress folder, it will get messed up and try and use the wordpress .htaccess.
As for speed, nothing changed for me with and without permalinks on.
Trent
Does editing your .htaccess to just having the following and nothing else work?:
Options +MultiViews
Does that work? Having it of course in your /bbpress/ folder only so that it is not screwing up your wordpress .htaccess file. Does that work for your installation?
Trent
Here’s a couple things to try.
Disable all your plugins.
Set $bb->mod_rewrite = false; in your bbPress’ config.php.
After you changed the hierarchy in the admin section, did you click the “Save Forum Order” button?
I don’t believe this is a plugin issue. It’s possible it’s a theme issue. You may have to change some of the markup and CSS of your theme to get it to work correctly. Check out (can probably just copy and paste) the markup in /bb-templates/kakumei/front-page.php:
<?php if ( bb_forums() ) : ?>
<h2><?php _e('Forums'); ?></h2>
<table id="forumlist">
<tr>
<th><?php _e('Main Theme'); ?></th>
<th><?php _e('Topics'); ?></th>
<th><?php _e('Posts'); ?></th>
</tr>
<?php while ( bb_forum() ) : ?>
<tr<?php bb_forum_class(); ?>>
<td><?php bb_forum_pad( '<div class="nest">' ); ?><a href="<?php forum_link(); ?>"><?php forum_name(); ?></a><small><?php forum_description(); ?></small><?php bb_forum_pad( '</div>' ); ?></td>
<td class="num"><?php forum_topics(); ?></td>
<td class="num"><?php forum_posts(); ?></td>
</tr>
<?php endwhile; ?>
</table>
<?php endif; // bb_forums() ?>
You’ll then need some CSS too:
#forumlist tr td div.nest {
padding-left: 2.5ex;
}
Also, the URLs will not look like example.com/forum/sub-forum; the URLs do not currently reflect the hierarchy.
Thanks for your explanations, i hope bbPress will be as clever as WordPress.
do you mean that “after upgrading and changing the permalink structure of a forum; the old permalinks does not redirect to the new one” ?
No, I just meant that with the current code, if you’ve somehow managed to change the slug, you’ve broken the old links. But, as you point out, bbPress knows how to move “sideways” across different kinds of permalinks.
WordPress allows you to change the slug and automatically redirects your old links to the new slug; it’s more clever than bbPress is at the moment
It’s there! I’m looking at it right now. In the code you copied it is line 10.
The bb_posts table is what we’re looking for, not wp_posts (also a table), and it tells you the databasename.tablename so it’s actually trying to look for a table called “posts”. I don’t think the wpbb_prefix option exists in your tables, I suspect that’s a Latest Discussions plugin thing (ah, hindsight). If it did, it would read bb_. The . is used to join two strings together, so what it should be doing is joining 'bb_' and 'posts' together into the table name 'bb_posts', but since that option doesn’t exist in your tables it just join together '' (a blank) and 'posts', leaving us with the incorrect table name of just 'posts'. I suspect.
karaboga, permalinks should be permanent. Perhaps we can work on redirecting old permalinks to the new ones. Better yet, that’d be a great plugin
mdawaffe, do you mean that “after upgrading and changing the permalink structure of a forum; the old permalinks does not redirect to the new one” ? In this forum, for example we if write
https://bbpress.org/forums/topic/100
it is redirected to the 100th topic with the new permalink structure.
—
Yes, permalinks should be permanent. But, in WordPress we can change the post slug, and then the permalink of the post is changed. Why cannot we do so in bbPress?
Sorry fel but that piece of code isnt in there. This is what it looks like
‘<?php
function felblogtotopicid( $felpostID ) {
global $table_prefix, $wpdb;
$posts_table = $table_prefix . “bbpress_post_posts”;
$topic_id = $wpdb->get_var(“SELECT topic_id FROM $posts_table WHERE post_id = $felpostID LIMIT 1;”);
return $topic_id;
}
global $post, $wpdb;
if( $forumtopic = felblogtotopicid( $post->ID ) ) {
$bbprefix = get_option( ‘wpbb_bbprefix’ );
$replies = $wpdb->get_results( ‘
SELECT poster_id, post_text, post_time
FROM ‘ . $bbprefix . ‘posts
WHERE topic_id = ‘ . $forumtopic
);’
I think it has something to do with ‘$table_prefix, $wpdb;’ and ‘$posts_table = $table_prefix . “bbpress_post_posts”;’. My table prefix is not wpdb (where wpdb = database name) it is just wp. Plus that ‘.’ in there is throwing it off as well as the error reads:
[Table ‘databasename.posts’ doesn’t exist]
SELECT poster_id, post_text, post_time FROM posts WHERE topic_id = 6
“.posts” That ‘.’ is getting into the code and appending itself to the db name…
I think…
You are the master though….
