Automattic / Automattic/jetpack

Some Jetpack settings/endpoints not available in Calypso when using standalone plugins

Open
#26,918 3 comments 0 reactions 0 assignees View on GitHub
[Feature] WPCOM API [Plugin] Jetpack Enhancement Epic
Dominant language
PHP
Stars
1.8k
Forks
898
Avg merge
1d 18h
Merged PRs (30d)
774

Description

## Summary

As an example, when using a standalone plugin like Jetpack Social on a site connected to WordPress.com, the Sharing Buttons (which require Jetpack proper) can't be enabled from Calypso and give a non-helpful error:

196464250-c0949a80-dd2c-4d92-85d6-07d329630a7c

An additional example I noticed was trying to modify the the SEO settings (also requires Jetpack plugin) on `https://wordpress.com/marketing/traffic/example.com`

**We should audit other Calypso use cases here and work on improving messaging or updating the logic on those pages to account for sites with a full Jetpack connection, but not using the Jetpack plugin.**

Source: 7832-gh-Automattic/jpop-issues

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Sharing Buttons flow in Calypso with Jetpack Social installed, then check the SEO settings at wordpress.com/marketing/traffic/example.com. Audit the other Calypso use cases affected by a full Jetpack connection without the Jetpack plugin. Done means those pages either account for the connection state or show helpful messaging instead of the current error.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, react, wordpress
Domain
full-stack, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
43/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.