Hi Robin,
thank you for your reply. The code in that resource isn’t quite satisfactory but it gave me a head start.
I came up with the following function to disable the wp toolbar:
// disable wp toolbar on the frontend of website for role:'subscriber'
function disable_admin_bar() {
if (current_user_can( 'subscriber' ) ) {
show_admin_bar( false );
}
}
add_action( 'after_setup_theme', 'disable_admin_bar' );
and the following to disable wp-admin:
// not allow access to wp-admin backend for role:'subscriber'
function sub_no_read_wpadmin(){
$role = get_role( 'subscriber' );
$role->remove_cap( 'read' );
}
add_action( 'admin_init', 'sub_no_read_wpadmin' );
Hopefully this is sound. Do you see any problems with this implementation?
Do you really have two :: in your CSS file? There should be one.
put this in the custom css part of your theme
.archive-description {
display : none !important ;
}
Hi
What I want to get rid of is the one marked with the arrow (which I underlined) in the image: https://prnt.sc/u0h1vn, not what I gave sign (x)
And your code changes to writing that I marked (x)
it should work, try
add_filter( 'bbp_get_forum_archive_title', 'tcv_forum');
function tcv_forum () {
return 'forum-diskusi' ;
}
Hi
Thank you for giving the code
But you don’t seem to understand what I mean
Your code omits “Diskusi” instead of “Arsip”
What I want is to remove the words “Arsip” at the top (not on the page), not to remove the words “Diskusi”
How to solve it?
Thank you
Put this in your child theme’s function file –
ie wp-content/themes/%your-theme-name%/functions.php
where %your-theme-name% is the name of your theme
or use
Code Snippets
add_filter( 'bbp_get_forum_archive_title', 'tcv_forum');
function tcv_forum () {
Return 'Forum' ;
}
Hi there,
I am currently setting up a bbpress forum. This is why I post a view threads atm because I have questions. Hopefully, it’s not perceived as spam.
I know that this is not a bbpress issue, more of a wordpress thing in general. However, I guess that most bbpress developers/admins have solved this issue – therefore I ask it here.
I want to disable access to wordpress admin dashboard for all normal forum participants (role: subscriber/participant).
I have done some searching and found that it could be achieved through the following custom php.
disable wp-admin:
// redirect back to homepage and not allow access to wp backend for subscribers
function rkk_redirect_admin(){
if ( ! wp_doing_ajax() && ! current_user_can( 'edit_posts' ) ) {
wp_redirect( site_url() );
exit;
}
}
add_action( 'admin_init', 'rkk_redirect_admin' );
disable wp admin toolbar:
// disable wp toolbar on the frontend of website for subscribers
function rkk_disable_admin_bar() {
if( ! current_user_can('edit_posts') )
add_filter('show_admin_bar', '__return_false');
}
add_action( 'after_setup_theme', 'rkk_disable_admin_bar' );
I included that code in functions.php of childtheme. However, it does not seem to have an effect. Subscriber can still access wp-admin and can see the wp toolbar in the front end.
Anybody have a good solution for this? I don’t want to use an extra plugin for that.
thank you for helping. best regards, peter
I want image to be displayed in left of forum title. Any code that I can add to snippet?
#bbpress-forums is the ID for forums – suggest you ask here on how to hide breadcrumb
https://wordpress.org/support/plugin/breadcrumb-navxt/
Hello,
I would like to select with CSS selector for BBpress forum pages to hide Breadcrumb NavXT.
Is there a CSS code ?
THanks for your help.
Hi I have embedded a forum into a WP page with the shortcode.
Displaying and browsing the forum works as it should but when I clik on the “subscribe” button, the page reloads and I’m not subscribe for alerts on that forum.
Seems to be doing that only when I embed the forum in another page.
If I go directly to the forum, then the button works.
Looks like something with the “rewrite” string or something like that.
Any clue how I could fix that ?
Put this in your child theme’s function file –
ie wp-content/themes/%your-theme-name%/functions.php
where %your-theme-name% is the name of your theme
or use
Code Snippets
add_filter('bbp_has_replies_query', 'rew_modify_replies_query');
function rew_modify_replies_query($bbp_r) {
$bbp_r['order'] = 'DESC';
return $bbp_r;
}
add_filter('bbp_show_lead_topic', 'rew_show_lead_topic');
function rew_show_lead_topic () {
return true ;
}
I have to sort topics and replies in bbpress forum changing code how can I do it?
Hi I think i have the exact same problem.
What I notice is when a forum is embedded in another page throught either a URL or SHORTCODE.
The subscribe button simply does not work.
When I got directly at the forum, the button works.
Is it the same for you ?
Thanks. I tend to stick with the visual TinyMCE editor rather than the text editor because toggling the editors messes up my code example snippets.
This worked for me:
<center>
<img src="https://i.imgur.com/W6QaJvk.jpeg" width=216 height=298>
</center>
@2cats, just out of curiosity is it the mechanics of putting in the patch that you’re uncomfortable with. Or it it the fact that you (or your clients) would then have to deal with the patched code when updates happen.
Also I’m assuming that you’re aware of the plug-in mentioned above that fixes some of the current bbPress bugs.
Clearly the bbPress developers (who donate their time) can only do so much. But I too am curious how the priorities are set. BuddyPress recently ran a survey asking users about their priorities. I wonder if there is something like this in the works for bbPress. Sometimes I also wonder about the feasibility of a group of users with specific needs *hiring* a bbPress developer to make certain fixes and integrate them into the build. But these are just random thoughts of someone who doesn’t really know much about how these things work.
topics can be ‘sticky’ or ‘super-sticky’
sticky posts go at the top of their forum
Super sticky posts go at the top of every forum
sounds like your topics are becoming super sticky
you can look at these in then backend
dashboard>topics>edit topics and select topic > topic attributes on top right hand side> Type
they can also be set in front end
where in the topic they show in admin as
stick (to front)
if you click the ‘stick’ then it is sticky, if you click the ‘(to front)’ it becomes super-sticky which is very easy to do by mistake.
on relationships, bbpress uses wordpress ‘post-parent’
so a reply has a post parent of the topic it belongs to
a topic has a post parent of the forum it belongs to
and a forum has a post parent of a forum if it is a sub forum, or a category if it belongs to a category
These relationships are also stored in the post_meta table
details on ‘children’ are not kept – for instance displaying topics is done by a function called bbp_has_topics which selects topics where the post_parent is the forum concerned. bbp_has_relies has a similar serach for replies where the post_parent is the topic concerned.
I’m not exactly sure how to describe this problem. But I’ve seen this happen twice now. The situation is that there are several forums, and each one has a “sticky” post at the top, describing the guidelines for the particular forum.
At some point, the post at the top of one forum is duplicated on all the forums. So forums B, C, D, … all have the “forum A Guideline” post at the top of them (in addition to their own guideline post).
I’m not very good with images, but I hope this kind of shows what’s happening:
https://num9.com/wp-content/uploads/2020/08/foo.jpeg
FWIW, when I look in the database. The post in question shows its parent as the proper forum.
On a related note, I’d love to know how bbPress figures out the relationship between forums, topics, and posts. I see that each element has a pointer to its parent. But I haven’t been able to figure out where the pointers to a forum or post’s children are.
The only documentation I was able to find on the database is:
Stored Database Data
Could somebody point me to further documentation? Or let me know if I just need to read the code (specific pointers would be appreciated).
I edited the php file indicated in the trac ticket. On my setup this is:
public_html/wp-content/plugins/bbpress/includes/replies/functions.php
This is a very simple change to one line, but it does require editing the bbPress code, and (AFAIK) can’t be done in a child theme. So you would have to keep this in mind every time you update bbPress.
If you’re not familiar with doing this type of thing, then you probably want to either:
(1) Consider using by bbp-style-pack by @robin-w, which I *believe* fixes this. Robin can answer questions about that.
(2) Just wait for the bug to get fixed. I don’t really know how the priorities for bugs are set, but my impression is that this one could take a while. I might be wrong.
This is a possible fix for this:
add_filter(
‘elementor_pro/utils/get_public_post_types’,
function($post_types) {
$post_types[‘forum’] = ‘Forum’;
$post_types[‘topic’] = ‘Topic’;
$post_types[‘reply’] = ‘Reply’;
return $post_types;
}
);
Source:
https://elementor.com/blog/introducing-hello-theme/#comment-58192
Sadly this could not be the perfect solution, specially if you are using bbpress without buddypress, it seems that you could get 404 pages on user profiles.
Right now I’m trying to use a combination of bbpress + buddypress, and for me the user profile (buddypress) is working fine.
create a page and call it the same as your forum slug (usually forums)
then in that page put the message you want followed by
[bbp-forum-index]
(If you are using Gutenberg, then as this as a shortcode block)
this will then be your forums page
In any case thanks for your time!
Hope developers will fix this bug soon.
Currently, this bug can be fixed using the code below.
Also, Replies box should be moved below Custom Fields
/* Fix BBpress 2.6 bug with Custom Fields */
if( function_exists( 'bbp_get_version' ) && version_compare( bbp_get_version(), '2.5' ) > 0 ) {
add_action( 'wp_ajax_add-reply', 'wp_ajax_add_fix_bbpress_26');
function wp_ajax_add_fix_bbpress_26() {
// print_error_log( $_POST );
// $_POST['action'] = 'add-meta';
wp_ajax_add_meta();
}
add_action( 'wp_ajax_delete-reply', 'wp_ajax_delete_fix_bbpress_26');
function wp_ajax_delete_fix_bbpress_26() {
// print_error_log( $_POST );
wp_ajax_delete_meta();
}
add_action( 'add_meta_boxes', 'bbpress_26_fix_add_meta_boxes', 25 );
function bbpress_26_fix_add_meta_boxes() {
do_action( 'bbp_topic_attributes_metabox' );
}
}