[@sambauers Participant 15 years, 6 months ago]

Perhaps talk to the WordPress Chinese translation group… http://www.wpcng.com/

Raw POT files for each version are here… http://svn.automattic.com/bbpress-i18n/pot/tags/

[@sambauers Participant 15 years, 6 months ago]

Works for me. Did you make the change manually or did you grab the latest version from trunk?

[@sambauers Participant 15 years, 6 months ago]

@arturo84

Is this WPMU? If not remove the dot at the start of both domains.

If you are using WPMU you might need to sit tight while I troubleshoot that one.

[@sambauers Participant 15 years, 6 months ago]

This will probably work:

rewrite ^/page/([0-9]+)/?$ /index.php?page=$1 last;

rewrite ^/forum/([^/]+)/page/([0-9]+)/?$ /forum.php?id=$1&page=$2 last;

rewrite ^/forum/([^/]+)/?$ /forum.php?id=$1 last;

rewrite ^/forum/?$ / permanent;

rewrite ^/topic/([^/]+)/page/([0-9]+)/?$ /topic.php?id=$1&page=$2 last;

rewrite ^/topic/([^/]+)/?$ /bbpress/topic.php?id=$1 last;

rewrite ^/topic/?$ / permanent;

rewrite ^/tags/([^/]+)/page/([0-9]+)/?$ /tags.php?tag=$1&page=$2 last;

rewrite ^/tags/([^/]+)/?$ /tags.php?tag=$1 last;

rewrite ^/tags/?$ /tags.php last;

rewrite ^/profile/([^/]+)/page/([0-9]+)/?$ /profile.php?id=$1&page=$2 last;

rewrite ^/profile/([^/]+)/([^/]+)/?$ /profile.php?id=$1&tab=$2 last;

rewrite ^/profile/([^/]+)/([^/]+)/page/([0-9]+)/?$ /profile.php?id=$1&tab=$2&page=$3 last;

rewrite ^/profile/([^/]+)/?$ /profile.php?id=$1 last;

rewrite ^/profile/?$ /profile.php last;

rewrite ^/view/([^/]+)/page/([0-9]+)/?$ /view.php?view=$1&page=$2 last;

rewrite ^/view/([^/]+)/?$ /view.php?view=$1 last;

rewrite ^/rss/?$ /rss.php last;

rewrite ^/rss/topics/?$ /rss.php?topics=1 last;

rewrite ^/rss/forum/([^/]+)/?$ /rss.php?forum=$1 last;

rewrite ^/rss/forum/([^/]+)/topics/?$ /rss.php?forum=$1&topics=1 last;

rewrite ^/rss/topic/([^/]+)/?$ /rss.php?topic=$1 last;

rewrite ^/rss/tags/([^/]+)/?$ /rss.php?tag=$1 last;

rewrite ^/rss/tags/([^/]+)/topics/?$ /rss.php?tag=$1&topics=1 last;

rewrite ^/rss/profile/([^/]+)/?$ /rss.php?profile=$1 last;

rewrite ^/rss/view/([^/]+)/?$ /rss.php?view=$1 last;



if ( !-e $request_filename ) {

rewrite ^ /index.php last;

}

[@sambauers Participant 15 years, 6 months ago]

@dthom

The version is in a meta tag in the header as well as stated in the footer of the admin area.

bbPress doesn’t have granular per-forum permissions out-of-the-box. There are plugins that cover that though.

You might need to use the smtp mailer plugin to get emails working. Using that you can send email via an SMTP server instead of the default method which tries to send through PHP’s mail() function.

@the_Wish

The “fix” won’t fix any text which is already malformed. Once you edit the text to repair it shouldn’t happen again.

@Michael3185

0.9 Templates should still work with 1.0 – you will want to examine some of the new template functions that are in the default theme though.

[@sambauers Participant 15 years, 6 months ago]

Output caching is probably totally unnecessary for 99.9% of bbPress installs.

There are a few reasons but primarily:

1. Most of the users on your site are probably logged in, and that means they can’t get cached versions.

2. bbPress is pretty light on MySQL queries.

At Automattic we have never had any need to run any caching besides MySQL query cache, and sometimes we don’t even use that. Although our hardware might be better than most, we also have more traffic than most too.

[@sambauers Participant 15 years, 6 months ago]

Go into the bbPress directory in a terminal (Mac/Linux/Unix)

All filters:

grep -r -n apply_filterss*( . | grep -v .svn/ | grep -v @uses

All actions:

grep -r -n do_actions*( . | grep -v .svn/ | grep -v @uses && grep -r -n do_action_ref_arrays*( . | grep -v .svn/ | grep -v @uses

[@sambauers Participant 15 years, 6 months ago]

Try fudging it by adding a subdomain to the WordPress URLs in the WordPress Integration section.

I’m going to look at WPMU integration now to see what else might be up there.

[@sambauers Participant 15 years, 6 months ago]

The fix on the WordPress side is to remove these defines from wp-config.php:

define('COOKIEHASH', 'whatever');

define('SITECOOKIEPATH', '/wp-admin');

The plugin will be updated soon, but remove those if you are running WordPress standard (i.e. Non-WPMU)

[@sambauers Participant 15 years, 6 months ago]

There is now a fix in bbPress trunk for an associated issue where bbPress would not clear all wordpress_logged_in cookies that were generated by WordPress.

Seriously, my life is wasting away chasing WordPress cookies.

[@sambauers Participant 15 years, 6 months ago]

There is a problem with the integration plugin. Some code which was meant to distinguish between WordPress and WPMU is now failing.

I’ll have a new plugin out soon. When you upgrade the plugin, you will need to remove the settings it previously instructed you to use in wp-config.php and then check the admin page in WordPress for the new settings to use.

[@sambauers Participant 15 years, 6 months ago]

The bad quoting issue is fixed, it was caused by the move to the new esc_html() function from WordPress.

Here’s the quick fix. In bb-includes/functions.bb-formatting.php go to line 83 and replace:

$text = esc_html( $text );

with:

$text = wp_specialchars( $text, ENT_NOQUOTES );

[@sambauers Participant 15 years, 6 months ago]

Single quotes in attributes ought to work too. I’ll look at both these problems as a matter of urgency.

[@sambauers Participant 15 years, 6 months ago]

It probably won’t ever work. Try bbPress 1.0 instead (but you will need to export a trunk version from SVN).

[@sambauers Participant 15 years, 6 months ago]

Does your site always have “www” in front of it?

In any case, try changing the COOKIE_DOMAIN in WordPress like so (note the dot in front of the domain):

define('COOKIE_DOMAIN', '.site.com');

Also enter this value in bb-config on the bbPress side:

$bb->cookiedomain = '.site.com';

Doing this will log you out, but you should be able to just log back in.

[@sambauers Participant 15 years, 6 months ago]

bbPress uses the display name by default for most functions where the user needs to be identified by name. Check how the default template does it.

The only time the user login is shown is if the user has no display name set.

[@sambauers Participant 15 years, 6 months ago]

Awesome.

Please post any new bugs to the trac. They may get lost in here otherwise.

[@sambauers Participant 15 years, 6 months ago]

We have bbPress physically located a subdirectory within WordPress.com (WPMU), you can call that “bbpress”. We do it this way because we point *.wordpress.com to the same host (well not exactly, but for the point of the example let’s say we do). Anyway, because on WordPress.com all blogs are given a subdomain, we need to intercept the forum subdomains and push them to the bbPress code before WPMU executes. That’s what this .htaccess code does.

You could do it without fewer rewrite rules if you didn’t use pretty permalinks.

[@sambauers Participant 15 years, 6 months ago]

Sounds like the upload to your server was incomplete. (I’m assuming you downloaded to your computer then uploaded via FTP).

[@sambauers Participant 15 years, 6 months ago]

By the way, I don’t like supporting the last one. But I am.

[@sambauers Participant 15 years, 6 months ago]

I tend to use these terms and they are all potentially mutually exclusive, no one type of integration absolutely depends on the other although the first one generally requires the second one to work (99.9% of the time).

• Cookie integration – Sharing of login cookies with WordPress
• User database integration – Sharing of user data tables with WordPress
• Deep integration – Including the WordPress codebase (PHP) inside bbPress to allow use of WordPress functions inside bbPress

[@sambauers Participant 15 years, 6 months ago]

OK, took me a couple of reads to work out what was happening.

Now fixed in the latest trunk. If you aren’t using SVN to update then you will also need to grab the latest BackPress seperately.

[@sambauers Participant 15 years, 6 months ago]

The tag issue is fixed.

This list contains all the outstanding reported issues which I am aiming to fix before the 1.0 release. At the moment there are only two things there. If you know of an issue that isn’t there, then please add it immediately.

Other remaining tasks before 1.0 is released all have to do with finishing the admin screens. This will be heavily based on WordPress.

We also have Ben Dunkle – the guy who created the WordPress admin icons – working on some missing icons (forums, topics, posts).

[@sambauers Participant 15 years, 6 months ago]

@arturo84

RC-2 has a bug with integration (just some function name clashes). Can you grab the current trunk and try that? It seems to work for me.

[@sambauers Participant 15 years, 6 months ago]

Change that add_option() to backpress_add_option()

This is now fixed in trunk.