Automattic / Automattic/jetpack

Post Access Settings - Unable to select Paid Subscribers Only

Open
#40,351 4 comments 0 reactions 0 assignees View on GitHub
[Feature] Paid Content [Feature] Subscriptions [Platform] Atomic [Platform] Simple [Plugin] Jetpack [Pri] Low [Status] Auto-allocated Bug Customer Report [LEGACY] Earn Triaged
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

### Impacted plugin

Jetpack

### Quick summary

Unable to select "Paid Subscribers Only" after creating a Paid Content Block and / or Paid Newsletter. Required to create a new one though the pop-up pictured below.

When editing a post, go to the Access to limit the post visibility to "Paid Subscribers Only".
A pop-up appears asking to Set Up Payments when a Stripe connection has already been setup.

Pop-up says:

> Set up payments
>
> To start collecting payments, you’ll just need to:
>
> Create a payment offer and choose a price for access to paid content
> Set up or connect your Stripe account
>
> Not Now Get Started

Clicked on "Get Started", created a new Newsletter Tier in the Tools > Monetize.
Went back to the post and was able to select "Paid Subscribers Only".

I had to create a new Newsletter Tier, I couldn't select the one I made earlier.

I also could not select a subscription from the Paid Content Blocks.

![Image](https://github.com/user-attachments/assets/8867a841-ffde-4c45-8ca9-f2acd1cd53db)

### Steps to reproduce

1. Connect Stripe to an account if you haven't done so yet
2. Create a Paid Content Block and/or create a Paid Newsletter by following the support guide: https://wordpress.com/support/paid-newsletters/
3. Create a new post, save as draft or publish (this won't work if the post is Private)
4. In the Post settings go to Access and select "Paid Subscribers Only"
5. Pop-up appears with the message that Stripe needs to be connected and that you need to create a payment offer
6. Note that you are not able to select the Paid Newsletter or Paid Content Block subscription created earlier.
7. Click on Get Started to create a brand new Paid Newsletter Subscriptions
8. This sends you to the Tools > Monetize page
9. After setting this up return to the post
10. Go to Post Settings > Access > and select "Paid Subscribers Only."
11. Paid Subscribers is selected successfully. Click Save/Publish to save the changes.
12. Create a new post and Go to Post Settings > Access > and select "Paid Subscribers Only."
13. Note that you can select the "Paid Subscribers Only" option after creating the newsletter though that flow that starts in the post editor.

### A clear and concise description of what you expected to happen.

After creating subscriptions for my site, either Paid Content or a Newsletter in Tools, I expect to be able to set the posts to be accessed by paid subscribers.

### What actually happened

It is not possible to limit a post to paid subscribers without creating a new newsletter tier.

### Impact

One

### Available workarounds?

Yes, easy to implement

### If the above answer is "Yes...", outline the workaround.

This is not really a workaround - but you do have to use the "Get Started" button from the Pop-up to create a valid Newsletter subscription.

### Platform (Simple and/or Atomic)

Atomic, Simple

### Logs or notes

(9094740-zd)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Post Settings > Access flow after creating a Paid Content Block or Paid Newsletter in Tools > Monetize, then compare it with the Get Started flow that succeeds. Trace the post editor and payment-offer setup entry points mentioned in the report; done means existing subscriptions can be selected without creating a new Newsletter tier.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php, react
Domain
frontend, payments
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.