Last modified: 2014-09-05 00:55:38 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 T27054, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25054 - Per-page configurable date-based thread limit
Per-page configurable date-based thread limit
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 21690 25055
Blocks: 24815
  Show dependency treegraph
 
Reported: 2010-09-04 16:27 UTC by Nemo
Modified: 2014-09-05 00:55 UTC (History)
5 users (show)

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


Attachments

Description Nemo 2010-09-04 16:27:29 UTC
Bug 20961 has been fixed, but it should also be possible to set per-page how old the last included thread should be (e.g., 7 days). It makes sense that on some pages you show all recent discussions, even if they're many, because they all need the same attention (e.g. [[WP:AN/I]] and similar pages or the village pump), espcially if you can't mark a thread as closed/resolved (see also bug 24815).
Comment 1 Nemo 2010-09-04 16:44:30 UTC
See also bug 25055 for a sort of workaround.
Comment 2 Brandon Harris 2010-09-10 01:29:45 UTC
This is going to be getting changed in the redesign - the way that the table of contents works - so it's a bit of a moot bug.

I am not normally a fan of per-page configuration options. However, WP:AN/I is a big concern of mine, so it isn't something I'm willing to throw away entirely.

I'm going to close this, with the caveat that we can reopen if the issue requires additional attention.
Comment 3 Andre Klapper 2013-01-09 13:24:54 UTC
Brandon:
This report has been in ASSIGNED status for more than one year and you are set as its assignee. In case that you are not actively working on a fix, please reset the bug status to NEW/UNCONFIRMED.
In case you do not plan to work on a fix in the near future: Please also edit the "Assigned To" field by clicking "Reset Assignee to default", in order to not prevent potential contributors from working on a fix. Thanks for your help!
[assigned>=1y]

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


Navigation
Links