Social: roll out the modernized dashboard to 100%#50092
Conversation
Flip the `rsm_jetpack_ui_modernization_social` gate default from false to true so the modernized wp-build Social dashboard loads by default on Atomic and self-hosted Jetpack sites. Simple is driven separately from the WordPress.com backend, so this PR stays open until that cohort reaches 100%. Hosts (and a11ns who want the legacy view back) can still opt out with add_filter( 'rsm_jetpack_ui_modernization_social', '__return_false' ). Unlike Newsletter, the Social gate carried no Jetpack-side cohort scaffolding to remove — its staged rollout lives entirely on the wpcom side — so this is a single default flip plus the matching test. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 Follow this PR Review Process:
If you have questions about anything, reach out in #jetpack-developers for guidance! |
Code Coverage SummaryThis PR did not change code coverage! That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷 |
Fixes #
Brings the modernized Jetpack Social wp-admin dashboard to 100% on the Jetpack side, mirroring the Newsletter rollout (#50091).
Do not merge until the Simple-site cohort reaches 100% on the WordPress.com backend. Like Newsletter, the Simple rollout is staged from a wpcom server-side flag; this PR flips the Jetpack-side default, which takes effect on Atomic (WoA) and self-hosted Jetpack sites immediately on merge. Holding it open until Simple is at 100% keeps the two paths consistent.
Proposed changes
rsm_jetpack_ui_modernization_socialgate (Social_Admin_Page::is_modernized()) default fromfalsetotrue, so the wp-build Social dashboard (Overview + Settings tabs) loads by default instead of the legacy single-page React app.function_exists( 'jetpack_social_..._render_page' )guard inis_wp_build_dashboard_active()is unchanged, so a site still falls back to the legacy bundle if the wp-build chassis isn't available.add_filter( 'rsm_jetpack_ui_modernization_social', '__return_false' )— exercised by the existing kill-switch test.Related product discussion/links
Does this pull request change what data or activity we track or use?
No.
Testing instructions
admin.php?page=jetpack-social) and confirm the modernized wp-build dashboard (Overview + Settings tabs) loads by default, instead of the legacy single-page screen.add_filter( 'rsm_jetpack_ui_modernization_social', '__return_false' );restores the legacy Social admin screen.composer phpunitinprojects/packages/publicize(113 tests pass;--filter Social_Admin_Page_Testcovers the new default-on behavior, the explicit-on case, and the kill switch).🤖 Generated with Claude Code