Last modified: 2014-09-05 00:55:29 UTC
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.
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.
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]
