wordpress-mobile / wordpress-mobile/WordPress-iOS
A jetpack site might disappear when Jetpack is deactivated
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3.9k
- Forks
- 1.2k
- Avg merge
- 23h 51m
- Merged PRs (30d)
- 58
Description
If you add a self hosted, then connect to Jetpack and later deactivate Jetpack, the site will disappear from the app. This is by design, but could be confusing to users.
I'm not sure what to do about it, if anything, but we could flag any self hosted as manually added in the app, then if it gets removed from the wp.com account, we migrate it back to a self hosted, but needing authentication (or maybe we keep the password from the start). This would require better prompts to re-authenticate though (see #687)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how the WordPress iOS app represents self-hosted sites after Jetpack is deactivated, then trace the related authentication and site-removal flow. The issue does not name files or tests; done would require an agreed behavior for retaining or migrating the site and prompting for authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100