We’ve recently upgraded from RT 2 to RT v3.0.5 and every once in a while
the “Next”, “Previous”, “First” and “Last” buttons aren’t displayed on
the ticket Display screen. There doesn’t seem to be any reason for this
happening. I’m using Mozilla 1.4.
I also saw something strange after I upgraded from RT2.0.15 to 3.0.6. When I look at the tickets window RT says there are 23 tickets that match the search but only 19 tickets are actually listed…
Is this an upgrade bug or a 3.0.6 bug??
Stevo----- Original Message -----
From: Michael Gibbons
To: rt-users@lists.fsck.com
Sent: Monday, September 29, 2003 10:49 AM
Subject: [rt-users] RT 3.0.5 “Next” and “Previous” buttons sometimes not displayed
We’ve recently upgraded from RT 2 to RT v3.0.5 and every once in a while the “Next”, “Previous”, “First” and “Last” buttons aren’t displayed on the ticket Display screen. There doesn’t seem to be any reason for this happening. I’m using Mozilla 1.4.
I also saw something strange after I upgraded from RT2.0.15 to 3.0.6.
When I look at the tickets window RT says there are 23 tickets that
match the search but only 19 tickets are actually listed…
Is this an upgrade bug or a 3.0.6 bug??
It’s known miss feature. 4 Tickets match your search but are Dead thus
don’t display.
I also saw something strange after I upgraded from RT2.0.15 to 3.0.6.
When I look at the tickets window RT says there are 23 tickets that
match the search but only 19 tickets are actually listed…
Is this an upgrade bug or a 3.0.6 bug??
It’s known miss feature. 4 Tickets match your search but are Dead thus
don’t display.
“Dead” was the RT2 term for a Deleted ticket. I’d recommend reading the
documentation, specifically page 5 of the manual (found here: http://www.bestpractical.com/rt/draftmanual.pdf), to determine what
exactly this means.
Now, does anyone have any idea why the “Next” and “Previous” buttons
aren’t being displayed (the original subject of this e-mail)?
Every now and then, the “Next,” “Previous,” “First,” and “Last” buttons disappear, creating a bit of a navigation challenge. Our primary browser is Mozilla 1.4, and despite thorough testing, I can’t pinpoint a specific trigger for this issue. I’ve tried clearing the browser cache, ensuring JavaScript is enabled, and checking RT’s configuration settings without success.