Page MenuHomePhabricator

Pagination on special page inclusion
Closed, DeclinedPublic

Description

When I use {{Special:Prefixindex/Foo Bar}} only a certain ammount of pages are shown.
It's just a poor plain list without any info about more pages. Ass pagination links on bottom please.

Example: http://www.mediawiki.org/wiki/User:Subfader/Pagination_on_special_page_inclusion


Version: unspecified
Severity: normal

Details

Reference
bz30966

Event Timeline

bzimport raised the priority of this task from to Needs Triage.Nov 21 2014, 11:50 PM
bzimport set Reference to bz30966.
bzimport added a subscriber: Unknown Object (MLST).
  • I'd like to see some "Ass pagination", but I ment "Add pagination".

Did I already express my hate for poor Bugzilla features such as preview, edit or a proper search? :P

(In reply to comment #2)

Did I already express my hate for poor Bugzilla features such as preview, edit
or a proper search? :P

I feel your pain...

(In reply to comment #0)

When I use {{Special:Prefixindex/Foo Bar}} only a certain ammount of pages are
shown.
It's just a poor plain list without any info about more pages. Ass pagination
links on bottom please.

Example:
http://www.mediawiki.org/wiki/User:Subfader/Pagination_on_special_page_inclusion

With the pagination links linking to the special page directly? On one hand it does make sense, on the other, people translcude special pages to get a specific set of results into a page (For example, list of user subpages). I'm not sure if they'd want the paging links going to some other page.

I don't care much where the link goes as long as there is some or info about more existing pages or even navigation.

"people translcude special pages to get a specific set of results into a page (For example, list of user subpages)"

Yeah but you're introuble as soon as you have more than X subpages.

Same for other inclusions, e.g. {{Special:Newpages}}

Broadly speaking, it probably makes sense in the future to replace these awful old-style inline inclusions with dynamic widgets that can query the wiki in a way that's reasonably friendly to caching etc. Those should do any paging/refresh/etc via ajax and such, and not be embedding separate data into the low-level page output.

(In reply to comment #5)

Broadly speaking, it probably makes sense in the future to replace these awful
old-style inline inclusions with dynamic widgets that can query the wiki in a
way that's reasonably friendly to caching etc. Those should do any
paging/refresh/etc via ajax and such, and not be embedding separate data into
the low-level page output.

I'd pretty much agree with that. ajax/api makes sense here.

yeah ok. someone feel free to close this.