Page MenuHomePhabricator

[5.0.0.503] non-main space articles not handled properly from Explore feed
Closed, ResolvedPublic

Description

Repro steps

  1. Visit an article which is not in main space - e.g. starts with Wikipedia: or User: e.g. User:Etonkovidova/sandbox
  2. When such articles made their way to Home page to 'Because you read ...' section - they are displayed as a placeholder without content

IMG_0388.PNG (2×1 px, 154 KB)

  1. Clicking on 'More like User:Etonkovidova/sandbox' bring an empty page

IMG_0389 (1).PNG (2×1 px, 67 KB)

Expected results

  • no-main space articles should be treated as other articles
  • if there is nothing to direct to (aka 'More like ...') the link should not be displayed.

API Note

MobileView now returns the "ns" field. Only articles in the article space (ns=0) should be used for recommendations.

Event Timeline

Etonkovidova raised the priority of this task from to Needs Triage.
Etonkovidova updated the task description. (Show Details)
JMinor triaged this task as Medium priority.Jan 27 2016, 7:20 PM
JMinor set Security to None.
JMinor renamed this task from [5.0.0.503] no-main space articles not handled properly from Home page to [5.0.0.503] no-main space articles not handled properly from Explore feed.Feb 6 2017, 7:52 PM
JMinor renamed this task from [5.0.0.503] no-main space articles not handled properly from Explore feed to [5.0.0.503] non-main space articles not handled properly from Explore feed.Feb 23 2017, 5:46 PM

set isExcludedFromFeed = true for pages without ns 0

@JMinor should this also exclude the main page? I'm seeing ns = 0 for the main page.

Will handle Main Pages in follow-up ticket.

Testing on iPhone 5s and iPhone 6s (iOS 10.2.1) and Wikipedia 5.4.0 (1081).

I haven't received any "Because you read" entries regarding "User:Etonkovidova/sandbox" with either device, while I have received "Because you read"s for other iOS test articles of late (i.e. rivers in California for T157643) so either it's still not fixed or I'm using the wrong specs. If anyone knows what might be happening in my case please let me know.

@Nicholas.tsg that is the correct test. Just re-tested on my iPhone 6S and this is fixed.