Memory Wiki

I'll follow the investigation plan step by step. ## Step 1: Disable the output-buffer mu-plugin and fetch both pages

Now let me read the HTML of both pages, starting with extracting sidebar/container structure:

Now let me read the studios page HTML structure:

## Step 3: Read the theme templates

Let me look at how the template hierarchy decides between `buddypress.php` and `page.php`, and how the right sidebar gets rendered:

Now let me check the theme mods and registered sidebars:

Let me look at how BP sets up the template and what checks determine if it uses `buddypress.php`:

Let me check how BP's template loader is working and what the activity slug is:

Let me check how the front page is handled vs other pages, and look at the `bp_core_load_template` and `template_redirect` logic:

I have completed the investigation. Let me summarize everything I've found. --- # INVESTIGATION REPORT: Layout Differences Between Homepage and /studios/ ## 1. Homepage (`/`) — Raw HTML Structure | Aspect | Finding | |--------|---------| | **Post ID / Type** | `post-32`, `post_type=page`, slug `home` | | **Template used** | `buddypress.php` (has `<div class="content-wrapper rg-bp-container">`) | | **Sidebars** | Two `<aside>` elements **inside** the content wrapper | | **Left sidebar** | `<aside id="left" class="widget-area sm-wb-grid-1-4 md-wb-grid-1-5">` — BP activity navigation widgets (`widget-activity-nav`, `widget-activity-subnav`) | | **Right sidebar** | `<aside id="secondary" class="widget-area activity-index-widget-area sm-wb-grid-1-3">` — widget `block-9` (empty) | | **Layout source** | BP component detection → `sidebar-buddypress.php` | | **Theme mod** | `reign_activity_directory_sidebar_layout` = `right_sidebar` | ## 2. Studios (`/studios/`) — Raw HTML Structure | Aspect | Finding | |--------|---------| | **Post ID / Type** | `post-0`, `post_type=buddypress`, slug `studios` | | **Template used** | `page.php` (has `<div class="content-wrapper">` WITHOUT `rg-bp-container`) | | **Sidebars** | One `<aside>` element **outside** the content wrapper | | **Right sidebar** | `<aside id="reign-sidebar-right" class="widget-area default">` — widgets `block-7`, `block-8`, plus injected activity-nav & activity-subnav | | **Content** | Login form ("This community area is accessible to logged-in members only") | | **Layout source** | `page.php` → `do_action('reign_after_content_section')` → `render_right_sidebar_area()` → `sidebar.php` | | **Theme mod** | `reign_groups_directory_sidebar_layout` = **empty** (no value set) | ## 3. Side-by-Side Comparison | Aspect | Homepage (`/`) | Studios (`/studios/`) | |--------|---------------|----------------------| | **Template file** | `/var/www/html/wp-content/themes/reign-theme/buddypress.php` | `/var/www/html/wp-content/themes/reign-theme/page.php` | | **Content wrapper class** | `content-wrapper rg-bp-container` | `content-wrapper` | | **Left sidebar ID** | `left` (from `sidebar-buddypress.php`, line 103-120) | **None** | | **Right sidebar ID** | `secondary` (from `sidebar-buddypress.php`, line 130-143) | `reign-sidebar-right` (from `sidebar.php`, line 46-55) | | **Widgets in right sidebar** | `activity-index` → `block-9` | `sidebar-right` → `block-7`, `block-8` + injected nav widgets | | **Layout setting source** | `sidebar-buddypress.php` lines 20-32 using `reign_activity_directory_sidebar_layout` | `sidebar.php` lines 1-25 using `reign_page_single_right_sidebar` = `sidebar-right` | | **BP component detected** | `bp_current_component()` → **activity** | `bp_current_component()` → **empty** | | **Post query result** | Post ID 32, type `page` (publicly queryable) | Post ID 0, type `buddypress` (NOT publicly queryable) | | **Page meta** | `site_layout` = `right_sidebar` | `site_layout` = `right_sidebar` | ## 4. Root Cause Analysis ### THE ROOT CAUSE IS A POST_TYPE MISMATCH The BP groups directory page (ID 31, slug `studios`) has **`post_type = 'buddypress'`** — a custom post type that is **not publicly queryable**. The BP activity directory page (ID 32, slug `home`) which serves as the front page has **`post_type = 'page'`** — a standard publicly queryable post type. This difference cascades through the entire template pipeline: ### Line-by-line tracing **For `/studios/` (page 31, post_type `buddypress`):** 1. WordPress rewrite rules at `/studios/?` → `index.php?bp_groups=1` (rewrite rules registered by BP with slug "studios") 2. The `buddypress` post type is not publicly queryable → `WP_Query` cannot find it → **`get_queried_object_id()` returns 0** 3. BuddyPress creates a dummy `$post` object (post-0) with injected login form content 4. **Template selection**: No `single-buddypress.php` exists in theme → no fallback → `page.php` is used 5. In `page.php` (line 10): `<div class="content-wrapper">` — NO `rg-bp-container` class 6. `page.php` calls `do_action('reign_after_content_section')` → `render_right_sidebar_area()` in `class-reign-theme-structure.php` line 684 7. `render_right_sidebar_area()` at line 704-712: `$post` is the dummy (ID 0), so `$wbcom_metabox_data` is empty → `$site_layout` is empty → falls through to line 730: `$active_content_layout` = theme mod `reign_page_single_layout` with fallback `right_sidebar` 8. At line 734: condition `($active_content_layout == 'both_sidebar') || ($active_content_layout == 'right_sidebar')` is TRUE → calls `get_sidebar()` → loads `sidebar.php` 9. `sidebar.php` line 2: `reign_get_sidebar_id_to_show('primary_sidebar')` returns empty → line 5-13: `$post` is dummy, `get_post_type()` is empty → theme mod fallbacks return empty → line 34: defaults to `sidebar-right` 10. `sidebar.php` line 42-55: renders `<aside id="reign-sidebar-right">` with widgets from `sidebar-right` (block-7, block-8) 11. **`sidebar-buddypress.php` is never loaded** because `buddypress.php` is not the template **For `/` (page 32, post_type `page`):** 1. WordPress finds page 32 with normal query → `get_queried_object_id()` = 32 2. BuddyPress intercepts via `bp_core_load_template()` because the front page is also the BP activity directory (bp-pages option shows `activity => 32`) 3. BP loads `buddypress.php` template 4. `buddypress.php` line 30-31: `<div class="content-wrapper rg-bp-container">` 5. `buddypress.php` line 50: `get_sidebar('buddypress')` → loads `sidebar-buddypress.php` 6. `sidebar-buddypress.php` line 9: `bp_is_current_component('activity')` is TRUE → sets `$post` to activity page (ID 32) 7. `sidebar-buddypress.php` line 20-22: `$bp_activity_sidebar = 'right_sidebar'` → falls into condition at line 27-29 → `$sidebar_id = 'activity-index'` 8. `sidebar-buddypress.php` line 130-143: renders `<aside id="secondary" class="widget-area activity-index-widget-area">` with `dynamic_sidebar('activity-index')` → widget `block-9` 9. Additionally, the left sidebar nav widgets are rendered within the article content by BP itself (not from a sidebar file) ### The specific condition that diverges The critical fork is at `buddypress.php` line 50: ```php echo get_sidebar( 'buddypress' ); ``` This line ONLY runs if BP intercepts the template and loads `buddypress.php`. BP intercepts the template ONLY if `bp_is_current_component()` returns a truthy value. On `/studios/`, `bp_is_current_component()` returns **empty** because: - The `buddypress` post type is not publicly queryable, so the main query fails - Without a proper query, BP's component initialization doesn't complete - The login block (injected by BP's private community feature or a plugin) prevents BP from setting up component context ### What would need to change To make `/studios/` render with the same layout as the homepage, **one of these** would need to change: **Option A:** Change post_type of page 31 from `buddypress` to `page` (like page 32). This ensures WordPress can query it, BP can detect the component, and the `buddypress.php` template loads correctly. **Option B:** Set a default value for `reign_groups_directory_sidebar_layout` theme mod so that `sidebar-buddypress.php` can render correctly even if loaded. Currently it's empty, while `reign_activity_directory_sidebar_layout` = `right_sidebar`. **Option C:** Ensure users are logged in before accessing `/studios/` so that BP properly initializes the groups component detection. **Option D:** Add a `single-buddypress.php` template file that loads `buddypress.php` for the `buddypress` post type. The **most likely intended fix** is **Option A** — the `buddypress` post type for BP directory pages was probably meant to be `page` post type, matching how the activity directory page (ID 32) is configured.