[expose]

I wonder if anyone can help please. I have run an update to a WordPress site (created by someone else) that had bbpress integrated. I didn’t upgrade BBpress. Before the WP upgrade, the forum was working fine. However since the wordpress upgrade (from 2.9.2 to 3.1) we are having the following problems:

1) I cannot access the bbpress admin panel

2) The Forum is showing posts and topics but the reply form is missing (only the heading shows)

3) I cant see any way of creating posts, topics or threads so I presume something else is missing…

I had to rewrite the WordPress theme files as the original custom theme had been so badly coded / core hacked etc. I haven’t touched the custom bbpress theme so thought it would be something to do with that. So first thing I did was disable it and enabled the default bbpress theme (through phpmyadmin) but have exactly the same set of problems – which to me rules out a theme issue.

Anybody have any ideas where to start? Sorry I am not sure of bbpress version. Where do I find that?

[zaerl]

https://bbpress.org/forums/topic/tons-of-depreciated-errors#post-70000

[zaerl]

https://bbpress.org/forums/topic/tons-of-depreciated-errors#post-70000

[arthurfreitas]

When one of them is disabled, both systems funscionam normally.

Sorry.

When one of them is disabled, both systems works normally.

Att,

[arthurfreitas]

When one of them is disabled, both systems funscionam normally.

Sorry.

When one of them is disabled, both systems works normally.

Att,

[Joe]

Hello,

I’ve recently just installed a bbPress instance on my server, but I’m running into a fair amount of issues with PHP.

Take, for example, the homepage ( http://greenerclassrooms.org.uk/bbpress/ ) which has all the PHP errors in the header.

Can you help at all?

I’m running the PHP5.3.5 and MySQL 5.1

Also, if I try to login, it goes to a white page with the following text:

Deprecated: Assigning the return value of new by reference is deprecated in /home/cattery/public_html/greenerclassrooms/bbpress/bb-settings.php on line 186

Deprecated: Assigning the return value of new by reference is deprecated in /home/cattery/public_html/greenerclassrooms/bbpress/bb-includes/backpress/functions.wp-object-cache.php on line 108

Deprecated: Assigning the return value of new by reference is deprecated in /home/cattery/public_html/greenerclassrooms/bbpress/bb-includes/backpress/pomo/mo.php on line 171

Deprecated: Assigning the return value of new by reference is deprecated in /home/cattery/public_html/greenerclassrooms/bbpress/bb-includes/functions.bb-l10n.php on line 484

Deprecated: Assigning the return value of new by reference is deprecated in /home/cattery/public_html/greenerclassrooms/bbpress/bb-includes/backpress/class.wp-taxonomy.php on line 581

Warning: Cannot modify header information – headers already sent by (output started at /home/cattery/public_html/greenerclassrooms/bbpress/bb-settings.php:186) in /home/cattery/public_html/greenerclassrooms/bbpress/bb-includes/backpress/class.wp-auth.php on line 273

Warning: Cannot modify header information – headers already sent by (output started at /home/cattery/public_html/greenerclassrooms/bbpress/bb-settings.php:186) in /home/cattery/public_html/greenerclassrooms/bbpress/bb-includes/backpress/class.wp-auth.php on line 273

Warning: Cannot modify header information – headers already sent by (output started at /home/cattery/public_html/greenerclassrooms/bbpress/bb-settings.php:186) in /home/cattery/public_html/greenerclassrooms/bbpress/bb-includes/backpress/class.wp-auth.php on line 273

Warning: Cannot modify header information – headers already sent by (output started at /home/cattery/public_html/greenerclassrooms/bbpress/bb-settings.php:186) in /home/cattery/public_html/greenerclassrooms/bbpress/bb-includes/backpress/class.wp-auth.php on line 273

Warning: Cannot modify header information – headers already sent by (output started at /home/cattery/public_html/greenerclassrooms/bbpress/bb-settings.php:186) in /home/cattery/public_html/greenerclassrooms/bbpress/bb-includes/backpress/class.wp-auth.php on line 273

Warning: Cannot modify header information – headers already sent by (output started at /home/cattery/public_html/greenerclassrooms/bbpress/bb-settings.php:186) in /home/cattery/public_html/greenerclassrooms/bbpress/bb-includes/functions.bb-pluggable.php on line 232

[arthurfreitas]

Hi comm,

First of all, excuse the English. I’m better with French.

OK, I have WordPress installed on my machine and a bbPress deeply integrated (theme, cookies, users, etc…)

Everything worked fine until I activate the WP-Super-Cache, which made ​​my bbPress “disappear”. When I access the forum system, only appears a blank screen, inclusive in the administrative panels.

I noticed that this only happens when the WP-Super-Cache is enabled and integrated with my theme of WordPress is selected. When one of them is disabled, both systems funscionam normally.

Is there any way to enable the WP-Super-Cache does not destroy my deep integration with bbPress?

Att,

Arthur Freitas.

[jnw]

I just noticed this documentation: https://bbpress.org/documentation/integration-with-wordpress/.

Does this mean my 3.1 installation is incompatible with the integration?

When will bbpress be compatible enough to be able to log into both wp-admin and the forum at once?

[jnw]

I just noticed this documentation: https://bbpress.org/documentation/integration-with-wordpress/.

Does this mean my 3.1 installation is incompatible with the integration?

When will bbpress be compatible enough to be able to log into both wp-admin and the forum at once?

[jnw]

Hi all,

I’m sure this has been covered a few times, but here goes.

Cookies obviously aren’t working, because I’m getting booted out of wp-admin when logged into bbpress and visa versa.

Have installed the bbPress integration plugin with settings in wp-admin like so:

bbPress URL: http://website.com/forum/

Your Plugins URL: http//website.com/forum/bb-admin/plugins.php

Wordpress type: WordPress

Added this code to the very bottom of wp-config.php

define( ‘COOKIEPATH’, ‘/’ );

In bb-admin, I’ve got:

Wordpress address: http://website.com

Blog address: http://website.com

WordPress “auth” cookie salt: (auth_salt wasn’t present in the wp admin page, anyway I took the code from wp-config.php)

WordPress “secure auth” cookie salt: (as above)

WordPress “logged in” cookie salt: (as above)

Manually entered codes so the following match

AUTH_KEY / BB_AUTH_KEY

SECURE_AUTH_KEY / BB_SECURE_AUTH_KEY

LOGGED_IN_KEY / BB_LOGGED_IN_KEY

And that’s where I’m at. Can someone tell me what I’m missing?

I’m not going to worry about database sharing right now – is that advisable? Or is it highly recommended?

Also what should I have the wordpress roles set to for each one of these?

WordPress Administrator

WordPress Editor

WordPress Author

WordPress Contributor

WordPress Subscriber

Thanks for the help!

[_ck_]

Because you cannot disable access for all files in the template directory – CSS and some images have to be loaded directly by the browsers in the end.

So turning off PHP responses will do for now.

[_ck_]

Because you cannot disable access for all files in the template directory – CSS and some images have to be loaded directly by the browsers in the end.

So turning off PHP responses will do for now.

[qayqay12]

If there are never supposed to be loaded directly by the browser maybe we could also deny the access by another .htaccess config:

<Limit GET POST”>

order deny,allow

deny from all

</Limit>

Why don’t you add those .htaccess files in the repository. They will ensure security and they will not hurt on other servers than apache.

[qayqay12]

If there are never supposed to be loaded directly by the browser maybe we could also deny the access by another .htaccess config:

<Limit GET POST”>

order deny,allow

deny from all

</Limit>

Why don’t you add those .htaccess files in the repository. They will ensure security and they will not hurt on other servers than apache.

[_ck_]

There is a security bulletin being circulated this week about a “path disclosure” bug in bbPress 1.0.3 – it actually affects all versions.

It’s not a super-serious security bug in itself but it can be used to gain leverage.

Basically someone can discover the real path your files are in by causing a PHP error by trying to access a template file directly, where there is an error in the template because bbPress is not loaded at that time.

Here is a simple workaround for users on Apache (vast majority of users).

Make a file called .htaccess (note the dot at the start)

in it, put this line

php_flag display_errors off

Then upload that file to bb-templates and my-templates

The reason why we don’t put that in the master .htaccess file for all of bbPress is because you may need to see any regular errors in the future. However for the template subdirectories, there is no need because those files are never (supposed to be) loaded directly by the browser.

[jakobs]

Hi!

I have a smaller blog network (WordPress 3.1 Multisite) and bbPress 1.03.

Right now the integration works, but not fully. I can login on the forum with my wordpress user accounts but there’s some problem with cookies. I still need to login/log out one time at each site (forum/blog).

I’ve copied this from wp-config.php:

define(‘AUTH_KEY’, ”);

define(‘SECURE_AUTH_KEY’, ”);

define(‘LOGGED_IN_KEY’, ”);

define(‘NONCE_KEY’, ”);

define(‘AUTH_SALT’, ”);

define(‘SECURE_AUTH_SALT’, ”);

define(‘LOGGED_IN_SALT’, ”);

define(‘NONCE_SALT’, ”);

And of course included the salts + added BB_ suffix in bb-config.php.

I have a separate database for bbpress and the “Separate user database settings”-settings in options-wordpress seems to be right.

The URL:s under cookies is also correct (http://domain.net – as my blog).

Do you have any idea what the problem is?

Would be grateful for a solution. Thanks.

[miruru]

Thank you for this fantastic plugin, even if it is still under development. Great work so far and well done.

However I just have one small problem and cannot work out why it’s happening.

I left the slugs as default in the Forum setting and went to view the admin profile. All data is being displayed correct, however the Page Title displays, “Nothing found for User Admin”. I’ve looked everywhere but cannot find where it is going wrong. I’ve tried a different theme to no avail. This is really annoying me.

I’ve checked all the other pages and they are fine just the user page. Is there something that is causing this? I’ve tried disabling the All In One SEO plugin and then the page title says “Not Found” and the data is still being displayed correctly.

Any help would be most appreciated.

[WPsites]

Just thought I would update this post as nothing seems to have been said about the threaded posts plugin recently (https://bbpress.org/plugins/topic/threaded-posts/)

I’m in the process of setting up a forum and one of the requirements was for threaded posts so I have used this plugin.

I have it installed on the most recent version of BBpress (“Bechet” version 1.0.3) and on it’s own it works fine.

To get it to work I did have to follow the comments on the info page for this plugin. Pretty much just changed some file names.

If you want to use the threaded post plugin along with the BBpress moderation suite then you will run into problems when you come to moving and splitting threads since the moderation suite doesn’t know anything about the threaded post functionality and just cannot deal with it. So you will have your work cut out trying to hack the moderation suite to take into account the threaded posts (it is doable though).

Also the threaded post plugin may fail to list the threaded posts correctly if used in conjunction with other plugins that change the mysql query for displaying posts on the topic page. Since this plugin checks EVERY database query and if it matches what the plugin thinks is a request to display all posts from a topic then it intervenes and add something extra to the query to list the threaded posts in the right place.

As part of that, in the code for this plugin it actually says “# FIXME: This is a horrible horrible hack” in the no_child_posts function. Well I had to fix it in order for it to play nicely with some private forum functionality that changes the mysql query when requesting posts for a topic. The code I created that replaces the no_child_posts functionality is below.

function threaded_sql_where($where){

return $where . ” AND pp.post_id is NULL “;

}

add_filter(‘get_thread_where’, ‘threaded_sql_where’, 10, 1);

function threaded_sql_join(){

return “LEFT JOIN bb_post_parent AS pp ON pp.post_id = p.post_id”;

}

add_filter(‘get_thread_join’, ‘threaded_sql_join’, 10, 1);

You can download my modified version of the threaded posts plugin here: http://www.wpsites.co.uk/threaded_posts.zip

[dreamgrowers]

Oh, that makes total sense, thank you so much!

Well folks, this is exactly why I want bbpress to use my custom WP login because I’ve calibrated it perfectly to prevent spam as well as ask specific questions about the users.

Would still love to get help rediredting login to WP-admin

Thanks!

[dreamgrowers]

Oh, that makes total sense, thank you so much!

Well folks, this is exactly why I want bbpress to use my custom WP login because I’ve calibrated it perfectly to prevent spam as well as ask specific questions about the users.

Would still love to get help rediredting login to WP-admin

Thanks!

[amnion]

Indeed, this is an excellent plugin. Easiest transfer of forums I have ever done.

[amnion]

Indeed, this is an excellent plugin. Easiest transfer of forums I have ever done.

[Ryan Gannon]

Also, bbp_reply_author_link( array( ‘type’ => ‘avatar’ ) ); returns the avatar thumbnail is there a way to retrieve the full version of the avatar?

[zaerl]

It’s a known bug which has been fixed in the last (not released to the public) version. bbPress (standalone) is dead and I have decided to freeze all my plugins and waiting for the plugin version to come.

[zaerl]

It’s a known bug which has been fixed in the last (not released to the public) version. bbPress (standalone) is dead and I have decided to freeze all my plugins and waiting for the plugin version to come.