Skip to:
Content

BuddyPress.org

Changes between Initial Version and Version 1 of Ticket #9330, comment 2


Ignore:
Timestamp:
05/31/2026 05:06:35 PM (7 weeks ago)
Author:
indigetal

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #9330, comment 2

    initial v1  
    11Set component to Core. The fix is in `bp-core-template.php` and applies to any directory used as the static front page.
    22
    3 Many BuddyPress communities set a directory (Activity, Members, Groups, etc.) as the WordPress homepage. That is a supported, common setup. However, once the homepage URL carries *any* query string, such as a filter, pagination, campaign tracking, or a shared link like `/?ref=newsletter` — `bp_is_site_home()` can return false and BuddyPress never treats the request as the directory front page. Members see a broken or empty homepage instead of the community feed they expect.
     3Many BuddyPress communities set a directory (Activity, Members, Groups, etc.) as the WordPress homepage. That is a supported, common setup. However, once the homepage URL carries *any* query string, such as a filter, pagination, campaign tracking, or a shared link like `/?ref=newsletter`, `bp_is_site_home()` can return false and BuddyPress never treats the request as the directory front page. Members see a broken or empty homepage instead of the community feed they expect.
    44
    55The ticket describes the technical cause, but the actual community impact is much broader: query args are a normal part of the web, not an edge case. Extensions that add directory filtering, search refinements, or deep links should not each ship a `bp_get_requested_url` workaround to strip their own parameters. That does not scale when several plugins are active, and it is easy to miss a parameter and still break routing.