Feature Requests item #1664425, was opened at 2007-02-20 10:30 Message generated for change (Comment added) made by mamandel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1664425&group_id=103 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark A. Mandel (mamandel) Assigned to: Nobody/Anonymous (nobody) Summary: next/previous message links should use active sort method Initial Comment: When you are reading a message in an archive, the "previous message" and "next message" always refer to the sort by date, ignoring the sort that you are currently using. This makes them useless for reading through a thread, or for looking at messages by the same author or with the same subject line. They should use the sort order that the user has selected. We use version 2.1.7. ----------------------------------------------------------------------

Comment By: Mark A. Mandel (mamandel) Date: 2007-02-20 19:46

Message: Logged In: YES user_id=915526 Originator: YES (Update) So, give the admin an option, check boxes, for which sort order(s) to use when building the archive. If I as administrator am willing to spend the space at the top of each letter page to show prev and next by date, prev and next by thread, prev and next by author, and prev and next by subject, or any subset of those pairs, I'd like that option. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-20 19:31 Message: Logged In: YES user_id=1123998 Originator: NO Actually, the previous and next links refer to thread order, not date order. Also, this issue has been partially addressed for Mailman 2.2 by changing the description of the links to: # Previous message (by thread): <prior subject> # Next message (by thread): <next subject> I know this doesn't answer your request, but given the way the pipermail html archives are built as static html pages, your request would require a separate html file for each message/sequence, thus nearly quadrupling the size of the html archive. The alternative would require archive message pages to be built on the fly by CGIs for both public and private archives. Neither of these alternatives is likely to be implemented in the current pipermail archiver. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1664425&group_id=103