wordpress-mobile / wordpress-mobile/WordPress-iOS

Posts from JP connected sites without a JP paid plan are not indexed in tags feeds

Open
#22,435 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Enhancement Reader
Dominant language
Swift
Stars
3.9k
Forks
1.2k
Avg merge
23h 51m
Merged PRs (30d)
58

Description

Internal discussion ref: p1705052443959929-slack-C0180B5PRJ4

Expected behavior

When a user posts to a JP-connected site using a tag, the post should appear in that tag feed in the reader.

Actual behavior

When a user posts to a JP-connected site using a tag, the post appears in that tag feed in the reader only if there is an active JP paid plan on that site.

This is due to some filtering in place in the backend. Especially thinking of the prompts "View all answers" scenario, that shows posts for the daily prompt tag, we might consider showing a nudge "to educate the user that their blog can be included in more places with a plan".

(NOTE: if we go this way, for it to be reliable and future-proof, we should make it driven by a flag sent by the API)

Tested on [iPad 7th gen], iOS [17.0], Jetpack iOS / WordPress iOS [24.0]

Ref: Android twin issue

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the iOS reader tag-feed flow and the backend filtering described in the issue, then compare the Android twin issue #19997. Confirm where the JP paid-plan condition is applied and whether the API provides the proposed flag; done means eligible posts from JP-connected sites appear in tag feeds without requiring a JP paid plan.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
api, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.