>>> I am experiencing the same situation as Deurk. >>> My settings are: >>> Server Side Sorting? off >>> Server Side Threading? off >>> Folder Threading? off >>> Sorted by? Date
>> I noticed the two of you have the same settings. [..] Do you have UID >> support on by any chance? > Yup! Okay... now I'm able to duplicate it, and I think I know the problem. When thinking about it, what is going wrong is fairly simple. Normally when SquirrelMail returns the data from the server, it is returned in date order (oldest first). We then run a sorting algorithm on the results, and store it in an array ($msort I think). We also keep the original results in an array ($msgs). I think what is happening is the DMN plugin is reading the $msgs array, and $msgs *should* be identical. What I'm guessing is that somehow they aren't being set. The UID values set in the $msgs array show that the message you had (1st in your list) is really last in the list. When clicking on the delete, it moves to the next, which in $msgs is the second to last value. This would explain why you get the "Prev" | "delete & Prev" links instead of "Next" | "Delete and Next" links. I shall take a look, and see if I can verify that this is in fact what is happening. Out of curiousity, when you turn OFF UID support, does the problem go away? Thanks -- Jonathan Angliss ([EMAIL PROTECTED]) ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
