mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

Ah that issue is not to do with pagination but more with how we sort
results coming out of the database.

The issue is they are sorted by title, which is a string, so the number
at the end of the string eg 1, 2 3 etc. are treated as part of the
string.

So  Pagination Group 14 comes before Pagination Group 14 due to
alphabetical sorting and not natural sorting as expected.

There are ways to achieve natural sorting but the main problem with them
is they either need the string to have some predictability - eg
position/length of integer to be predictable or to have some sql
function added to the database, neither of these options are acceptable.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1531610

Title:
  Clean up inconsistencies in the paginators

Status in Mahara:
  In Progress
Status in Mahara 15.10 series:
  New
Status in Mahara 16.04 series:
  In Progress

Bug description:
  Now that we have the paginators behaving with the same underlying code
  there has arisen some issues with the optional variables each
  paginator can use.

  These issues include:
  - pages using jump links opiton but not collections
  Need to make it consistent

  - Some places using limit per page from the get_account_preference($USER->get('id'), 'viewsperpage'); variable while other are set to the default 10 per page.
  Need to only use the account preference for portfolio/group/institution/site pages and not elsewhere
  Need to also have it so that if the page has less than 10 results to ignore the user preference

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1531610/+subscriptions