Automattic / Automattic/jetpack
Subscriptions: Adding First-time Subscription Level Disrupts Posting Experience
- Dominant language
- PHP
- Stars
- 1.8k
- Forks
- 898
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 774
Description
### Impacted plugin
Jetpack
### Quick summary
When a user marks a post as for paid subscribers only for the first time, the user is moved over to WordPress.com to configure the paid plan. However, the user is never returned back to the post screen.
### Steps to reproduce
1. Add a new post
2. Mark as being for "Paid subscribers only"
3. If there are no paid subscription levels, observe that you are moved over to WordPress.com to complete the process
4. Observe that upon registration, you are never returned to the post editor
### A clear and concise description of what you expected to happen.
I would expect that the ability to configure a newsletter subscription level wouldn't disrupt my editing. This could be accomplished by returning me to my post editor after adding the required subscription level.
### What actually happened
Start in the post editor:

After clicking on "Paid subscribers only," a modal pops up inviting me to get started:

This moves me out of the post editor and over to WordPress.com:

Once I add the subscription tier, I remain on WordPress.com:

The post is in my WP Admin dashboard as a draft:

However, when I opened the post, it didn't save my intention to make the post for paid subscribers only:

### Impact
Some (< 50%)
### Available workarounds?
No but the platform is still usable
### Platform (Simple and/or Atomic)
Self-hosted
### Logs or notes
_No response_
Contributor guide
Research direction
Reproduce the flow from the post editor through WordPress.com subscription setup, then inspect how the draft is reopened in WP Admin. Done means the user returns to the post editor after creating the first paid subscription level and the “Paid subscribers only” choice remains selected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- content, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100