Automattic / Automattic/jetpack
Feature Request: Improve Error Messaging for Manual Jetpack Social Shares When User Is Not Connected to WordPress.com
- Dominant language
- PHP
- Stars
- 1.8k
- Forks
- 898
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 774
Description
### Impacted plugin
Social
### What
When an Editor or Admin user attempts to manually share a post via Jetpack Social, and they are not connected to [WordPress.com](http://WordPress.com), the UI fails silently with a generic error: “Unable to share the Post” We’d like to see clearer error messaging that explicitly informs the user that they must connect their [WordPress.com](http://WordPress.com) account in order to complete the action.
### How
It would be great l to improve the error messaging shown when a manual share attempt fails due to the user not being connected to [WordPress.com](http://WordPress.com). Currently, the UI just shows a generic red banner saying “Unable to share the Post” (screenshot attached), which doesn’t give users any hint about what went wrong or how to fix it.
We suggest updating the message to something more specific, like:
“Please connect your [WordPress.com](http://WordPress.com) account to share this post.”
It could also include a link or button that brings the user to Jetpack → My Jetpack to connect their account.
This would help reduce confusion for users and support teams, especially since the “shared” status of the connection implies manual sharing should work without needing additional setup. The current message also makes it unclear that the post was saved successfully, even if the share itself failed.
Error in network tab:

Contributor guide
Research direction
The issue identifies the Jetpack Social manual-share UI and the generic “Unable to share the Post” failure, but names no file or test. Trace that failure when the user is not connected to WordPress.com, then verify that the message explains the connection requirement and that the saved-post state remains clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php, react
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100