Automattic / Automattic/jetpack

Monetize: Merge Subscriber login button and paid-content Login button

Open
#36,525 1 comment 0 reactions 0 assignees View on GitHub
[Plugin] Jetpack Enhancement
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 14h
Merged PRs (30d)
790

Description

### Impacted plugin

Jetpack

### What

Both button have the same functionalities and have duplicated features

### How

Discussion here: https://github.com/Automattic/jetpack/pull/35441#issuecomment-1952390591

- This will allow to proxy the token on Jetpack/self-hosted (see https://github.com/Automattic/gold/issues/359 )
- We should be able to proxy the subscriber login button in the paid-content login button directly (in order to be backward compatible with existing `premium-content/login-button` blocks

Contributor guide

Open the contributing guide

Research direction

Start with the discussion in Automattic/jetpack#35441 and the linked gold issue #359, then compare the Subscriber login button with the paid-content Login button. Done means their duplicated functionality is merged while existing premium-content/login-button blocks remain backward compatible and token proxying works as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
authentication
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.