Skip to content

WPCOM_Features: add PODCASTING feature and Premium-and-higher plan mapping#48700

Open
robertbpugh wants to merge 1 commit into
trunkfrom
pods-142-add-podcasting-feature
Open

WPCOM_Features: add PODCASTING feature and Premium-and-higher plan mapping#48700
robertbpugh wants to merge 1 commit into
trunkfrom
pods-142-add-podcasting-feature

Conversation

@robertbpugh
Copy link
Copy Markdown
Contributor

Proposed changes

  • Add WPCOM_Features::PODCASTING = 'podcasting' so Podcast_Gate (PODS-141) and any future surface gate resolve product access through one slug.
  • Map it to WPCOM_PREMIUM_AND_HIGHER_PLANS plus JETPACK_ALL_SITES, which covers Premium, Pro, Business (including Hundred-Year), Ecommerce, Ecommerce Trial, and WooExpress. The two extras from the issue body fold into this rollup: WPCOM_ECOMMERCE_PLANS already lives under Business-and-higher, and WPCOM_100_YEAR_PLANS is not a constant in this file since Hundred-Year nests inside WPCOM_BUSINESS_PLANS.

The file is mirrored verbatim into wpcom. A paired wpcom PR has to deploy alongside this one before any podcast surface gate ships.

Related product discussion/links

  • Linear: PODS-142
  • Sibling PR (gate helper): PODS-141

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

No.

Testing instructions

  • php -l projects/plugins/wpcomsh/wpcom-features/class-wpcom-features.php passes locally.
  • After deploy, WPCOM_Features::supports( WPCOM_Features::PODCASTING, $blog_id ) returns true on a Premium-or-higher blog and false on Free or Personal (without the podcasting-grandfathered sticker, which is wired in PODS-141).

…pping

Maps the new podcasting feature to WPCOM_PREMIUM_AND_HIGHER_PLANS plus
JETPACK_ALL_SITES so Current_Plan::supports( 'podcasting' ) and downstream
podcast surface gates can resolve product access from a single source.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 11, 2026

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 (WordPress.com Site Helper), and enable the pods-142-add-podcasting-feature branch.

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
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 11, 2026

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!


Wpcomsh plugin:

  • Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2)

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

@jp-launch-control
Copy link
Copy Markdown

jp-launch-control Bot commented May 11, 2026

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

@robertbpugh robertbpugh marked this pull request as ready for review May 11, 2026 19:04
Copilot AI review requested due to automatic review settings May 11, 2026 19:04
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new WPCOM_Features slug for podcasting and wires it into the wpcomsh feature-to-plan mapping so podcast-related gating can rely on a single feature identifier across surfaces.

Changes:

  • Introduce WPCOM_Features::PODCASTING = 'podcasting'.
  • Map PODCASTING access to WPCOM_PREMIUM_AND_HIGHER_PLANS plus JETPACK_ALL_SITES.
  • Add a wpcomsh changelog entry documenting the new feature mapping.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
projects/plugins/wpcomsh/wpcom-features/class-wpcom-features.php Adds the PODCASTING feature constant and maps it to Premium-and-higher plans and all Jetpack sites.
projects/plugins/wpcomsh/changelog/pods-142-podcasting-feature Adds a changelog entry for the new PODCASTING feature mapping.

Comment on lines +1094 to +1097
self::PODCASTING => array(
self::WPCOM_PREMIUM_AND_HIGHER_PLANS,
self::JETPACK_ALL_SITES,
),
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@copilot apply changes based on this feedback

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the PR/testing notes to use the correct APIs (wpcom_site_has_feature( WPCOM_Features::PODCASTING ) / WPCOM_Features::has_feature(...)) instead of WPCOM_Features::supports(...). No code changes were required for this feedback; current head is 578dd1f.

@robertbpugh
Copy link
Copy Markdown
Contributor Author

@copilot apply changes based on the comments in this thread

Copy link
Copy Markdown
Contributor

Copilot AI commented May 11, 2026

@copilot apply changes based on the comments in this thread

I checked the linked review thread and applied the actionable feedback: use wpcom_site_has_feature( WPCOM_Features::PODCASTING ) (or WPCOM_Features::has_feature(...)) instead of WPCOM_Features::supports(...) in the PR/testing guidance. The code changes remain in 578dd1f.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants