Podcast Episode: render the player in all contexts

[arcangelini]

What this does

The Podcast Episode block used to only show its full player on the front end of a site. Everywhere else — RSS feed, Reader on Atomic/Jetpack sites — you just got a plain "listen" link.

This makes the block render the full player in every context. Because the player now lives in the RSS feed, the WPCOM Reader picks it up on Atomic/Jetpack sites too, with no wpcom-side change.

Also:

• The episode title is now a link back to the post.
• The <audio>/<video> tags carry a plain link inside them, so clients that strip the player still show something clickable.
• Email is untouched — it's handled separately by render_email().

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

No.

Testing instructions

1. On a site with the Podcast module on, publish a post with a Podcast Episode block that has a media URL.
2. Open the post's RSS feed (/feed/) — the item should contain the full player markup (jetpack-podcast-episode__player, <audio>/<video>), not just a bare link.
3. On an Atomic/Jetpack site, open the post in the Reader (wordpress.com/read) — the player should render.
4. View the post on the front end — the player should look the same as before.

[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 or WordPress.com Site Helper), and enable the fix/podcast-episode-render-all-contexts branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fix/podcast-episode-render-all-contexts

bin/jetpack-downloader test jetpack-mu-wpcom-plugin fix/podcast-episode-render-all-contexts

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!

[jp-launch-control]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/packages/podcast/src/blocks/podcast-episode/class-podcast-episode-block.php	343/434 (79.03%)	-0.10%	0 💚

Full summary · PHP report · JS report