Search Results for '+.+default+.+'
-
Search Results
-
In case a user change his display name to be diffrent from his username, you cannot use @someusername to mention someone since you do not know what the users username is.
Would be nice to be able to optionally include an
@someusernamejust below the link to a reply or topic authors profile.Perhaps the best way of doing this would be to add an extra argument to the args array for the bbp_get_reply_author_link function. The current args are:
$defaults = array (
'post_id' => 0,
'link_title' => '',
'type' => 'both',
'size' => 80,
'sep' => ' ',
'show_role' => false
);But could be changed to:
$defaults = array (
'post_id' => 0,
'link_title' => '',
'type' => 'both',
'size' => 80,
'sep' => ' ',
'show_role' => false,
'show_mention' => true,
);I know having the user name visible is kind of a security issue, but since the user name already is visible in the profile URL…
Also, a setting for this in the backend would be nice.
Once can check “Use the fancy WordPress editor to create and edit topics and replies”, yes.
However, the problem is such editor confuses people.
(I don’t suppose majority of my audience recognise, not to mention knowing how to use HTML)1) “Visual” and “HTML” what the heck?
2) They don’t intuitively know that they need to switch to the “HTML” editor to insert images.The editor used here is not fantastic but it is much better than the default WordPress one, for forums.
Topic: User registration
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.
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.phpGo 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
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 documentationI 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:422) 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 13 years, 4 months ago by
.
-
This topic was modified 13 years, 4 months ago by
-
This topic was modified 13 years, 4 months ago by
-
This topic was modified 13 years, 4 months ago by
-
This topic was modified 13 years, 4 months ago by
-
This topic was modified 13 years, 4 months ago by
-
This topic was modified 13 years, 4 months ago by
-
This topic was modified 13 years, 4 months ago by
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?
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 > ForumsThat 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.
-
This topic was modified 13 years, 4 months ago by
