MHonArc - Bugs: bug #372, Links to thread index from message...
You are not allowed to post comments on this tracker with your current authentication level.
bug #372: Links to thread index from message page do not link to the correct thread index page when MULTIPG and TREVERSE is active
Submitter: | Earl Hood <ehood> | ||
Submitted: | Fri 10 May 2002 04:49:02 AM UTC | ||
Votes: | 100 | ||
Category: | Threading | Severity: | 2 - Minor |
Priority: | 1 - Later | Item Group: | Incorrect Behavior |
Status: | Postponed | Privacy: | Public |
Assigned to: | ehood | Open/Closed: | Open |
Operating System: | All | Perl Version: | All |
Component Version: | <=2.6.10 | Fixed Release: |
Mon 03 Jan 2011 06:06:53 AM UTC, comment #3: |
Earl Hood <ehood>![]() ![]() |
Wed 15 Nov 2006 11:08:06 PM UTC, comment #2: Tho my search of of the web for archives using Mhonarc multipage reverse date order did not turn up much, I think this is a very useful format. My ISP is just dealing with the bug by disabling such links :( The archives of my main list has nearly 25,000 messages (about 125 index pages of 200 messages per index page) See them via http://cohousing.org/cohousing-L
|
Fred H Olson <fholson> |
Mon 02 May 2005 06:10:56 PM UTC, comment #1: Problem occurs for reverse date indexes also.
|
Earl Hood <ehood>![]() ![]() |
Fri 10 May 2002 04:49:02 AM UTC, original submission:
OPEN: The problem is that a listing for a message in a thread index is not "fixed" due to how threads are organized. Non-related messages can move the location of a message listing, but currently MHonArc is unable to detect this. A possible solution is to compare old ordinal location with new ordinal location for each message. If different, see if new position cause message to move to another index page. If so, mark message to be edited. This kind of check would cause a performance hit, but it may be unavoidable inorder to fix the
|
Earl Hood <ehood>![]() ![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 100 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 8 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2011-01-03 | ehood | Severity | 1,5 | ![]() |
2 - Minor |
Priority | 2 | ![]() |
1 - Later | ||
Status | None | ![]() |
Postponed | ||
2006-11-15 | fholson | Carbon-Copy | - | ![]() |
Added fholson |
2005-05-02 | ehood | Operating System | None | ![]() |
All |
Perl Version | ![]() |
All | |||
Component Version | ![]() |
<=2.6.10 | |||
2002-05-10 | ehood | Category | None | ![]() |
None |
Powered by Savane 3.12.
Corresponding source code
Unsure when, or if ever, this problem will be addressed.
Going to postpone it for now. Item does not seem to have
many users demanding for a fix.
May tag this as a "Known Limitation" in the future and
close it if no additional movement is done for this item.