VideoPress: enable modernized dashboard by default

[dhasilva]

Fixes #48506

Proposed changes

• Flip the VideoPress dashboard modernization filter (rsm_jetpack_ui_modernization_videopress) to default true, so the modernized wp-build dashboard is now served by default.
• Leave the legacy dashboard code in place so it can still be reached during the test period by overriding the filter (e.g. add_filter( 'rsm_jetpack_ui_modernization_videopress', '__return_false' )) in case a regression needs a quick fallback.

Related product discussion/links

Does this pull request change what data or activity we track or use?

No.

Testing instructions

• On a site with the VideoPress plugin (or Jetpack VideoPress) active, go to VideoPress in wp-admin (wp-admin/admin.php?page=jetpack-videopress).
• Confirm the modernized dashboard loads by default, with no filter overrides in place.
• Add add_filter( 'rsm_jetpack_ui_modernization_videopress', '__return_false' ); (e.g. in a mu-plugin or snippet) and reload the page; confirm the legacy dashboard is served, verifying the fallback path still works.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the update/videopress-modernization-release branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/videopress-modernization-release

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

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:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: June 2, 2026
  • Code freeze: June 1, 2026

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

---

Videopress plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[jp-launch-control]

Code Coverage Summary

This 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. 🤷

Full summary · PHP report · JS report

[keoshi]

Confirmed the new UI loads and add_filter( 'rsm_jetpack_ui_modernization_videopress', '__return_false' ); shows the legacy one.

Two things worth noting, the first which I'd consider blocking:

• The VideoPress page is fully available pre-connection, making all uploads fail.
• I'm seeing the same header height change noted here.

[dhasilva]

The VideoPress page is fully available pre-connection, making all uploads fail.

Great catch!

[dhasilva]

The VideoPress page is fully available pre-connection, making all uploads fail.

Fixed in #49063