[heydemoura]

Proposed changes

• Bug: on WordPress.com (Simple) sites the All Playlists block always shows its "No playlists yet" empty state, even when published posts contain Video Playlist blocks.
• Cause: the block lists the videopress_playlist_index option, which Playlist_Index keeps current from wp_after_insert_post / deleted_post, plus a one-off full scan scheduled on admin_init. Those hooks are only added by the package's Initializer::active_initialization(). WordPress.com does not run the package initializer, so nothing ever writes the index there and the block reads an empty option. The extended-block file already starts Channel::init() for the same reason, but not the index.
• Fix: register_videopress_blocks() now also starts Playlist_Index::init() once the Video Playlist block is registered, so the index is kept wherever the block exists. Where the package initializer already ran (self-hosted and Atomic sites with the VideoPress module active), hooking it again is a no-op: the callbacks are identical, so WordPress keeps one.
• Existing sites: they get the full scan on their next admin_init (the index version option is missing), and any post save re-indexes that post.

Related product discussion/links

• Follow-up to VideoPress: add an All Playlists block #52724 (All Playlists block) and VideoPress: add a site-wide playlist index option #52729 (playlist index).

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

No.

Testing instructions

• jetpack docker phpunit jetpack -- --filter=VideoPress_Video_Extension_Test: the playlist index follows saved posts when the playlist block is registered, and is not hooked when it is not.
• On a WordPress.com Simple site with this change (sandbox):
  1. Publish a post with a Video Playlist block that has a title and some videos.
  2. Open a page with an All Playlists block: the playlist is listed instead of "No playlists yet".
  3. For a site that already had playlists before the fix, visit wp-admin once (it schedules the full scan), let cron run, and reload the page: the existing playlists are listed.

🤖 Generated with Claude Code

[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 fix/videopress-all-playlists-empty-state branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fix/videopress-all-playlists-empty-state

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:

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

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/plugins/jetpack/extensions/extended-blocks/videopress-video/videopress-video.php	12/33 (36.36%)	-3.64%	3 ❤️‍🩹

Full summary · PHP report · JS report