Page MenuHomePhabricator

Bad-prefix triggered differently in API compared to Upload and UploadWizard
Closed, InvalidPublic

Description

bad-prefix, the warning that is triggered on filenames such as "DSC 123" can also be triggered in the API by some subsection of normal filenames such as
Scandinavia complectens Sueciæ, Daniæ et Norvegiæ regna – ex tabulis - Kungliga Biblioteket - 10348309.tif .

The same filename does however not trigger a warning in either Upload or UploadWizard.

Event Timeline

Lokal_Profil raised the priority of this task from to Needs Triage.
Lokal_Profil updated the task description. (Show Details)
Lokal_Profil subscribed.

Upon closer inspection shows thhat the testing is implemented completely differently in the three modes:

Testing with "P1100961.JPG":

  • Triggers the warning in UploadWizard
  • Triggers no warning in the API
  • Triggers no warning in Special:Upload
matmarex changed the task status from Open to Stalled.May 12 2016, 5:45 PM
matmarex subscribed.

I can't reproduce any of the problems described here on Commons. Is this fixed, or am I misunderstanding your report?

I can't reproduce any of the problems described here on Commons. Is this fixed, or am I misunderstanding your report?

We manually fixed the filter for the Scandinavia example. The P1100961 one should still trigger errors (unless it was fixed).

The main gist of the report was however that the api, UploadWizard and Special:Upload use different mechanisms/black-lists to determine bad-prefix. They should all use the same one.

But they don't, as far as I can see. What do I need to do to trigger the warning for P1100961 in UploadWizard?

Just tested (now on my laptop). Looks like this one was fixed at some point, can't recreate this anymore. Close as invalid?

Thanks for rechecking!