bbpress just uses wordpress authentication, so probably the answer is no
and for different forum access look at
Private groups
Hi,
New to bbpress. Just installed.
We have WordPress custom roles and I need to limit access to forums based on custom roles.
1. Is it possible to limit forum visibility (forums, post, widgets) based on WP custom user roles?
I have many user roles and would like to limit it by user role “MainGroup” that is set up for users that have certain access.
2. Is it possible to do the above but based on role combinations, eg give access to users with role “MainGroup” AND “Learner” user groups?
3. Is it possible to set user access on a per forum basis or globally (all forums)?
Many thanks for any help and advice.
Ben
bbpress just uses WordPress users so if your plugin is not using wordpress users,the answer is probably no.
Maybe ask the private content plugin authors.
We are using a plugin called PrivateContent on a client portal site, which allows us to make the site private and give employees access to the site behind a firewall. We installed BB Press so employees can have a forum, but the users set up in PrivateContent are unable to participate in the forum; apparently only WordPress users are able to participate. Is there a work-around for this?
what wordpress and bbpress roles do users have?
it could be a theme or plugin issue
Themes
As a test switch to a default theme such as twentytwenty, 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.
If you cannot do this to your site (say because it is live) then use the ‘troubleshooting’ features of this plugin to let you test without affecting other users
Health Check & Troubleshooting
Then come back
Install
bbp style pack
then
dashboard>settings>bbp style pack>Subscription Emails
dashboard>settings>bbp style pack>Moderation
install the ‘check and log’ plugin, enable logging and see if the issue is sending from the site or within your email system. so if showing in the log, then website is creating.
May well be the sending address, you could use style pack to change the sending address to a real one, lots of email stuff hate ‘noreply@’ addressses
Install
bbp style pack
once activated go to
dashboard>settings>bbp style pack>Subscription Emails
Ive recently installed bbpress to a wordpress website and behind the forum there is a white box, i have eddited bbpress.css and the box is still there, any ideas on how to remove it?
If there are no keymasters, then
bbp style pack
once activated, navigate to
dashboard>settings>bbp style pack>bug fixes and you will see the options to make yourself the keymaster
You can then deactivate and remove the style pack plugin, or look at what it offers
In the new version, I am encountering a major issue where all AJAX functionality, as well as BuddyPress and other plugins, are not working properly.
I have checked every scenario, including using the default WordPress theme, and consistently face issues due to the new version of bbPress.
I kindly request you to resolve this issue as soon as possible, as my client has raised a refund request because of this problem.
Security risk: privesc. It could be possible to elevate a user’s privileges to a higher permission level.
Severity: critical
Fixed in: 2.6.5
Security risk: privesc. It could be possible to elevate a user’s privileges to a higher permission level.
Severity: high
Fixed in: 2.6.5
Security risk: xss. Data from an attacker could be interpreted as code by site visitors’ web browsers. The ability to run code in another site visitors’ browser can be abused to steal information, or modify site configuration.
Severity: medium
Fixed in: 2.6.0
Security risk: xss. Data from an attacker could be interpreted as code by site visitors’ web browsers. The ability to run code in another site visitors’ browser can be abused to steal information, or modify site configuration.
Severity: medium
Fixed in: 2.6.5
Security risk: sqli. The plugin contains a vulnerability wherein unauthenticated visitors could inject SQL statements into WordPress. SQL injection could allow an attacker to gain control of your site.
Severity: low
Fixed in: 2.0
Security risk: xss. Data from an attacker could be interpreted as code by site visitors’ web browsers. The ability to run code in another site visitors’ browser can be abused to steal information, or modify site configuration.
Severity: low
Fixed in: 2.5.9
Security risk: sqli. The plugin contains a vulnerability wherein unauthenticated visitors could inject SQL statements into WordPress. SQL injection could allow an attacker to gain control of your site.
Severity: low
Fixed in: 2.0
Security risk: xss. Data from an attacker could be interpreted as code by site visitors’ web browsers. The ability to run code in another site visitors’ browser can be abused to steal information, or modify site configuration.
Severity: low
Fixed in: 2.5.10
Security risk: sqli. The plugin contains a vulnerability wherein unauthenticated visitors could inject SQL statements into WordPress. SQL injection could allow an attacker to gain control of your site.
Severity: low
Fixed in: 2.5.13
Install
bbp style pack
once activated go to
dashboard>settings>bbp style pack>Topic Form Additional Fields
ok, you are doing stuff with combinations of old versions of software – I can only help with current.
Wordpress 6.x dramatically changed how WordPress works, and Twenty Twenty-Two is one of the new FSE themes.
So on WordPress 6.5.5 with Twenty Twenty-Two you will need the fix mentioned above. BBpress 2.6.11 is the current version of bbpress and should also be used.
Regards
Robin
Hello Robin,
I am using the default Twenty Twenty-Two Version: 1.2 theme provided by WordPress in version WP 6.0.9, without any customizations.
Does that too need the above fix you mentioned?.
Also I have earlier version of BBpress i.e 2.6.9 working fine with WordPress 5.8 installed on one of a server, which works absolutely fine without any such issues.
Any way to debug the possible cause ?. Cause no errors in apache logs as well.
I suspect you are using an FSE theme, so you need a fix to work with bbpress.
install
bbp style pack
once activated, navigate to
dashboard>settings>bbp style pack, and you should see the first tab called ‘Theme Support’ – if you don’t see this, come back.
In that tab, select
Enable Theme Support
and save
The forums should then display
Nothing new
The following 13 errors fixed
View RSS feeds return the all-topic feed if the view doesn’t exist
After export from SMF error: bbp_converter_db_connection_failed
BBP_Converter_DB does not have a method “__destruct
Restoring a trashed topic will set the post status to ‘draft’ as of WordPress 5.6.0
Default arg to “bbp_add_forums_roles()” can cause errors
Reduce subscription email subject duplication
Editor buttons missing since 2.6.8 upgrade
bbp_get_reply_url() generates incorrect link for a spammed topic
Search displays hidden forums to participants
The content-archive-forum.php template does not filter if the search form should be displayed
Recount topics for each user, counts only published topics
Statistics widget throws Undefined index if no replies or topics tags
“You may use these HTML tags and attributes:” not escaped correctly
If anyone out there needs to quickly do an emergency fix to their live site before updating to 2.6.11, here are the changed lines of code between 2.6.10 and 2.6.11:
https://bbpress.trac.wordpress.org/changeset/7272
I’m not advocating for hacking on weird files on live sites, but I understand everyone’s situations are different, and thought maybe this could be helpful to see.
Apologies to everyone who was quick to install 2.6.10 and had a scare.
It has been a few years; I’m out of practice and botched it.
I backported the 2.6.11 fix to the 2.6.10 tag, so in the unlikely event anyone still downloads 2.6.10 it will not be broken like it was.
Go get 2.6.11 from: https://wordpress.org/plugins/bbpress 💚
I have raised a trac ticket for this release which hopefully the authors will look at
https://bbpress.trac.wordpress.org/ticket/3601
Chuckie, try logging in using the standard WordPress login page and rollback to the previous version.
https://publictalksoftware.co.uk/wp-login.php
