Last modified: 2013-05-02 10:07:44 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T44902, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42902 - "wpSearchFilter" query string does not work on some wikipedias.
"wpSearchFilter" query string does not work on some wikipedias.
Status: RESOLVED DUPLICATE of bug 46154
Product: MediaWiki extensions
Classification: Unclassified
AbuseFilter (Other open bugs)
unspecified
All All
: Low normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-09 19:53 UTC by Sorawee Porncharoenwase
Modified: 2013-05-02 10:07 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Sorawee Porncharoenwase 2012-12-09 19:53:50 UTC
In Special:AbuseLog, "wpSearchFilter" query string does not work. I found this bug on Simple English and Thai Wikipedia. For example, https://simple.wikipedia.org/w/index.php?title=Special:AbuseLog&wpSearchFilter=2 should list only filter number 2, but it lists all filters instead. (There is no problem in English Wikipedia)
Comment 1 Octra Bond 2012-12-11 21:44:01 UTC
This problem occurs in Thai Wikipedia too. For example:

https://th.wikipedia.org/w/index.php?title=%E0%B8%9E%E0%B8%B4%E0%B9%80%E0%B8%A8%E0%B8%A9:%E0%B8%9B%E0%B8%B9%E0%B8%A1%E0%B8%81%E0%B8%B2%E0%B8%A3%E0%B8%A5%E0%B8%B0%E0%B9%80%E0%B8%A1%E0%B8%B4%E0%B8%94&wpSearchFilter=1

The wpSearchFilter does not work; it does not filter with ID=1 but show all result instead. I have known the bug for some time (but it is not a big deal for me).

I am a normal user if you want to know, in case of the issue might relate with admin level.
Comment 2 Sorawee Porncharoenwase 2013-05-01 18:04:32 UTC

*** This bug has been marked as a duplicate of bug 46154 ***
Comment 3 Tomasz W. Kozlowski 2013-05-01 18:36:09 UTC
This is in no way a duplicate of bug 46154, reopening.
Comment 4 Sorawee Porncharoenwase 2013-05-01 18:54:42 UTC
It was my misunderstanding. At the time that I reported this bug, I didn't know that in order to view details of Abuselog, I have to have the permission. After I knew that, I reported bug 46154. Since you had solved bug 46154, this bug was solved as well. Now everything works fine. So I closed this bug as duplicated. Thanks a lot for your help, anyway :)
Comment 5 Tomasz W. Kozlowski 2013-05-01 19:01:21 UTC
Sorry then!

*** This bug has been marked as a duplicate of bug 46154 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links