[Sam Bauers]

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;

}

[michael3185]

Using 0.9.0.5, I created a custom theme, doing it as instructed by copying template files into a my-templates/my-theme folder. I then created a new ‘role’ as one thread suggested, by modifying capabilities.php. No problems, and all works well.

For the Guest role I added, I allowed them to post replies, but not create new topics. Then I noticed that ‘Create Topic’ was showing on the topics page, but with no input area beneath it. I went through the theme template files over and over, but couldn’t find out where the [H2]Create Topic[/h2] (and similar for Reply) were. Odd. I finally tracked it down to a function in template-functions.php, around lines 136 – 142, where the titles are output, and then the post page called.

What this means is that A) the titles are not part of the post form (ie input area), and a theme can’t be properly customised without hacking a core file, which will then be overwritten by an upgrade. I’ve hacked my template-functions.php, and will have to do so again when I upgrade. The good thing is that my theme template files now have the titles where they ought to be, and they can be easy customised.

I didn’t want to mess with the template-functions.php code in case I broke it, so I just remmed out the follow line, then added the titles to post-form.php and topic.php;

// echo ‘<h2 class=”post-form”>’ . $h2 . ‘</h2>’ . “n”;

I don’t know if this has been changed in 1.0, but don’t you think it should be? I realise that the ‘role’ change I made hacked a core file, but at least upgrading to 1.0 (when it’s marked as stable) will give me proper roles.

[massbase]

ok, ill try that out (windows) if it wont work ill wait for the wiki.

my plugin plan:-

– User albums – in each profile a small image gallery of all uploaded images will be shown.

– Faviroute users – each user can follow another / bookmark a user.

– items-4-sale – users list their items for sale on their profiles.

– thumbnails for posts – so posts can be turned via themeing into a blog style post on frontpage.

so prepare for more annoying posts from me as i learn, believe it!

soon this lite forum can be turned into a social platform without the need of hefty BuddyPress

[Sam Bauers]

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

[Sam Bauers]

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)

[John James Jacoby]

Something must be up with the trunk…

If I install bbPress in a sub folder of WordPress, what seems to happen regardless of my settings or fudges, is that the bbPress login cookie is dropped with a “Host: domain.com” and a login via WordPress drops a cookie with a “Domain: .domain.com”

I’ve matched the URL’s, used with and without the integration speedup short-cut, deep/shallow integration, etc… Basically I’ve tried wiggling the settings back and forth, to no avail.

I was actually going to start my integration screen casts, so I suppose this will wait until tomorrow. haha!

I was able to get a WordPress login to drop cookies like “Host: domain.com” but the cookies the integration plugin drops are still “Domain: .domain.com” (If it dropped “Host: domain.com”, or if bbPress knew to look for “Domain: .domain.com” I suspect they’d work just fine.)

Note: I swear this WAS working earlier last week, as I’ve integrated two sites successfully with login/logout working from either direction.

[Sam Bauers]

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.

[Sam Bauers]

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 );

[John James Jacoby]

I think I’ve been salivating for 10 months waiting for this.

[norights]

I was having the same troubles as the original poster. WordPress 2.8 and BBPress 1.0 RC2, whenever I logged into BBP I couldn’t log into WP without logging out of BBP first. All the settings matched in both configs and adding in the suggested code (be it from the WP plugin which gave me a COOKIEHASH, a COOKIE_DOMAIN, a SITECOOKIEPATH, and a COOKIEPATH or from the BBP integration page which gave me just a COOKIE_DOMAIN and a COOKIEPATH) didn’t change anything. I tried junsuijin’s suggestions and now when I log into one it logs me out of the other. Anybody know how to get this running properly?

[Tynan Beatty]

Ok arturo84, make the changes Sam suggested by dropping the www from your cookie domain settings in each config, then put the Integration plugin code back into wp-config. In wp-config the Integration plugin recommends the following settings among others:

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

define('COOKIEPATH', '/');

change SITECOOKIEPATH to match COOKIEPATH like this:

define('SITECOOKIEPATH', '/');

define('COOKIEPATH', '/');

Then for the bb-config you should include the recommended integration speedups from the bottom of your bb-admin/options-wordpress.php page, and make sure that the cookiedomain doesn’t have www, and that both cookiepath and sitecookiepath are / as well:

$bb->cookiepath = '/';

$bb->sitecookiepath = '/';

Then go into bb-settings.php (in the base bbpress folder). Look to line 768 if you have rc-2. Change line 768 from:

$bb->sitecookiepath = rtrim( trim( $bb->sitecookiepath ), " tnrx0B/" );

to this:

$bb->sitecookiepath = rtrim( trim( $bb->sitecookiepath ), " tnrx0B" );

$_bb_sitecookiepath = rtrim( trim( $bb->sitecookiepath ), " tnrx0B/" );

Notice the removed / before the ” and that you need to add the second variable below it as that variable is used to set the other cookie paths.

Upload the altered bb-settings.php over your current one and it should fix the problem. Please come back and let us know if it works for you too

peace~

[Tynan Beatty]

Ok I think I found a fix for this and I’m submitting a patch to trac now

[johnhiler]

Hopefully we can leverage the WordPress theme directory code:

https://wordpress.org/extend/themes/

In the mean time, do you know of any extra themes beside the ones on bbshowcase?

http://bbshowcase.org/forums/view/available-themes

If we assemble a list of available themes, we’ll be all ready to go when the bbPress theme directory comes out eventually!

[Tynan Beatty]

This gave me a couple ideas to fix both our problems. Changing define('SITECOOKIEPATH', '...');

to match define('COOKIEPATH', '...'); fixed half of my problem (in other words, removing the wp-admin from the end of SITECOOKIEPATH, since I noticed that having it there sets a cookie with a Path like /yawp/wp-adminwp-admin), I can at least include the Integration plugin’s suggested settings in wp-config now. But I still get a second logged_in cookie when logging into the bbp side, that logging out from WP cannot remove. IE, /yawp/ and /yawp for the Path:

I haven’t figured out how to make bbP stop giving the second cookie without the trailing / but at least it now removes the one with the trailing / when logging out from WP (WP still thinks it is logged in due to the non-trailing slash cookie and shows the site admin link in meta, but won’t allow me re-enter the admin after logging out. At that point it acts as the situation arturo84 describes as his original problem, but also fails to logout from the bbp side)!

[Sam Bauers]

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.

[Ipstenu (Mika Epstein)]

Single quotes are bad HTML anyway and shouldn’t be used…

Checking with trunk: If I add in a link: <a href="http://bbpress.org">This is a link</a> it works. If I edit that post, I get this: <a href="http://bbpress.org&quot;">This is a link</a> It gets even weirder as it goes on.

Why is this really familiar? I think we had this once before…

(tags working, pagination of users working. We’ll get there! )

[the_Wish]

Thank you for your continuing work and effort on bbPress.

I upgraded from RC1 to RC2 and something seems to be messy with the way additional markup is handled.

So far, users could use syntax like this:

<a href='http://bbpress.org'><img src='https://bbpress.org/test.jpg' /></a>

to link a picture for example.

Now with RC2, the ‘…’ upper commas aren’t recognized any longer but instead you’d have to write:

<a href=http://bbpress.org><img src=https://bbpress.org/test.jpg /></a>

and “…” quotation marks will be automatically added.

Now the problem is that once the user edits a comment with such markup later on, the now present “…” will again not be recognized and turned into broken code instead.

[Ashish Kumar (Ashfame)]

Looking forward to it.

[Arturo]

i’ve upgraded wp from 2.7.1 to 2.8, checked all the key for the cookie and

AUTH_KEY in wp-config is the same of BB_AUTH_KEY in bb-config, the same for SECURE_AUTH_KEY – BB_SECURE_AUTH_KEY,

LOGGED_IN_KEY – BB_LOGGED_IN_KEY, NONCE_KEY – BB_NONCE_KEY.

i’ve installed and activated the plugin bbPress Integration 1.0-rc-2 configured with the url of bbpress (http://www.site.com/forums/) saved the option, copy/past in wp-config.php for the “code” in the box which is:

define(‘COOKIEHASH’, ‘e99db1aecc456188d6dc1ccc37528ff8’);

define(‘COOKIE_DOMAIN’, ‘.www.site.com’);

define(‘SITECOOKIEPATH’, ‘/wp-admin’);

define(‘COOKIEPATH’, ‘/’);

i’m able to login in bbpress side, and i see the cookie wordpress_e99db1aecc456188d6dc1ccc37528ff8 for /forums/bb-admin, /forums/bb-plugins, /forums/my-plugins, /wp-admin, /wp-content/plugins and /.

i’ve other 2 cookies bb-user-settings-1 and bb-user-settings-time-1 for /forums/bb-admin.

when i try to go in wp-admin i’m slogged from wp and 2 new cookies appear, wordpress_test_cookie.

when i try to login in WP side i’m redirected to the login page every time.

if i remove the code generated by the Sam’s plugin i can login but i’m logged out from bbpress…

how resolve this problem? thanks for the help.

[Florian]

Thanks. I manually added your fix to my installation and it seems to work fine.

[Sam Bauers]

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.

[Sam Bauers]

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

[John James Jacoby]

Thanks Sam. I’ve yet to try this, but I will tomorrow and will let you know how it works. I suspect probably better than I could ever do on my own.

My guess, is this works if bbPress is installed in a directory off the WordPress root called “/bbpress/” ?

Does this mean that some/all of the code above goes into the WordPress .htaccess file to prevent it from taking over, or does it go in the bbPress .htaccess file?

[Markus Pezold]

Hi again,

the code doesn’t work 100% in my installation.

After the Login in WordPress – my testuser is shown as “logged”, but I can’t go to the Administration. The System doesn’t redirect me. At the same time my testuser ist shown as “logged in” in bbPress and there I can go to the admin.

When I test the login from bbPress first nothing seems to happen. I’m not logged in in both bbPress and WordPress.

hmpf … So … I’m going to test tomorrow again.

[Sam Bauers]

Change that add_option() to backpress_add_option()

This is now fixed in trunk.