Page MenuHomePhabricator

Allow users to set LiquidThreads thread paging limit with preferences or view options
Open, NormalPublic

Description

When the page http://translatewiki.net/wiki/Support
has been altered from a normal talk page, its content
has been broken into several pages. That is counterproductive
when searching for something. With the newly introduced screen
clutter, it is now extremely hard and time consuming to find
something anyways. Average processing times of finding answers
to ones questions went up some 700 % to 30.000 % depending somewhat
on how long ago answers were given, and other random things.

This page is extremely unproductive now. Scattering everything over
several pages makes thing only worse - needlessly.


Version: unspecified
Severity: enhancement
URL: http://translatewiki.net/wiki/Support

Details

Reference
bz21690

Event Timeline

bzimport raised the priority of this task from to Normal.Nov 21 2014, 10:55 PM
bzimport set Reference to bz21690.
bzimport added a subscriber: Unknown Object (MLST).

You can search threads using the included search box. The intention is that paging takes the place of archival.

Paging could be effectively disabled by setting a high paging count, see bug 20961.

Paging cannot be used instead or archiving, (in twns support page)
since section counts are unrelated to the fact whether something is
done or not.

The MediaWiki search is not doing the same as the browsers search.
While it is of course nice to have both, MediaWikis search does not,
or hardly, work on some wikis.

I will not be disabling paging, as it mitigates performance problems.

My advice if you wish to avoid paging is:

  • On your own installation, you can set $wgLiquidThreadsDefaultPageLimit to a high number (from r59623).
  • On another installation, you can override paging by using {{#lqtpagelimit:highnumber}} (from r59623).

It may make sense for me to make it possible to view more than the paging limit on a particular page through user preference or display options. I'm changing the summary of this bug to reflect this.

See also bug 25055 for a sort of workaround.

Jorm added a comment.Sep 10 2010, 1:40 AM

This will become moot with the redesign and its infinite scrolling system.

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]

Jorm removed a subscriber: Jorm.Dec 26 2015, 7:30 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 26 2015, 7:30 PM
Meno25 removed a subscriber: Meno25.Feb 19 2016, 5:48 PM
Nemo_bis rescinded a token.Jul 16 2016, 8:01 AM
Jdforrester-WMF lowered the priority of this task from Normal to Lowest.Aug 4 2016, 11:35 PM
Jdforrester-WMF added a subscriber: Jdforrester-WMF.

LiquidThreads has been replaced by StructuredDiscussions on all Wikimedia production wikis (except one, which will be done soon). It is no longer under active development or maintenance, so I'm re-classifying all open LQT tasks as "Lowest" priority.

Nemo_bis raised the priority of this task from Lowest to Normal.Feb 24 2019, 8:37 AM

Restore information removed with now-invalid rationale.

Liuxinyu970226 lowered the priority of this task from Normal to Lowest.Mar 22 2019, 2:00 AM
Liuxinyu970226 added a subscriber: Liuxinyu970226.

@Nemo_bis Do you have Gerrit patches to fix this? If not, keep Lowest, or file a patch to revert my action here.

Nemo_bis raised the priority of this task from Lowest to Normal.Mar 22 2019, 1:09 PM

Restore information removed with invalid rationale.