[Robin W]

but if you really want to debug

It could be a theme or plugin issue

Themes

As a test switch to a default theme such as twentyfifteen, and see if this fixes.

Plugins

If that doesn’t work, also deactivate all plugins apart from bbpress and see if this fixes. if it does, re-enable one at a time to see which is causing the error.

Then come back

[Robin W]

It could be a theme or plugin issue

Themes

As a test switch to a default theme such as twentyfifteen, and see if this fixes.

Plugins

If that doesn’t work, also deactivate all plugins apart from bbpress and see if this fixes. if it does, re-enable one at a time to see which is causing the error.

Then come back

[Robin W]

This is because in the bbpress plugin there is a template called content-search.php. Many themes also now have a template file called content-search.php. Since the bbPress templates don’t necessarily need to be in a bbPress folder, the bbPress plugin is choosing the template from your theme before the template that is actually in bbPress.

To fix copy content-search.php from the bbPress plugin templates and place it in a child theme in a folder called bbpress.

Functions files and child themes – explained !

So create a directory on your child theme called ‘bbpress’
ie wp-content/themes/%your-theme-name%/bbpress

where %your-theme-name% is the name of your theme

find
wp-content/plugins/bbpress/templates/default/bbpress/content-search.php
Make a copy of this file, and put in in the directory called bbpress that you created above, so you end up with
wp-content/themes/%your-theme-name%/bbpress/content-search.php
bbPress will now use this template instead of the original

[Robin W]

This is because your theme or a plugin is adding the bootstrap library, and also adding the ‘.card’ css class to the forum display, and this has a bad effect.

It could be a theme or plugin issue

Themes

As a test switch to a default theme such as twentyfifteen, and see if this fixes.

Plugins

If that doesn’t work, also deactivate all plugins apart from bbpress and see if this fixes. if it does, re-enable one at a time to see which is causing the error.

Then come back

[Robin W]

create a directory on your theme called ‘bbpress’
ie wp-content/themes/%your-theme-name%/bbpress

where %your-theme-name% is the name of your theme

find
wp-content/plugins/bbpress/templates/default/bbpress/form-anonymous.php
Make a copy of this file, and put in in the directory called bbpress that you created above, so you end up with
wp-content/themes/%your-theme-name%/bbpress/form-anonymous.php
bbPress will now use this template instead of the original
and you can amend this

in that template you will see

<p>
			<label for="bbp_anonymous_email"><?php _e( 'Mail (will not be published) (required):', 'bbpress' ); ?></label><br />
			<input type="text" id="bbp_anonymous_email"   value="<?php bbp_author_email(); ?>" tabindex="<?php bbp_tab_index(); ?>" size="40" name="bbp_anonymous_email" />
		</p>

just remove that – I think that should work

[dunritetech]

This is related to an issue in previous versions. Please update WP Super Cache to the latest version ( 1.6.8 ). Before plugin activation, you should fix the file wp-content/wp-cache-config.php (You need FTP access). The fastest way is removing this file (In this case all settings will reset to defaults).

[Robin W]

It could be a theme or plugin issue

Themes

As a test switch to a default theme such as twentyfifteen, and see if this fixes.

Plugins

If that doesn’t work, also deactivate all plugins apart from bbpress and see if this fixes. if it does, re-enable one at a time to see which is causing the error.

Then come back

[scottott]

I have renamed the root forum link to ‘discussions’ and then tried both methods of creating a page (with and without the shortcode). If I go directly to a subforum or topic, everything is fine. But if I want to go to the forum home (index), the URL mysite.com/discussions/ executes a search on my WP site, rather than taking me to the main page of for the forum. The same happened when I used the default name for the forum root. I can’t share a link, because the site is Members-only.

[kexia]

Does anyone know the correct way to enable the participant role to read private topics? I found a bit of a work around (see below). But I’d like to know how to enable it correctly.

Even though bbPress’ documentation says that users with the Participant role can read private forums and topics, the current version of bbPress (2.5.14) allows participants to read private forum names, but not private topics names or content.

I did some searching on this site and it looks like people have been complaining and notifying bbPress about this bug for about seven years and it’s STILL not fixed. The most support help I’ve seen is someone saying the issue is because of another plugin. But that’s not the case.

I checked the bbPress code in the capabilities.php file located in wp-content/plugins/bbpress/includes/core/capabilities.php, and sure enough, the capability to ‘read_private_topics’ is not listed under the Participant’s Topic Caps section:

// Participant/Default
case bbp_get_participant_role() :
default :
$caps = array(

// Primary caps
‘spectate’ => true,
‘participate’ => true,

// Forum caps
‘read_private_forums’ => true,

// Topic caps
‘publish_topics’ => true,
‘edit_topics’ => true,

// Reply caps
‘publish_replies’ => true,
‘edit_replies’ => true,

// Topic tag caps
‘assign_topic_tags’ => true,
);

I tried adding the ‘read_private_topics’ capability to the Participant capabilities section:

// Topic caps
‘publish_topics’ => true,
‘edit_topics’ => true,
‘read_private_topics’ => true,

But that didn’t work. So then I tried copying and pasting all the capabilities from the Moderator role to the participant role, including the first part of the code under the “Primary Caps” section that lists spectate, participate, moderate, throttle, and view trash.

// Moderator
case bbp_get_moderator_role() :
$caps = array(

// Primary caps
‘spectate’ => true,
‘participate’ => true,
‘moderate’ => true,
‘throttle’ => true,
‘view_trash’ => true,

// Forum caps
‘publish_forums’ => true,
‘edit_forums’ => true,
‘read_private_forums’ => true,
‘read_hidden_forums’ => true,

// Topic caps
‘publish_topics’ => true,
‘edit_topics’ => true,
‘edit_others_topics’ => true,
‘delete_topics’ => true,
‘delete_others_topics’ => true,
‘read_private_topics’ => true,

// Reply caps
‘publish_replies’ => true,
‘edit_replies’ => true,
‘edit_others_replies’ => true,
‘delete_replies’ => true,
‘delete_others_replies’ => true,
‘read_private_replies’ => true,

// Topic tag caps
‘manage_topic_tags’ => true,
‘edit_topic_tags’ => true,
‘delete_topic_tags’ => true,
‘assign_topic_tags’ => true,
);

And it worked! Participants could then read private topics. However, it meant that they had the exact same capabilities as moderators, which defeats the purpose of having those two different user roles. And I don’t want to make all participant users moderators. So I kept the moderator capabilities under the Participant section, however, any of the moderator capabilities that I didn’t want the participant to have, I changed it from “true” to “false.” For example, I do not want participants to be able to edit others’ topics, so I changed this part of the code:

‘edit_others_topics’ => true,

To this:

‘edit_others_topics’ => false,

That worked. However, the button to edit others’ topics still show up for the participant, but if they click on it, either nothing happens or they get an error message saying they don’t have that privilege.

The first time I tried this I deleted most of the first section, called Primary Caps:

// Primary caps
‘spectate’ => true,
‘participate’ => true,
‘moderate’ => true,
‘throttle’ => true,
‘view_trash’ => true,

But when I did that, it didn’t work again. It seems like the “‘moderate’ = > true,” part has to stay there in order for this work around to work.

So in conclusion, the participant caps section was replaced with this code:

// Participant/Default
case bbp_get_participant_role() :
default :
$caps = array(

// Primary caps
‘spectate’ => true,
‘participate’ => true,
‘moderate’ => true,

// Forum caps
‘publish_forums’ => false,
‘edit_forums’ => false,
‘read_private_forums’ => true,
‘read_hidden_forums’ => false,

// Topic caps
‘publish_topics’ => true,
‘edit_topics’ => true,
‘edit_others_topics’ => false,
‘delete_topics’ => false,
‘delete_others_topics’ => false,
‘read_private_topics’ => true,

// Reply caps
‘publish_replies’ => true,
‘edit_replies’ => true,
‘edit_others_replies’ => false,
‘delete_replies’ => false,
‘delete_others_replies’ => false,
‘read_private_replies’ => true,

// Topic tag caps
‘manage_topic_tags’ => false,
‘edit_topic_tags’ => false,
‘delete_topic_tags’ => false,
‘assign_topic_tags’ => true,
);

So that’s a work around for now. But I’d still like to know: When is bbPress going to fix this bug issue? And if they have already (and I’ve just missed it somehow): How do I correct it so that the participant user role can read private topics? If anyone has any ideas, can you please leave a DETAILED reply below, including WHERE to find the files that need to be altered. (Ex: wp-content/plugins/bbpress/includes/core/capabilities.php. I noticed that many people in this forum don’t really write down all the steps to fix things, which causes more confusion.)

[kexia]

Does anyone know the correct way to enable the participant role to read private topics? I found a bit of a work around (see below). But I’d like to know how to enable it correctly.

Even though bbPress’ documentation says that users with the Participant role can read private forums and topics, the current version of bbPress (2.5.14) allows participants to read private forum names, but not private topics names or content.

I did some searching on this site and it looks like people have been complaining and notifying bbPress about this bug for about seven years and it’s STILL not fixed. The most support help I’ve seen is someone saying the issue is because of another plugin. But that’s not the case.

I checked the bbPress code in the capabilities.php file located in wp-content/plugins/bbpress/includes/core/capabilities.php, and sure enough, the capability to ‘read_private_topics’ is not listed under the Participant’s Topic Caps section:

<blockquote cite=”// Participant/Default
case bbp_get_participant_role() :
default :
$caps = array(

// Primary caps
‘spectate’ => true,
‘participate’ => true,

// Forum caps
‘read_private_forums’ => true,

// Topic caps
‘publish_topics’ => true,
‘edit_topics’ => true,

// Reply caps
‘publish_replies’ => true,
‘edit_replies’ => true,

// Topic tag caps
‘assign_topic_tags’ => true,
);
“>

I tried adding the ‘read_private_topics’ capability to the Participant capabilities section:

<blockquote cite=” // Topic caps
‘publish_topics’ => true,
‘edit_topics’ => true,
‘read_private_topics’ => true,
“>

But that didn’t work. So then I tried copying and pasting all the capabilities from the Moderator role to the participant role, including the first part of the code under the “Primary Caps” section that lists spectate, participate, moderate, throttle, and view trash.

<blockquote cite=”// Moderator
case bbp_get_moderator_role() :
$caps = array(

// Primary caps
‘spectate’ => true,
‘participate’ => true,
‘moderate’ => true,
‘throttle’ => true,
‘view_trash’ => true,

// Forum caps
‘publish_forums’ => true,
‘edit_forums’ => true,
‘read_private_forums’ => true,
‘read_hidden_forums’ => true,

// Topic caps
‘publish_topics’ => true,
‘edit_topics’ => true,
‘edit_others_topics’ => true,
‘delete_topics’ => true,
‘delete_others_topics’ => true,
‘read_private_topics’ => true,

// Reply caps
‘publish_replies’ => true,
‘edit_replies’ => true,
‘edit_others_replies’ => true,
‘delete_replies’ => true,
‘delete_others_replies’ => true,
‘read_private_replies’ => true,

// Topic tag caps
‘manage_topic_tags’ => true,
‘edit_topic_tags’ => true,
‘delete_topic_tags’ => true,
‘assign_topic_tags’ => true,
);”>

And it worked! Participants could then read private topics. However, it meant that they had the exact same capabilities as moderators, which defeats the purpose of having those two different user roles. And I don’t want to make all participant users moderators. So I kept the moderator capabilities under the Participant section, however, any of the moderator capabilities that I didn’t want the participant to have, I changed it from “true” to “false.” For example, I do not want participants to be able to edit others’ topics, so I changed this part of the code:

true,”>

To this:

false,”>

That worked. However, the button to edit others’ topics still show up for the participant, but if they click on it, either nothing happens or they get an error message saying they don’t have that privilege.

The first time I tried this I deleted most of the first section, called Primary Caps:

<blockquote cite=” // Primary caps
‘spectate’ => true,
‘participate’ => true,
‘moderate’ => true,
‘throttle’ => true,
‘view_trash’ => true,”>

But when I did that, it didn’t work again. It seems like the “‘moderate’ => true,” part has to stay there in order for this work around to work.

So in conclusion, the participant caps section was replaced with this code:

<blockquote cite=” // Participant/Default
case bbp_get_participant_role() :
default :
$caps = array(

// Primary caps
‘spectate’ => true,
‘participate’ => true,
‘moderate’ => true,

// Forum caps
‘publish_forums’ => false,
‘edit_forums’ => false,
‘read_private_forums’ => true,
‘read_hidden_forums’ => false,

// Topic caps
‘publish_topics’ => true,
‘edit_topics’ => true,
‘edit_others_topics’ => false,
‘delete_topics’ => false,
‘delete_others_topics’ => false,
‘read_private_topics’ => true,

// Reply caps
‘publish_replies’ => true,
‘edit_replies’ => true,
‘edit_others_replies’ => false,
‘delete_replies’ => false,
‘delete_others_replies’ => false,
‘read_private_replies’ => true,

// Topic tag caps
‘manage_topic_tags’ => false,
‘edit_topic_tags’ => false,
‘delete_topic_tags’ => false,
‘assign_topic_tags’ => true,
);”>

So that’s a work around for now. But I’d still like to know: When is bbPress going to fix this bug issue? And if they have already (and I’ve just missed it somehow): How do I correct it so that the participant user role can read private topics? If anyone has any ideas, can you please leave a DETAILED reply below, including WHERE to find the files that need to be altered. (Ex: wp-content/plugins/bbpress/includes/core/capabilities.php. I noticed that many people in this forum don’t really write down all the steps to fix things, which causes more confusion.)

[deafmetal]

Forum Index (does same thing when using shortcodes), Child Forum, and Topics:

After upgrading to 2.6 RC 7, and doing forum repairs, I lost the header, categories and formatting for my forum index and child forums. The topics work just fine still.

To troubleshoot, I deactivated all plugins, removed bbPress, activated the default 17 theme, and removed my primary theme. If I re-install/activate bbpress, the index and children headers then show up, albeit without the default styling.

So I reinstalled my theme (which has native bbpress/buddypress support built in), re-activated bbpress, and the headers/categories/formatting disappeared again.

I wanted to think it was a css issue, but I had re-installed everything fresh. So it appears something corrupted my database, tied specifically to my theme. Any recommendations for how to “fix” the repairs and undo the damage?

For the life of me I cannot figure out how to fix this without a wholesale home home directory and sql db restoral. But I’d lose WEEKS of edits and css customization. Ughh

Thank you in advance!!

[Robin W]

It could be a theme or plugin issue

Themes

As a test switch to a default theme such as twentyfifteen, and see if this fixes.

Plugins

If that doesn’t work, also deactivate all plugins apart from bbpress and see if this fixes. if it does, re-enable one at a time to see which is causing the error.

Then come back

[StudentFilmmakers]

I have a forum software running in the /forums of the site so I can’t let it stay at default /forums.

[lwadz88]

Hello All,

I hope all is well.I am pretty new to this and maybe there is already a way to do or a plugin I missing. May have been discussed before but I don’t even know what to call it.

Is there a way to display a custom field from the buddypress profile under the username in the forum comments just like the default bbpress user roles (i.e. like a box containing a specified field from buddypress profile). For my purpose there is an important peice of profile information I’d like to have follow the user around whenever they make posts. Thanks!

[auxiclic]

I have a WordPress site with 4 languages english (default), french, italian and spanish :
WP v5.2.1, bbPress v2.5.14, Polylang v2.5.4
I set up the custom content types in the polylang settings : Forums, Topics, Replies

There is no problem for the english forum but I got two problems :

– for the french forum : the english words are not translated (it is fine with italian and spanish). The two bbPress-fr_FR.po and bbPress-fr_FR.mo were missing. I added them but without success.

– for the french, italian and spanish forum : I can add a topic (then it redirects to home page). When I click on it the topic link, it redirects to home page. When I try to view the topic in the back office, it redirects to home page

Thanks in advance for your help

[amaccuro]

Hello,
how can I change the forum email set in bbpress?
My intention would be to assign an email for all notifications of any kind.

I noticed that in the bbpress settings there is no setting, can you help me?

Thanks

[oneskysandy]

I am having this problem too. It looks like reply.js isn’t getting enqueued because bbp_is_single_topic is false.

/wp-content/plugins/bbpress/templates/default/bbpress-functions.php

if ( bbp_is_single_topic() ) {
…
// Hierarchical replies

if ( bbp_thread_replies() ) {
$scripts[‘bbpress-reply’] = array(
‘file’ => ‘js/reply.js’,
‘dependencies’ => array( ‘jquery’ )

This should be bbpress functionality, but I’m unsure how to fix this. Also, I checked the permission, and it looks okay.

[chemdata]

How can I make the BBP forum fit the default page size with sidebar on the right as opposed to being full width?
Thanks.

[Barry]

OK, and are you in a position to take those testing steps a little further and deactivate everything except bbPress (and also switch to a default theme)?

If you can do that, and things work, we then know the problem lies in one of your other plugins or with your theme and by reactivating them and testing you can probably figure out which one is the problem.

You could even do this ‘in reverse’ if you want to avoid disruption on your live site. This service has a funny name, but poopy.life is really useful for this sort of thing. Start with a brand new WordPress install (it’s free, though it will only stay alive for 24hrs) and add bbPress but nothing else. Confirm it works as expected, and then start adding everything else that you have on your live site: see if you can figure out what exactly introduces the problem.

[Barry]

New forum posts, or new posts generally?

What else is running on your site: for example, do you have anti-spam tools such as Akismet in place?

Something that is often worthwhile is troubleshooting by deactivating all other plugins and switching to a default, unmodified theme: if you do this and things work as expected, it would indicate that the problem is being introduced by one of those other components (or by a combination of some of those components).

[bdd]

I’ve tried the troubleshooting recommendations (all other plugins off, default theme), as well things like enabling the visual editor and bbp_tinymce_paste_plain_text — still no good.

Anyone? Any direction on what’s causing this/how to fix it? Please and thanks.

[Robin W]

It could be a theme or plugin issue

Themes

As a test switch to a default theme such as twentyfifteen, and see if this fixes.

Plugins

If that doesn’t work, also deactivate all plugins apart from bbpress and style pack and see if this fixes. if it does, re-enable one at a time to see which is causing the error.

Then come back

[abhipatodi]

To check if the user is logged in, is_user_logged_in() is used:
function is_user_logged_in() {
$user = wp_get_current_user();
return $user->exists();
}
True if user is logged in, false if not logged in.

To obtain the default data (such as User ID, User Login, etc.)of the user try this code:

global $bp;
$the_user_id = $bp->loggedin_user->userdata->ID;
$the_user_login = $bp->loggedin_user->userdata->user_login;

To get data for the current logged in user, this this:
`$the_first_name = bp_get_profile_field_data(‘field=First Name&user_id=’.bp_loggedin_user_id());

Hope you find these code lines useful.

[9march]

Hi robin,

I have the same issue on my site, I added the code as it is but when i give a user the ‘tutor’ role, After saving the role disappears and the user has no bbpress role assigned to them.Even i i signup as a subscriber, If the default role is set to be ‘tutor’ The newly registered user ends up with no bbpress role.

Thanks,

[Barry]

Hmm, it’s possible there is some sort of conflict happening.

It occasionally happens, for instance, that other plugins (or even your theme) generate additional admin menu entries at exactly the same position used by another plugin (in this case, bbPress). In such a case, one will ‘win’ and the other will not be visible. I don’t know that that is what is happening here, but it’s an example of the sort of conflict that is possible.

Do you have a staging or testing site where you can deactivate all other plugins (except for bbPress) and switch to a default theme—do the admin menu items show up then?

Alternatively, you could make use of the (humorously-named, but useful) poopy.life service to generate a brand new WordPress sandbox. It only stays alive for 24hrs, but that would possibly be enough time to see if you can install bbPress and use it successfully in a ‘clean’ environment. If you can, that would again indicate there is some kind of conflict on your live site.

You could even troubleshoot ‘in reverse’ via this sandbox site, by incrementally adding your theme and other plugins and checking to see if any introduce this particular problem.