No apology necessary!
I think it’s good to post this here, in case it’s related to the most recent bbPress release.
There was a change related to Roles triggering PHP errors with certain plugins active, so it’s plausible that fix broke something else.
Which plugin were you using to make your new roles?
Blog post for 2.6.11 is up!
bbPress 2.6.11 is out!
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.
You’re welcome, Eusebiu. Really sorry about today!
2.6.11 is out!
Blog post imminent.
Changelog code page updated.
Sorry everyone 😔
2.6.11 will be out later today to fix this.
Most embeds can be disabled via the “Auto-embed links” setting in:
Admin > Settings > Forums
You can also permanently unhook them:
remove_action( 'bbp_init', 'bbp_reply_content_autoembed', 8 );
remove_action( 'bbp_init', 'bbp_topic_content_autoembed', 8 );
Images are a bit trickier, as you’ll need to remove img from the allowed-tags array:
add_filter( 'bbp_kses_allowed_tags', function( $tags = array() ) {
unset( $tags['img'] );
return $tags;
} );
bbPress includes a function called bbp_make_clickable that is used to turn regular URLs in topic and reply contents into anchors.
You would need to unhook it to prevent it from happening.
remove_filter( 'bbp_get_reply_content', 'bbp_make_clickable', 40 );
remove_filter( 'bbp_get_topic_content', 'bbp_make_clickable', 40 );
Just these!
We also use custom themes:
Sounds weird. Link to your forums where it’s happening?
bbPress 2.6.9 was just released, but it does not make changes to this yet.
I needed to rush out an Akismet fix first, and I’ll look more into this next.
Thank you for being patient. Sorry for the wait. 🙏
Hello! Your second URL is correctly showing 0 topics, at least.
I’m not entirely certain anymore if incorrect BuddyPress Group sub-pages will 404.
@robin-w – any suggestions on improvements bbPress should make?
I was thinking of renaming no-js to bbp-no-js to try and avoid an issue with other plugins or themes already doing something with that class, but I’m not sure that solves this specific problem.
That last one is simply a deprecation notice. It will not break anything.
There is also…
do_action( 'bbp_add_user_subscription', $user_id, $object_id, $type );
…and…
do_action( 'bbp_remove_user_subscription', $user_id, $object_id, $type );
…if you need something a bit more lower-level, that isn’t tied directly to the request handler.
Can you please post the code snippet you are using to enable the visual editor?
In my testing, it is working OK using these snippets:
Enable Visual Editor
I see now, thanks!
Perhaps, this is something that bbPress could do a better job with. Each of the forum/topic type pages is its own thing, and they do not inherit the page settings from the forum root in the way it seems like you are expecting for them to – which is totally reasonable to expect.
This is a deprecated argument that only appears when WP_DEBUG is turned on.
The debug log itself is nothing to worry about. 👍
bbPress will address this once its minimum version is (legitimately) raised to 5.5.
Thank you for letting us know here 🙏
There was a bug in 2.6.7 regarding page layouts, so give 2.6.8 a try and see if it’s better?
Revisions are totally a WordPress thing. It’s weird, but sounds accurate.
Using Gravity Forms to create new topics & replies will bypass the “freshness” hooks that bbPress expects to run normally. This means that the “branch” of topics & forums in the “tree” of that submission won’t get walked up to the root, to tell that whole branch what its most recent content is.
Once you post something yourself normally, the tree gets walked and everything looks OK.
The function that would normally be called is bbp_update_topic(). It includes all of the extra meta data that needs to be added – including a call to bbp_update_topic_walker() that “walks” the branch in the tree.
Lastly, it refreshes the last_changed cache key in the bbpress_posts cache group. You could try busting that cache on your Gravity Forms submission (to see if that’s enough) but I have a feeling it won’t be, and you’ll need to find the best way to trigger the update.
2.6.8 released. 🙏 very sorry for the problem. 🤞 let us know that everything is fixed?
The body class code changed, which might be causing this.
It is not intended, so 2.6.8 should fix it.
