Last modified: 2009-01-15 17:09:05 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 T3592, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 1592 - allow users to set default filters for Special:Recentchanges
allow users to set default filters for Special:Recentchanges
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Lowest enhancement with 4 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-02-25 21:14 UTC by John Lucero
Modified: 2009-01-15 17:09 UTC (History)
1 user (show)

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


Description John Lucero 2005-02-25 21:14:24 UTC
on the, Special:Recentchanges page, i suggest there be viewing prefrences, with
hide patrolled, hide minor, hide/show bots, show on how many days, how many
posts per page. I notice on refresh of the page, it resets, which gets kinda
Comment 1 Rowan Collins [IMSoP] 2005-02-26 14:58:32 UTC
I'm not quite sure what kind of "refresh" you're doing that's losing these
filters - if you just click your browser's refresh/reload button, it should go
to the same URL, which includes the same filters. 

If you go away and come back to the recent changes page, then yes, it will
return to the default settings; the easiest way around this is just to bookmark
the page once you've got it set to the right preferences - then, whenever you
visit that bookmark, it will show recentchanges with those settings. I guess
there could be some way of saving your preferred settings as a preference,
though, if anyone felt it was worth coding it.
Comment 2 Aaron Schulz 2009-01-15 17:09:05 UTC
Filters appear to be there now.

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