[Stephen Edgar]

The default bbPress breadcrumb behaviour is the same behaviour that you are looking for, that’s presuming you are using the default ‘forums’ as the forum prefix in bbPress settings.

I personally haven’t used Yoast breadcrumbs plugin but if you want to continue using it I’d suggest you head over to Yoast’s support for the plugin and ask what options you have.

[Stephen Edgar]

The process is still the same, I just updated the page you mention and it was only a minor modification for the default template location in bbPress 2.2.

[guidoh]

I cannot get user registration to work. I tried t ocreate a page and apply the bbPress – User Registration template, but there is not a single bbPress template in my drop-down menu. All there is is “Default” and “Contact Info”

Does anyone know what could be causing this? Or is there some other good way to create a user registration page/section/widget?

Thanks for any leads.

[andymacleod]

I’ve been working on a MMORPG guild site with 3 distinct levels of Membership with posting rights:
– guests/potential members who can post on PUBLIC forums
– full member who can post of the guild’s PRIVATE forums
– officer/moderators who can post of HIDDEN forums.

I chose to use WordPress and bbPress instead of a dedicated guild-hosting solution to make the site different from most other guild sites, taking advantage of WordPress’s theming and bbPress’s simplicity.

bbPress 2.2.1 only seem to expect only 2 levels of membership – there is no option to have a “guest/registered” user who can post on public forums. However, I did manage to create 3 levels of member by making a small change to a core file, found here:
bbpress\includes\core\capabilities.php

Go to where the Spectator role is defined (lines 134 to 169) and change them to have the same capabilities as for the participant role (lines 225-260). Then change line 146 ‘read_private_forums’ back to ‘false’.

The problem with this approach: Your “spectator” role is now no longer merely a spectator. And, of course, this amendment would be overwritten by updating bbPress. Alternatively, you could create another role here (would be good addition for bbPress 2.3) but you need to edit other parts of the file to do so…

Another issue: I wanted custom titles to appear on topic posts beside member’s avatars. To do this, I had to create new WordPress roles using Justin Tadlock’s Member plugin. I copied the WordPress default permissions for the “Subscriber” role and gave it the name “Guest”. I did the same for the “Member” role, and I copied the default Editor roles for the guild “Officer” role – because I wanted them to be able to edit pages and posts too.

The solution seems to work although it is not ideal… I thought I’d pass it on in case there were other people in a similar position who wanted more flexibility in terms of roles. Please, please, please could making it possible to change forum roles and titles a priority update for the next major update to bbPress.

Thanks,

Andy

[John James Jacoby]

You’ll have better luck looking into the existing templates, and copying existing functionality. Check in: templates/default/bbpress/content-archive-forum.php

https://bbpress.trac.wordpress.org/browser/trunk/templates/default/bbpress/content-archive-forum.php

[Michael]

Looks like you’ll need a plugin (or something) to override the $defaults array in bbp_get_the_content() in template-tags.php.  The “teeny’ variable is hard wired to TRUE — changing this to FALSE enables whatever TinyMCE config is set (through Ultimate TinyMCE et.al.).

It would be nice if this were a configurable option in the Forums settings, right next to “Fancy Editor” tic box. 🙂

Cheers.

Michael

[John James Jacoby]

@tzeldin88 – Again, difficult to be confident, but you could filter bbPress’s role mapping, to add custom comparisons for your newly created roles. Then bbPress will just naturally make:

X site role = Y forum role

with each new user that visits the site.

The filter you’d want to use, is bbp_get_user_role_map. It looks like this:

/**
 * Return a map of WordPress roles to bbPress roles. Used to automatically grant
 * appropriate bbPress roles to WordPress users that wouldn't already have a
 * role in the forums. Also guarantees WordPress admins get the Keymaster role.
 *
 * @since bbPress (r4334)
 *
 * @return array Filtered array of WordPress roles to bbPress roles
 */
function bbp_get_user_role_map() {

	// Get the default role once here
	$default_role = bbp_get_default_role();

	// Return filtered results, forcing admins to keymasters.
	return (array) apply_filters( 'bbp_get_user_role_map', array (
		'administrator' => bbp_get_keymaster_role(),
		'editor'        => $default_role,
		'author'        => $default_role,
		'contributor'   => $default_role,
		'subscriber'    => $default_role
	) );
}

[htz77]

Hi JJJ, thanks for the rapid reply! Just to clarify:

I’m already using this custom role (Student) in other ways throughout the site, so I can’t scrap it. Participating in the Forum was one of the things a Student could do, and participation in the Forum was restricted to ONLY Students.

I don’t actually have many Students yet, so I can actually just delete and re-add them, to fix any wrong/old capabilities, and avoid any “resetting”.

The issue is really more about simplifying the process for my client (the site admin) — so he doesn’t need to set a Student’s role in two different fields, in the admin: the normal wp Role field, and now this new Forum Role drop-down (which is at the bottom of the profile screen).

So I think I need the DEFAULT bbPress Role to be Spectator (for public / non-logged-in users, and another custom role, called Schools), so they can’t participate.

And I’d like my Student role to have the same (EFFECTIVE) Capabilities as a Participant, so the site-admin doesn’t need to set that separately. But it sounds like you’re saying that’s just not really possible, even though the Members plugin SEEMS able to assign the capabilities correctly.

Thanks again for your time and attention.
-Todd

[jakewho]

I just switched back to a default theme and I am still experiencing the same issue??

[John James Jacoby]

Likely something in your theme. What happens if you switch back to a default theme?

[fuzzybee]

I’m trying to create a custom forum index page which should look exactly like the default forum index page with forum names, number of topics, number of posts, last active topic etc. but sorted alphabetically based on forum names.

I’m looking at at bbp_has_forums, bbp_forums and bbp_list_forums inside /wp-content/plugins/bbpress/bbp-includes/bbp-forum-template.php.

However, I’m puzzled which function to use and
What arguments/ parameters I should pass?
the comments in bbp-forum-template.php itself says the same parameters as WP_Query() but would it make sense at all to have something like “post_type” => “forum”
I’m sure one can be clearer/ more explicit about the parameters here in some form of documentation

I gave it wild tries as follows
1) The following gives me fatal error:

$args = array(

'orderby' => 'title',
'order' => 'ASC',

);

while (bbp_forums($args)){
bbp_the_forum();

echo bbp_get_template_part( 'content', 'archive-forum' );

}


The error:
Fatal error: Call to undefined method stdClass::have_posts() in C:\www\forums.local\wp-content\plugins\bbpress\bbp-includes\bbp-forum-template.php on line 109 Call Stack: 0.0004 333592 1. {main}() C:\www\forums.local\index.php:0 0.0006 337280 2. require(‘C:\www\forums.local\wp-blog-header.php’) C:\www\forums.local\index.php:17 0.3864 38499368 3. require_once(‘C:\www\forums.local\wp-includes\template-loader.php’) C:\www\forums.local\wp-blog-header.php:16 0.3920 38515824 4. include(‘C:\www\forums.local\wp-content\themes\bp-tap\custom-index.php’) C:\www\forums.local\wp-includes\template-loader.php:43 0.4732 38674368 5. bbp_forums() C:\www\forums.local\wp-content\themes\bp-tap\custom-index.php:42

2) While the following just takes forever to load:

$args = array(

'orderby' => 'title',
'order' => 'ASC',

);

while (bbp_has_forums($args)){
bbp_the_forum();

echo bbp_get_template_part( 'content', 'archive-forum' );

}


I’m using WordPress 3.4.2 and bbPress 2.1.2.
I’ve copied all files and directories from /wp-content/plugins/bbPress/bbp-themes/bbp-twentyten/ to my theme directory.

• This topic was modified 12 years, 12 months ago by fuzzybee.
• This topic was modified 12 years, 12 months ago by fuzzybee.
• This topic was modified 12 years, 12 months ago by fuzzybee.
• This topic was modified 12 years, 12 months ago by fuzzybee.
• This topic was modified 12 years, 12 months ago by fuzzybee.
• This topic was modified 12 years, 12 months ago by fuzzybee.
• This topic was modified 12 years, 11 months ago by fuzzybee.
• This topic was modified 12 years, 11 months ago by fuzzybee.

[John James Jacoby]

bbPress 2.2.1 takes another step towards automating this for installations with custom roles. If you have custom roles, bbPress will now fallback to the default role for those users.

[John James Jacoby]

Up to you and your needs. Personally, I’d tick the box, and I suspect you’ll want to too. The reason it’s there is more for installations like WordPress.com, where the process of adding a user to a blog actually means something completely different than it does under normal circumstances.

Also, if the box isn’t ticket, bbPress doesn’t create a profile for that user, because they won’t have a *real* role on the site. They’ll be registered, but have to assigned role; bbPress will just dynamically assign the default to them on the fly when they’re using the site.

[rossagrant]

MASSIVE thanks go out to nerrad and JJJ for this fix!

Seems to work just perfectly.

So JJ, do you think I now need to tick the box in the back end to assign a default level to new sign-ups, or does this patch dynamically assign the ‘member’ role to all new sign-ups too?

[Sami Keijonen]

I finally started playing with bbPress. There are lot to learn because I want to display topics totally differently what is the default output.

First I want to display latest topics by latest activity like usual. I’ve created archive-topic.php in my theme so I can decide output.

After that I can filter topic post type so that topics are ordered by latest activity.

add_action( 'pre_get_posts', 'my_filter_topic' );

function my_filter_topic( $query ) {

if( $query->is_main_query() && is_post_type_archive( 'topic' ) ) {

$query->set( 'meta_key', '_bbp_last_active_id' );
$query->set( 'orderby', 'meta_value_num' );
$query->set( 'order', 'DESC' );

}

}

But this doesn’t display sticky posts first. They are more like last. Does someone have an idea how I get sticky posts to show first?

[Darren Ethier (nerrad)]

see the comments posted in the ticket jjj, the problem is that a role created by a plugin isn’t in the default map, and thus it won’t get handled (b/c any roles not in the default wp_roles don’t get handled). I added a patch to the ticket.

[edit: my brain is mush and translating to really bad grammar]

[John James Jacoby]

My first guess is s2member hooks in too late, or some other plugin is loading the current user way too early in the stack. bbPress doesn’t perform any of those actions until it expects WordPress to make them happen naturally.

If the current_user is loaded before the ‘after_setup_theme’ action is called (because of an is_super_admin() check, a call to current_user_can(), etc…) bbPress fails gracefully, and waits until it’s time. If S2member waits until init to add its roles, or if the WP_Roles array doesn’t include the s2Member roles by the time ‘after_setup_theme’ has fired, $wp->init(); will get called, loading the current user, and bbPress will map the roles accordingly.

Another possible problem is bbp_get_user_role_map() not mapping custom roles; it only maps to WordPress core roles. A possible fix to bbp_set_current_user_default_role() would be to array_diff() editable_roles() vs bbp_get_dynamic_roles(), loop through them, use the map where it matters, and use the default role otherwise.

[Darren Ethier (nerrad)]

s2member does do that. But for whatever reason, those roles aren’t being picked up by bbp_set_current_user_default_role() (via $bbp->current_user->roles)

[John James Jacoby]

bbPress 2.2 implements a new way to think about user roles in both WordPress and bbPress. A few users have posted up having issues after upgrading, so I’m going to take some time to explain what changed and why.

The problem bbPress 2.2 addresses, is the situation where a users ability to take certain actions in the forums was dictated by their role on the entire site, or their “blog role” as I’ll refer to it in some places going forward.

This means that in the past, a user could not be both a blog Editor and a forum Moderator at the same time; you’d need to be one or the other, and it was clear this wasn’t what anybody wanted.

In bbPress 2.0 and 2.1, every time you activated bbPress on a site, it went in and added a bunch of capabilities to the database. You never knew this, but it needed these roles so that users could perform certain tasks. bbPress would go in and modify the core WordPress roles, to add these capabilities to them. This made multisite installations a challenge, and network activation was very difficult too, because these roles needed to be added to every single site.

For existing users of sites, bbPress performed a bunch of calculations and educated guesses to automatically grant users with certain roles and capabilities. To do this, it would eventually need to add capabilities to the user, or switch them to a role that had those capabilities already; Forum Participant.

Subsequent updates to bbPress required database migration scripts for every change to user roles and capabilities. This is a lot of work for very little gain, since we’re not solving any problems with users needing multiple roles, and at the same time we’re polluting the database with a bunch of data that doesn’t change 99% of the time.

—

Under the hood, WordPress comes with support for users having multiple roles, and this is a perfect use-case for needing that functionality. Roles are just groups of capabilities. If a user has a role, it’s safe to assume they also have certain capabilities, right?

Wrong. Kind of. Sometimes.

Capabilities are saved in the database, per user, per site, and they bubble based on the role they are granted. If you use any plugin that modifies editable roles or capabilities in the database, what you’re doing is changing the individual capabilities for every user that gets that role going forward, but not necessarily every user that had that role in the past.

Remember, individual users have individual capabilities. When a user gets a new role that is modified in some way, they also get assigned the changed capabilities, either positive or negative. Negative capabilities are explicitly negative, and neither WordPress nor bbPress use these in core. They’re tricky, and make it easy to break things.

Once you’ve gone this far in, you’re playing with fire and will likely get burned. You now have altered core user roles, extra forum user roles, and a mish-mash of registered users with a random assortment of capabilities, based on when they signed up, what role they were granted, and what you happened to have changed that blog role’s capabilities to be at that moment.

To top this all off, there is no “repair” for your users, they’re basically stuck.

For bbPress users that never modified user roles or capabilities, their update process would be smooth sailing. It’s the modifications to database permissions that cause issues with bbPress 2.2. Why?

bbPress 2.2 introduces the concept of “dynamic roles” VS WordPress’s “editable roles.” What’s the difference? Editable roles are saved in the database, and allow you to completely shoot yourself in the foot (as above) once you start changing them around. Dynamic roles do not touch the database in any way, other than to assign the 1 role to the user, side-by-side with any other role they might have on your site.

bbPress comes with filters to allow you to modify the roles, and it’s still possible to add or subtract specific forum capabilities to a user if you needed to, and without all the fuss and danger of bbPress interfering with existing user roles and capabilities.

For users that are stuck with users that can’t access the forums, try using the forums role repair tool, located in: Admin > Tools > Forums

That tool loops through your users, and grants them a forum role based on their blog role based on the following map:

Admin = Keymaster
Editor = Participant
Author = Participant
Contributor = Participant
Subscriber = Participant

The map can be filtered, as can the default role of Participant. The problem will come in with existing users that have modified Participant roles that you may have tinkered with. They’ll end up with capabilities that are totally out of whack, no matter what you do. You’ll need to use an additional tool on top of this, if you want to clean up those old roles introduced by plugins like S2member.

Going forward, I’d like to get a better idea on what these plugins are doing, and make sure that bbPress plays as nicely as it can with them. Dynamic roles in WordPress core are probably a few releases away, but it’s important to bbPress’s future to have them in and working as soon as possible, to get everything dialed in for everyone.

[Anonymous User 7670885]

Latest question, sorry…

What is: Automatically assigns the default role to new, registered users upon visiting the site?

ATM new user is set to Participant from default… What expect if i enable this? Someone can try to best explain (yes, i know, my English is really poor… i’m sorry) 😐

[Darren Ethier (nerrad)]

which of course means that ANY plugin that adds users to different roles than what bbPress expects won’t have a default forum role applied.

[John James Jacoby]

Any idea why bbPress’s bbp_set_current_user_default_role() function isn’t working?

[Darren Ethier (nerrad)]

hmm … sorry if it’s already in this thread but do new signups in s2member (for various s2member roles) get the default bbPress role added (if that’s selected in the bbPress forums options)? There is an “Auto role” checkbox in `options-general.php?page=bbpress` that when checked is supposed to automatically assign default roles to new, registered users upon visiting the site…. I’ll have to check into that and see if new s2member registered users get that default role…

[John James Jacoby]

@rossagrant – it already tries to do that, via: Settings > Forums — Auto role —

“Automatically assign default role to new, registered users upon visiting the site.”

Basically, that bit looks for users with no bbPress role, and automatically gives it to them (without interfering with existing WordPress roles.)

I think the problem comes from having modified the bbp_participant role previously in the database, and bbPress not using those modified caps any longer. (Just a guess.)

bbPress moved away from “editable roles” in 2.2, since plugins like s2member and Members allow for manipulating bbPress’s roles in such a way that safe updates to bbPress are pretty much impossible; the moment we change our capability mapping, this all blows up.

Going forward, bbPress uses dynamic, secondary roles, that won’t interfere with any other capability or role on the site. I.E. a user can be a forum moderator and a blog editor, or a blog admin and and a forum participant, or no role on the blog, and a key master in the forums.

This type of setup is best for 95% of installations, but anyone that’s relying on roles in the DB are currently stuck (like we see here.)

One possible solution is to just let your database roles override bbPress’s dynamic roles. You can unhook most of those functions, but I don’t think that’s advisable for the long term, because you’ll lose any capability updates going forward, leaving some users in limbo when new features are introduced.

[Anonymous User 7670885]

Like from object… No more Ultimate TinyMCE (no more other button except wp default) in Fancy editor after latest (2.2) bbpress update :/