Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 18 of 806  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  1728   Mon Feb 27 11:16:56 2006 Warning Alex Halex@synergie-inf.comBug reportWindows2.6.1-1653Re: MOptions problem ?
[quote="Alex H"]Hi Stephan,
I have a unknown bug and need help :)!

First, please take a look to attached screenshot
On the "elog problem1.gif" and "elog problem2.gif" there aren't any problem.
The entry "Mairie STO" appears correct but when I try to edit the "Equipment" field, the list/combo shows 
improper data.
I obtain "- please select -" instead of "RT0004"
What's the problem ?
Thanks a lot.[/quote]

UP! No idea :'( ?
  1739   Wed Mar 1 19:51:05 2006 Warning Alexandre Gauthiersupernaut@underwares.orgBug reportLinux2.6.1-1622Inline images URL not working
Hello

I'm running elog on the blackdog embedded device so I can carry it around while doing my consultant work.

Whenever I try to insert an inline picture by using the
elog: /1
paths with ELCode, the link becomes "logbookname2/1" (Where logbookname is the name of my logbook) and hence, doesn't work. I recall that it worked once. The image did not display, but the URL seemed correct...

Any ideas?

EDIT: i inserted a space in the elog URL above because regardless of the code brackets, it would still get interpreted.
  1748   Sat Mar 4 06:08:29 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Crafted URL causes elog to coredump
While playing with TOP GROUP I managed to get elog 2.6.1 1660 on Solaris 9 to coredump. Since I didn't really understand TOP GROUP I tried a URL where I had http://elog.server.com/topgroupname/logbookname. Putting that logbookname at the end caused elog to dump.

Can this be reproduced by others?
  1764   Wed Mar 8 22:33:56 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1671OPTION <attribute> not working right in [ global <name>] Top Group
I've verified that when the following is part of the definition of a [logbook] OR is part of a regular [global] config:
Options Completed = Open{a}, Closed{b}
{a} Preset CompletedDate = 
{b} Preset CompletedDate = $date

. . . the intended function (when option "Open" is selected the attribute "CompletedDate" is cleared; when the option "Closed" is selected the attribute "CompletedDate" is filled with the current date)

When this same code is moved to a [global <name>] config the function no longer works (the attribute "CompletedDate" is not set).

This for me is a show stopper as using Top Group has allowed me to create and use logbooks in a way that I could not under the old way (single [global]. I have verified that the same thing happens under 2.5.9.
  1765   Thu Mar 9 04:46:42 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1671Removing 'New' from "List Menu commands" prevents saving elogd.cfg
Strange as it mmay seem, when I attempt to remove the "New" menu item from "List Menu commands" in a logbook section, I am no longer able to Save the config file -- I am presented with a message saying "Error: Command "Save" not allowed". I have to manually edit the file, add that menu item back in, and then all is ok. This is on the system where I am using 'Top Groups', so the logbook is a part of one of the top groups.
  1773   Tue Mar 14 17:51:52 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1668elogd 2.6.1 program Crash is repeatable under Windows
Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using "Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group feature. I am also including the .cfg that I used on my Windows box which is the same .cfg that I use in our Solaris environment.
  1841   Tue May 30 17:54:21 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1681Losing field 'focus' when using Conditional Attributes
Stefan, any way to address this? It appears to only be applicable when one defines conditional Options - when javascript updates the conditional lists the input focus appears to shift to the HTML edit area. I am still running ELOG V2.6.1-1681 and this is under Windows (my test system).


With version 2.6.1 rev 1681 I believe this is when I started seeing the behavior such that when a conditional attribute value is selected the focus switches to the message entry window. It looks like when the javascript cond_submit() is called for some reason on returning focus defaults to the message window. This occurs under Windows (rev 1861) and Solaris (rev 1864). I can see in function chkform() that focus is returned for checking Required attributes, but I see nothing for conditional attributes.

Thanks
  1847   Wed Jun 21 14:21:01 2006 Warning Ulrich Trüsselulrich.truessel@familienhund.chBug reportWindows2.6.1-6Corrupt page link
If a loggbook contains more than one page of entries, above and under the list are links for changing the page by number (or privous / last and all) conatining links looking like "http://localhost:8080/logbook/page2?mode=mode". This is the correct link and will work until Version 2.6.1-5!

In Version 2.6.1-6 the link is corrupted and look always like "http://localhost:8080/logbook/pag"
ELOG V3.1.5-3fb85fa6