Untitled Session
2026-05-31 15:04 UTC · 20 messages · cli
You2026-05-31 15:04 UTC
Investigate why /community renders on the frontend but doesn't appear in the WordPress admin Pages list at testing.jaimisaunders.com.
Donna2026-05-31 15:04 UTC
Tool2026-05-31 15:04 UTC
{"output": "OCI runtime exec failed: exec failed: unable to start container process: exec: \"mysql\": executable file not found in $PATH", "exit_code": 127, "error": null}
Donna2026-05-31 15:04 UTC
Tool2026-05-31 15:04 UTC
{"output": "/usr/bin/mariadb", "exit_code": 0, "error": null}
Donna2026-05-31 15:04 UTC
Tool2026-05-31 15:04 UTC
{"output": "", "exit_code": 0, "error": null}
Donna2026-05-31 15:04 UTC
Tool2026-05-31 15:04 UTC
{"output": "ID\tpost_title\tpost_name\tpost_type\tpost_status\tpost_parent\tmenu_order\n23\tCommunity\tcommunity\tbuddypress\tpublish\t0\t0\n59\tCommunity\tcommunity\tnav_menu_item\tpublish\t0\t0", "exit_code": 0, "error": null}
Donna2026-05-31 15:04 UTC
Found it. The page exists as a BuddyPress component, not a regular page. Let me dig deeper.
Tool2026-05-31 15:04 UTC
{"output": "*************************** 1. row ***************************\n ID: 23\n post_author: 1\n post_date: 2026-05-31 00:50:28\n post_date_gmt: 2026-05-31 00:50:28\n post_content: \n post_title: Community\n post_excerpt: \...
Tool2026-05-31 15:04 UTC
{"output": "option_name\toption_value\nbp-pages\ta:3:{s:8:\"activity\";i:23;s:7:\"members\";i:24;s:6:\"groups\";i:46;}", "exit_code": 0, "error": null}
Donna2026-05-31 15:04 UTC
Now let me also check what the other BuddyPress pages look like, and verify the menu item:
Tool2026-05-31 15:04 UTC
{"output": "ID\tpost_title\tpost_name\tpost_type\tpost_status\n24\tMembers\tmembers\tbuddypress\tpublish\n46\tStudios\tstudios\tbuddypress\tpublish", "exit_code": 0, "error": null}
Tool2026-05-31 15:04 UTC
{"output": "ID\tpost_title\tpost_name\tpost_type\tpost_status\tpost_parent\n59\tCommunity\tcommunity\tnav_menu_item\tpublish\t0", "exit_code": 0, "error": null}
Tool2026-05-31 15:04 UTC
{"output": "option_name\toption_value\n_bp_community_visibility\ta:1:{s:6:\"global\";s:6:\"anyone\";}\n_bp_db_version\t13906\n_bp_enable_akismet\t1\n_bp_enable_heartbeat_refresh\t1\n_bp_ignore_deprecated_code\t1\n_bp_initial_major_version\t14.0\n_bp_theme_package_id\tnouveau\n_transient_bp_active_me...
Donna2026-05-31 15:04 UTC
Let me also check how the slug is registered in the rewrite rules:
Tool2026-05-31 15:04 UTC
{"output": "option_value\na:132:{s:11:\"^wp-json/?$\";s:22:\"index.php?rest_route=/\";s:14:\"^wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:21:\"^index.php/wp-json/?$\";s:22:\"index.php?rest_route=/\";s:24:\"^index.php/wp-json/(.*)?\";s:33:\"index.php?rest_route=/$matches[1]\";s:17:\"...
Tool2026-05-31 15:04 UTC
{"output": "", "exit_code": 0, "error": null}
Donna2026-05-31 15:04 UTC
Here's a complete summary of the investigation:
---
## Investigation Summary: `/community` page mystery
### What I Did
Queried the WordPress database (MariaDB container `testing-db-1`) for any posts matching "community", and checked BuddyPress options and rewrite rules.
### What I Found
**The /community page is a BuddyPress component page, not a standard WordPress page.**
1. **post_type is `buddypress`, not `page`** — This is the root cause. ID 23 has:
- `post_title` = "Community"
- `post_name` = "community"
- `post_type` = `buddypress`
- `post_status` = `publish`
WordPress admin's Pages list only filters by `post_type = 'page'`, so posts of type `buddypress` are invisible there.
2. **The `bp-pages` option confirms it** — In `wp_options`, `bp-pages` contains:
```
a:3:{
s:8:"activity"; i:23;
s:7:"members"; i:24;
s:6:"groups"; i:46;
}
```
So the "Community" page (ID 23) is mapped as the **BuddyPress Activity component root page**. Similarly, ID 24 is "Members" and ID 46 is "Studios" (Groups).
3. **Rewrite rules route `/community/` to BuddyPress** — The active rewrite rules show:
- `community/?$` → `index.php?bp_activities=1`
- `community/([^/]+)/?$` → `index.php?bp_activities=1&bp_activity_action=$matches[1]`
So WordPress intercepts the `/community/` URL and hands it off to BuddyPress's activity component, not the standard page template.
4. **Navigation menu** — There's also a `nav_menu_item` (ID 59) named "Community" linking to this page, which is why it appears in the site's main navigation.
5. **No custom postmeta** — ID 23 has no entries in `wp_postmeta`, confirming it's purely a BuddyPress-managed page.
6. **Two other invisible BP pages exist** — "Members" (ID 24) and "Studios" (ID 46) are also of type `buddypress` and won't appear in the Pages list either.
### Conclusion
The page isn't "missing" or broken — it's working exactly as BuddyPress designed. BuddyPress creates its own custom post type (`buddypress`) for component root pages. If Donna needs to manage it from the WordPress admin, she would need to either:
- Use a plugin that exposes BuddyPress pages in the admin (like "BuddyPress Pages in Admin")
- Or navigate to **BuddyPress → Settings → Pages** in the WP admin, where BuddyPress shows its own management UI for these component pages.