Skip to:
Content

BuddyPress.org

Opened 3 weeks ago

Closed 3 weeks ago

Last modified 2 weeks ago

#9140 closed defect (bug) (reported-upstream)

"Discourage search engines from indexing this site" prevents bbPress activity to be recorded.

Reported by: lorangeo's profile Lorangeo Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Core Keywords:
Cc:

Description

When the option "Discourage search engines from indexing this site" is checked in the WP Reading settings, the bbPress activity is not being recorded anymore, and doesn't show on the activity feed. I think this is not logical and these settings are two different and unrelated things.

Change History (2)

#1 @r-a-y
3 weeks ago

  • Milestone Awaiting Review deleted
  • Resolution set to reported-upstream
  • Status changed from new to closed

This is a bbPress issue. See https://bbpress.trac.wordpress.org/ticket/2151 . You can override the default bbPress behavior by using the following code snippet in your theme's functions.php or another place like in /wp-content/mu-plugins/ or /wp-content/plugins/bp-custom.php

add_filter( 'bbp_is_site_public', '__return_true' );

#2 @petrkorolevth9
2 weeks ago

A recent issue has surfaced where enabling the "Discourage search engines from indexing this site" setting in WordPress's Reading settings unexpectedly stops the recording of bbPress forum activity in the activity feed. This seems illogical as the two functionalities—search engine visibility and activity logging—appear to be unrelated. Why might enabling this privacy setting impact the functionality of bbPress activity recording, and how can this be addressed without compromising site privacy?

In WordPress, the option to discourage search engines is intended to prevent the site from being indexed but not to interfere with internal functionalities such as activity tracking. However, users have noticed that upon enabling this setting, no new entries are logged in the bbPress activity feed, which is critical for community engagement and monitoring.

The issue has been redirected to the bbPress developers, suggesting it may be an internal handling within the bbPress plugin that inadvertently ties activity logging to site visibility settings. A temporary workaround involves using the add_filter( 'bbp_is_site_public', '__return_true' ); snippet in the site's customization files to force bbPress to recognize the site as public regardless of the WordPress search engine visibility setting.

How can developers ensure that changes to visibility settings do not unintentionally impact other site functionalities?

Last edited 2 weeks ago by petrkorolevth9 (previous) (diff)
Note: See TracTickets for help on using tickets.