Hi Andreas, I'm working on the same experiment as Joseph who submitted the bug report.
You are right, IDs greater than 10^5 are created no problem. The issue is with the internal elog link, in this case of the form elog:SequencerEvents/XXXXX The link generated uses only the first 5 digits of the message ID, and therefore links to the wrong message. In the two attachments you can see our sequencer event number 100098, first displaying the message where all of the ID is displayed and secondly in "full" view of the elog front page. Here, the "ID" column contains a link with the string: elog:SequencerEvents/10009. Our problem is that we often use this string to paste into other elogs and generate a link to the sequencer event message. However, since the string uses too few digits, we end up with a link to the wrong message
| Andreas Luedeke wrote: |
|
I am not sure I understand your bug report.
I can easily create IDs greater than 100'000 (see attached picture), but that is not your problem, or is it?
Cheers, Andreas
| Joseph McKenna wrote: |
|
We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000...
68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...
Is this a know bug we can find a fix for? We are using: elogd 2.9.2 built Jul 14 2015, 18:58:06 revision
|
|
|
Theme = default
CSS = tiny.css
Display mode = summary
Suppress default = 3
Self register = 2
Entries per page = 100
Filtered browsing = 0
Entries per page = 8
Reverse sort = 1
Restrict edit = 1
Summary lines = 1
Display Email recipients = 0
Comment = AH-Senden Ticketsystem
List Display = ID, Author, Auftraggeber, Kategorie, Arbeitsbeschreibung, Standort, Rechnername, Priorität, Status, erstellt am, Fertigstellung bis, fertiggestellt am
Thread Display = $Auftraggeber $Standort, $Arbeitsbeschreibung, $erstellt am, $Fertigstellung bis, $fertiggestellt am,
#Start Page = ?Status=2-offen&mode=threaded&sort=Standort
#Start Page = ?wpwd=1&mode=threaded&Status=1-To Do&sort=Standort
Date Format = %A, %B %d, %Y
Time Format = %A, %B %d, %Y, %H:%M
Message Height = 6
Attributes = Auftraggeber, Kategorie, Standort, Rechnername, Priorität, Status, erstellt am, in Bearbeitung seit, warten auf Freigabe seit, Fertigstellung bis, fertiggestellt am, fertiggestellt durch, Arbeitsbeschreibung, Author
Type To Do = Time
Type Date Entered = time
Type Date Closed = time
Options Kategorie = Netzwerk, TK-Anlage, Internet, SAN, ELO, Zeiterfassung, Exchange,Domäne, W-LAN DHCP, DHCP, Backup
Options Priorität = 1-sehr hoch, 2-hoch, 3-mittel, 4-niedrig, 99-alt,
Options Status = 1-To Do{1}, 2-offen{2}, 3-fertiggestellt{3}, 4-in Bearbeitung seit{4}, 5-warten auf Freigabe{5}
{1} Preset To Do = $Date
{2} Preset erstellt am = $Date
{3} Preset fertiggestellt am = $Date
{4} Preset in Bearbeitung seit = $Date
{5} Preset warten auf Freigabe seit =$Date
Options Standort = Geilenkirchen, Kerpen, Mönchengladbach, Kaarst, sonstige, alle
Extendable options = Standort, Kategorie, Priorität
Page Title = Ticketsystem Senden - $subject
Option Author = Filled In Automatically
Subst Author = $long_name
#Menu Commands = Back, New, Edit, Delete, Reply, Find, Select, Copy to, Move to,
Reverse sort = 1
Quick Filter = Auftraggeber, Standort, Status, Fertigstellung bis
Subst on reply subject = Re: $Arbeitsbeschreibung
Thread display = $subject, posted by $author on $Entry time
Thread icon = Icon
Remove on reply = Author, Author Email
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Author
Quick filter = Date, Category, Status
|