Page MenuHomePhabricator

TypeError on Special:NewPagesFeed Articles for Creation filter: "Cannot read property 'stats' of undefined" and "Cannot read property 'pages' of undefined"
Closed, ResolvedPublicBUG REPORT

Description

List of steps to reproduce (step by step, including full links if applicable):

What happens?:
The UI indefinitely says "Please wait..." and I get "Uncaught TypeError: response.pagetriagestats is undefined" and "Uncaught TypeError: response.pagetriagelist is undefined".

What should have happened instead?:
The feed should have loaded as normal.

Software version (if not a Wikimedia wiki), browser information, screenshots, other information, etc:
The bug still happens with safemode, the bug only happens when filtered to "Articles for Creation", filtering to "New Page Patrol" works fine. The bug does not happen on https://test.wikipedia.org. The bug happens in Firefox 88.0.1 (20210504152106), and I've also reproduced it in Microsoft Edge 90.0.818.62, in which the error is "Uncaught TypeError: Cannot read property 'stats' of undefined" and "Uncaught TypeError: Cannot read property 'pages' of undefined". The bug does not happen when logged out.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Aklapper renamed this task from Uncaught TypeError on Special:NewPagesFeed Articles for Creation filter to TypeError on Special:NewPagesFeed Articles for Creation filter: "Cannot read property 'stats' of undefined" and "Cannot read property 'pages' of undefined".May 18 2021, 10:31 PM

Thanks for reporting! Did this break recently? Is this a significant problem for your work? The page seems to work for me, and the error logs show 20-ish instances for the last 7 days, from two different devices, clustered around the same time, so this issue might be specific to your setup (a gadget interfering, maybe?).

Interestingly, disabling all gadgets, beta features, and other settings, did not fix this issue. However, I used the "Restore all default settings" which did fix this issue. So I still do not know exactly what in my configuration was causing this, but it is no longer occurring.