[buddypress-trac] [BuddyPress Trac] #9309: Support for WordPress 6.9

Sat Dec 27 04:19:00 UTC 2025

#9309: Support for WordPress 6.9
-------------------------+---------------------
 Reporter:  espellcaste  |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  14.5.0
Component:  Core         |     Version:
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |
-------------------------+---------------------

Comment (by vapvarun):

 @espellcaste Thanks for pushing back on this - you're right that proof
 matters!

 I spent some time digging into the reproduction steps and here's what I
 found:

 **Why you couldn't reproduce with TwentyFourteen:**
 TwentyFourteen doesn't have BP templates, so BP falls back to theme compat
 mode.

 **How to actually reproduce:**
 The issue only shows up with direct template loading. I set this up
 locally:

 1. Added `members/index.php` to the theme (triggers direct loading)
 2. Used `add_filter('bp_use_theme_compat_with_current_theme',
 '__return_false')`
 3. Used your test block plugin that enqueues CSS during render

 **Results on master (direct loading):**
 {{{
 $ curl ... | grep -n "bp-fouc-test-style\|</head>"
 302:</head>
 431:<link rel='stylesheet' id='bp-fouc-test-style-css'...
 }}}
 Style ends up on line 431, after `</head>` at 302 - that's inside
 `<body>`, causing FOUC.

 **With the fix:**
 {{{
 314:<link rel='stylesheet' id='bp-fouc-test-style-css'...
 315:</head>
 }}}
 Style hoisted to line 314, properly inside `<head>`.

 This matches what dd32 tracked down on profiles.wordpress.org:
 https://github.com/WordPress/wporg-mu-
 plugins/issues/715#issuecomment-3594242641

 (I'm using AI to help clean up my writing, but the testing and debugging
 was done locally first!)

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/9309#comment:14>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac