Post Access Settings - Unable to select Paid Subscribers Only #40351
Labels
Customer Report
Issues or PRs that were reported via Happiness. aka "Happiness Request", or "User Report"
Earn
Earn features
[Feature] Paid Content
aka Premium Content. Controlling specific content for paying site visitors.
[Feature] Subscriptions
All subscription-related things such as paid and unpaid, user management, and newsletter settings.
[Platform] Atomic
[Platform] Simple
[Plugin] Jetpack
Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/
[Pri] Low
[Status] Auto-allocated
Triaged
[Type] Bug
When a feature is broken and / or not performing as intended
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:
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.
Steps to reproduce
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)
The text was updated successfully, but these errors were encountered: