Thanks, Robin — that would be absolutely fantastic!
With a smooth and simple solution like that, I could even consider importing 3–4 more posts that originally were discussion posts and would fit much better in the forum. But no larger volumes than that.
I don’t know exactly how you’re planning to solve it, but if possible, it would be great to keep the original post and its comments intact until everything is confirmed to be working. If it’s easier to convert the existing content directly, that’s perfectly fine as well.
In our system, users also have the option to delete their own accounts if they wish. I assume we therefore need to take into account that some users who commented may no longer have a valid user ID. In that case, I guess a fallback user is needed? I do have such a user in my system called “Deleted User,” whose user ID could be used if necessary.
I’m also not entirely sure how bbPress handles topics and replies when the original user accounts are deleted — I haven’t had a chance to test that yet. 🙂
Many thanks for your help. I really don’t have the required level of knowledge for this, so it’s very much appreciated. 🙂
(I am using latest wp and PHP 8.3 FPM)
I’m encountering a strange behavior in my new bbPress installation. Here’s what happens:
Setup:
• Forum: “General”
• Sticky post in this forum containing the rules (closed for replies)
• A test topic: “Now I’m drinking coffee”
• A reply added to the test topic
Steps to Reproduce:
1. Create the topic “Now I’m drinking coffee” in the “General” forum.
2. Add a reply to this topic. Everything works as expected.
3. Go to wp-admin → Topics → All Topics.
4. Move the “coffee” topic to the trash.
Observed Behavior:
• The reply added to the trashed topic also goes to the replies trash.
• Its post_parent changes from the “coffee” topic to the sticky rules post (still published).
• If I restore the topic from the trash, the reply is no longer associated with the topic.
Expected Behavior:
• The reply’s post_parent should remain linked to the original topic.
• When emptying the topics trash, the reply should be deleted along with the topic, similar to how comments are handled with regular posts.
Environment:
• bbPress latest version
• WordPress latest version
• No child theme active
• Plugin: “Enable bbPress for Block Themes”
Has anyone else experienced this, or is there a fix/workaround?
Hi. I’m running a site with a brand-new forum. I haven’t imported anything and have only created a few test topics. I’m getting the same 500 error, and in my case PHP also tries to allocate memory endlessly.
Creating replies on the frontend works perfectly, but not via wp-admin → Replies → Add New Reply.
Every time I try, an empty reply is created with post_parent set to 0. I assume these empty replies are left floating around in cyberspace and have to be manually deleted from the database?
I’d also appreciate any help. I’m using the Blog FSE theme and the latest version of bbPress, together with the plugin “Enable bbPress for Block Themes”. We do not have a child theme active.
I noticed that this thread is almost a decade old at this point, so I’m looking for an update on measures bbPress has taken to bring your plugin up to the latest WCAG standard, especially in light of recent updates to Title II of the ADA stating that all state and local government web properties must be compliant with WCAG 2.1AA.
Please let me know if you have created a VPAT or Accessibility Conformance Report recently. Also, if you have a link to your accessibility statement I would love to have it for my records since our agency would like to be able to use your plugin from time to time but enforce the policy that all the plugins we use prioritize accessibility. Thanks!
Bonjour,
Je me permets de vous contacter concernant un problème d’accessibilité sur le forum BBPress du site rayons.handivelo.fr. Plus précisément, j’utilise le shortcode [bbp-topic-form] pour permettre aux utilisateurs de créer un nouveau sujet.
Problème rencontré :
– Je parviens à lire les champs du formulaire avec mon interface vocale, mais la liste déroulante des forums/catégories n’est pas accessible.
– Mon lecteur d’écran indique qu’il y a 19 éléments dans la liste, mais je ne peux pas les lire ou les sélectionner correctement.
– Pour information, je suis non-voyant et j’utilise un logiciel de synthèse vocale pour naviguer.
Questions :
1. Existe-t-il un autre shortcode ou une alternative pour rendre cette liste déroulante accessible ?
2. Serait-il possible de remplacer la liste déroulante par des boutons radio ou des cases à cocher pour faciliter la sélection ?
3. Avez-vous des bonnes pratiques ou des plugins à recommander pour améliorer l’accessibilité des formulaires BBPress ?
Contexte technique :
– Site : rayons.handivelo.fr https://rayons.handivelo.fr
– CMS : WordPress + BBPress
– Interface utilisée : Lecteur d’écran (ex : JAWS, NVDA)
Je reste à votre disposition pour tester toute solution que vous pourriez proposer. Merci par avance pour votre aide, et je vous souhaite une excellente année 2026 !
Bien cordialement,
Christophe
I will have to keep testing it, but it appears that posting a topic solved the problem.
What would the root cause of this issue?
Looks like these PHP warnings are coming from bbPress trying to read $_SERVER[‘HTTP_HOST’], which can be undefined in some environments. It might help to define or check that variable first, or test with debugging enabled to narrow down where it’s triggered
Thanks again!
Yes, problem is fixed and I will definitely do a test with 2025 and the plugins – I am also curious about this topic.
I will write again, if I find something
but still astonished how something like this effect can happen
I’m just a moderator here – an unpaid volunteer, I’m not a bbpress author.
There will be a reason for it, and it is almost certainly site specific, no problem on my test site, and with 100,000 installations of bbpress not one I have seen or heard of in 14 years of supporting bbpress.
The code above is not a ‘fix’, it is just a way to get bbpress to ignore the setting, which allows your site to work.
Anyway glad you are fixed 🙂
that would be worth trying.
untested, but you could first try
add_filter ('bbp_use_autoembed', 'rew_turn_off', 20,1 ) ;
function rew_turn_off ($value) {
return false ;
}
Thanks, and yes I was considering whether a function in your child theme might be affecting this.
so since you can test easily (that is untick the option, save and see if it remains unticked), then my next step would be to see what could be affecting this.
So my next step would be that 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.
Then come back
ummm, ok I have not seen this happen before.
As a test, can you untick another option and save – I need to work out if it is that setting or any setting on that page that is not working.
on your latter point, I am just a moderator here, and not a bbpress author.
The authors tend to release updates every few years, rather than more frequently.
My personal view is that you should consider bbpress to be a ‘mature’ product, ie any releases will be to fix issues rather than add functionality.
bbpress is written really well, and has loads of hooks. In essence it is a WordPress product, written by the founder of WordPress, and taken into a plugin by sponsorship from WordPress.
There are no show stopper bugs in it, it may throw a few notices (and these are very few at the moment), but WordPress recommends that you should not show error messages in live sites.
I currently have my test site running WordPress 6.9 and php 8.2 with no issues.
The only major issue with bbpress at the moment is that it does not work well with FSE themes.
However my bbp style pack plugin has fixes for this
bbp style pack
as well as block versions of the widgets and a ton of styling and functionality add-ons.
All plugins are subject to the authors commitment, and bbpress is no different.
suspect this is an AI generated spam, but in case not,
bbpress latest version is 2.6.14 and was updated 4 months ago.
bbPress
Hi all — today my Wordfence scan threw up a message saying the bbPress plugin “appears to be abandoned” (last updated Nov 29, 2021, tested to WP 6.3.2) and labelled it under a “Vulnerability Scan” result. I’m surprised because I’ve been running bbPress on a few sites and didn’t expect that kind of warning.
Has anyone else seen this exact Wordfence message recently? I’m trying to understand whether this is a false positive from the scanner or if there really is an issue with maintainer activity/compatibility. A few quick notes about my setup that might matter:
WP version: 6.3.2
bbPress version: (latest I have installed)
Hosting: shared (no custom hardening beyond basic security plugin)
I’m mainly looking for other users’ experiences — did Wordfence give you the same warning? Did you find official confirmation about bbPress maintenance status, or any advisories/CVEs? Also curious if anyone can point to a reliable source that tracks plugin maintenance/activity (GitHub, WP plugin repo changelog, etc.) so I can verify on my own.
I have Auto Approval disabled.
When a user creates a topic it is pending.
On forum archive it shows the topic as the latest post of the forum. The url leads to a 404 page for guest users.
I ran the same test on “Topics” and it is the same for both:
Type: Normal
Status: Open
Visibility: Public
ok, so that’s good, I wanted to check that first.
So now as a test for the August 28, 2017 reply
in dashboard>replies>edit reply try changing the publish date on the August 28, 2017 one to October 20, 2025
and see if it now appears?
ok, so lets test date theory.
so in one of the forums that has the issue
1. find a post with multiple replies that all show – a topic without the problem
then in dashboard>replies>edit replies
find one of the replies and look at all the settings for that
2. Then find a post with multiple replies where replies do not show, and again
in dashboard>replies>edit replies
find one of the replies and look at all the settings for that
and see if there are any differences.
then come back
I recently discovered that WordPress.com’s Personal and Premium plans allow plugin installation, so I immediately paid and installed bbPress.
However, a similar forum plugin, WPFORO, works fine, but after installing bbPress, when I go to the actual forum page (myid.wpcomstaging.com/forums/forum/test/), it just displays a blank screen, with neither my blog’s theme nor the forums displayed.
Just in case, I tried disabling my browser’s ad blocker and changing my theme, but the results were the same!
I asked a question on the WordPress.com forums and was directed here. Has anyone else encountered a similar issue? What solutions have you found?
When a user quotes another post using the quote button, their post shows the bbcode as plain text. I tried to recreate the issue on my end with a test account (non-admin) in incognito mode, and was not able to recreate the issue. Any idea what could be causing it? (example linked below)
Wordpress version: 6.8.2
bbPress version: 2.6.14
Link: example post with issue
Hi @johnjamesjacoby,
I realize you’re busy and I hate to keep pressing this, but the truth is that the functionality for this specific pagination has been broken for nearly five years (at least that I’ve been aware of).
In addition to the examples I’ve already shared (which I’m still waiting on a reply to), I wanted to provide one more. Since this site is publicly listed as an example on bbPress, I figured it would be fine to post it here.
On the Angry Birds bbPress/BuddyPress forum, the same pagination issue appears for Topics Started and Replies Created. You can see the broken links for the user “Bird Leader” here:
https://www.angrybirdsnest.com/members/birdleader/forums/replies/
If you try to view page 2 for either section, it results in a 404 error. Viewing the page source confirms they’re running the latest versions of both bbPress and BuddyPress.
A response on this matter would be greatly appreciated.
