#1350 Incorrect pagination of message list

closed-fixed
nobody
5
2003-10-01
2003-07-07
Marcin Orlowski
No

If you hSet Squirrel to put max i.e. 30 entries per
message index, and have more than 30 mails in INBOX (or
in folder in general) SM'd paginate its output (30 per
page), and place some shortcut list in form "1 2 3 4 n"
depends of how many items you have. In case you have
lot of mails in a folder, SM is forced to 'compress'
shortcut list. I.e. by having 510 mails and 30 items
per page gives 17 pages (SM ouputs 1 2 ... 5 6 7 8 9 10
... 15 16 17). The bug lurks in the code that is
responsible for placing "..." in a clever manner. While
on the 1st, 2nd page we see:

1 2 3 4 5 6 7 ... 14 15 16 17

on 3rd is still fine:

1 2 3 4 5 6 7 8 ... 15 16 17

The bugs shows on 4th:

1 2 ... 4 5 6 7 8 9 ... 15 16 17

as you can see, theres' no way to go back to page 3,
even IMHO if there should be such possibility to have
at least one successor and one predecessor of
currently displayed page.

On the 8th page it starts to work fine again (pages 5,6
and 7 'shares' problems of 4th)

1 2 ... 4 5 6 7 8 9 10 ... 16 17

As for me, user should be able to trawerse thru pages
with easiest way, and that means s/he always have to be
able to access PAGE-1 and PAGE+1 related to currently
shown PAGE.

Discussion

  • Logged In: YES
    user_id=285765

    Can not reproduce this. Which SquirrelMail version?

     
  • Logged In: YES
    user_id=69131

    1.2.8

     
  • Logged In: YES
    user_id=476981

    Thijs, I can reproduce it. I saw this before. FYI the paginator
    routine in 1.5, 1.4.x === 1.2.8

     
  • Logged In: YES
    user_id=476981

    Thijs, I can reproduce it. I saw this before. FYI the paginator
    routine in 1.5, 1.4.x === 1.2.8

     
  • Logged In: YES
    user_id=476981

    Hmm, I experiented this a long time ago but I cannot
    reproduce it now. I even tested on mailboxes with 17 pages
    and no luck.

     
    • status: open --> closed
     
  • Logged In: YES
    user_id=476981

    Finally I could reproduce it and fixed it :)

     
    • status: closed --> closed-fixed