Skip to content

Conversation

@arcangelini
Copy link
Member

@arcangelini arcangelini commented Nov 20, 2025

Closes https://linear.app/a8c/issue/CML-1027/fix-premium-contentcontainer-email-render

Proposed changes:

  • Add email_render_callback for jetpack/recurring-payments jetpack/payment-buttons and premium-content/container
Old Renderer Before After
Screen Shot 2025-11-24 at 12 07 47 Screen Shot 2025-11-24 at 13 27 20 Screen Shot 2025-11-24 at 11 57 35

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

NA

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

No

Testing instructions:

This change needs to be pulled into WPCOM to test since emails and previews are generated from WPCOM. To test on different sites make sure your site is using your sandbox for the public-api.wordpress.com.

  1. Setup Newsletter plans for the site
  2. Add wc-email-editor sticker to your blog
  3. Add Recurring Payment buttons and Premium Content blocks to the post and Publish
  4. View the email using the Email Preview from the post editor
  5. Send a test email to verify the same results.

@arcangelini arcangelini requested a review from a team November 20, 2025 00:08
@arcangelini arcangelini self-assigned this Nov 20, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 20, 2025

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 add/premium-content-block-email-render branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack add/premium-content-block-email-render

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 github-actions bot added [Block] Paid Content aka Premium Content [Block] Payment Buttons [Feature] Memberships [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] In Progress labels Nov 20, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 20, 2025

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 a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  • ✅ 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: December 2, 2025

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

@github-actions github-actions bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label Nov 20, 2025
@jp-launch-control
Copy link

jp-launch-control bot commented Nov 20, 2025

Code Coverage Summary

Coverage changed in 3 files.

File Coverage Δ% Δ Uncovered
projects/plugins/jetpack/extensions/blocks/payment-buttons/payment-buttons.php 6/40 (15.00%) 15.00% 3 ❤️‍🩹
projects/plugins/jetpack/modules/memberships/class-jetpack-memberships.php 89/438 (20.32%) 1.82% 1 ❤️‍🩹
projects/plugins/jetpack/extensions/blocks/premium-content/login-button/login-button.php 1/34 (2.94%) 2.94% 0 💚

Full summary · PHP report · JS report

@arcangelini arcangelini marked this pull request as ready for review November 24, 2025 12:31
Copy link
Member

@jeherve jeherve left a comment

Choose a reason for hiding this comment

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

I'm most likely missing something in my set up, because I do not see the payment buttons in the emails at all, whether I test on a Jetpack site or a wpcom simple site.

I also noticed some oddities with colors and text alignment:

Editor

Image

(centered italic text, buttons with custom colors from the theme palette, text with custom color, other text with color from the theme palette)

Email preview

Image

Email

Image

}

// Reuse the button block's email rendering method.
return \Automattic\Jetpack\Extensions\Button\render_email( $block_content, $button_block, $rendering_context );
Copy link
Member

Choose a reason for hiding this comment

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

I think I would check if the class exists just to be sure, since Jetpack allows disabling the registration of some blocks via filters. Some users may have disabled the button block for some reason (although I would assume it would cause them trouble with the paid content buttons already).

Copy link
Member

Choose a reason for hiding this comment

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

I'm thinking we may want to place those in a new subdirectory, to avoid mixing them with regular block tests. It would be easier to locate them in the future, if we need mocks again.

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

Labels

[Block] Paid Content aka Premium Content [Block] Payment Buttons Enhancement [Feature] Memberships [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] In Progress [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. [Tests] Includes Tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants