Automattic / Automattic/jetpack

Subscriptions: Adding First-time Subscription Level Disrupts Posting Experience

Open
#34,178 0 comments 0 reactions 0 assignees View on GitHub
[Feature] Subscriptions [Plugin] Jetpack [Pri] Normal [Status] Priority Review Triggered Earn Enhancement Triaged
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:

![Annotation on 2023-11-16 at 17-47-00](https://github.com/Automattic/jetpack/assets/45246438/ff6bee4a-2247-40ab-b41e-29490ca62ffd)

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

![Screenshot_at_November_16th_2023_-_5 07 28_pm](https://github.com/Automattic/jetpack/assets/45246438/30c89142-1ebb-4313-8985-7dcbc9b9f846)

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

![Annotation on 2023-11-16 at 17-51-16](https://github.com/Automattic/jetpack/assets/45246438/4a30905a-2dbc-4ae6-ad97-f171cd1e1175)

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

![Annotation on 2023-11-16 at 17-51-59](https://github.com/Automattic/jetpack/assets/45246438/00eb1ae7-1f63-46a1-921b-0c714b6ad1f2)

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

![Annotation on 2023-11-16 at 17-52-48](https://github.com/Automattic/jetpack/assets/45246438/713feda4-dbb0-4f92-a921-7e06bcb99e83)

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

![Annotation on 2023-11-16 at 17-54-18](https://github.com/Automattic/jetpack/assets/45246438/f9349782-924c-4074-8f12-56b7322b34c5)

### 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

Open the contributing 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.