Using the app with a local MediaWiki instance requires a bit of hackage in both the app and the java-mwapi library which is a big time drain and a bad complexity to introduce when working in the MW domain. There should instead be a dev option to set the wiki endpoint. This functionality will make it easier to test MW changes, including the upcoming Spoon regression testing.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Deskana | T75616 Tracking: API/backend issues blocking Wikipedia app development | |||
| Resolved | Anomie | T32788 Allow triggering of user password reset email via the API | |||
| Resolved | Anomie | T48179 Allow a challenge stage during authentication | |||
| Resolved | None | T5709 Refactoring to make external authentication and identity systems easier | |||
| Resolved | Tgr | T43201 UserLoadFromSession considered evil | |||
| Resolved | Anomie | T67493 Session is started by EditAction (problem for extensions using UserLoadFromSession hook) | |||
| Open | Feature | None | T55156 Provide option to force a login session to end within a certain time | ||
| Resolved | None | T89459 Modernize MediaWiki authentication system (AuthManager) | |||
| Resolved | Tgr | T134945 Update API clients for AuthManager | |||
| Resolved | Dbrant | T135633 Add "remember me" support | |||
| Resolved | • Mholloway | T124229 Update login and account creation for API changes | |||
| Resolved | • Niedzielski | T120415 [Dev] Enable custom MediaWiki endpoint |
Change 268853 had a related patch set uploaded (by Niedzielski):
Add HTTPS parameter constructor
Change 268855 had a related patch set uploaded (by Niedzielski):
Enable custom MediaWiki endpoint
Change 268855 abandoned by Niedzielski:
Enable custom MediaWiki endpoint
Reason:
Scrapped in favor of smaller patches which I should have done in the first place. My apologies for the churn.
Change 274042 had a related patch set uploaded (by Niedzielski):
Add port to constructor
Change 274047 had a related patch set uploaded (by Niedzielski):
Use URL authority instead of host
Note for QA: This should not introduce any functional changes in the app (i.e. everything should work just as before).
I found some issues on the Samsung tablet, but looks good on the mobile phone. I'd like to discuss this during the meeting tomorrow.
Based on the discussion during the meeting, the search discrepancies were likely due to A/B testing, and the absence of a lead image on the tablet was due to screen size. Everything else looks good, so probably no regression.