Re: Crafted URL causes elog to coredump, posted by Steve Jones on Mon Mar 6 18:04:39 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.
[/QUOTE]
|
|
Re: Crafted URL causes elog to coredump, posted by Steve Jones on Mon Mar 6 18:06:32 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.
[/QUOTE]
|
[RESOLVED] eLog Version number as eLog attribute?, posted by Steve Jones on Mon Mar 6 18:36:34 2006
|
[quote="Steve Jones"][quote="Stefan Ritt"][quote="Steve Jones"]When a footer is used (via Bottom text = <filename>) eLog no longer displays the eLog version
number at the bottom. Is it possible to somehow expose the version/revision as an eLog attribute or have the version still display even when a replacement
footer is specified?
|
|
[UPDATE] Re: Crafted URL causes elog to coredump, posted by Steve Jones on Mon Mar 6 18:54:32 2006
|
[quote="Steve Jones"][quote="Stefan Ritt"][quote="Steve Jones"]Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring
under rev 1660. [/QUOTE]
|
|
[UPDATE2] Re: Crafted URL causes elog to coredump, posted by Steve Jones on Wed Mar 8 18:05:54 2006
|
[quote="Steve Jones"][quote="Steve Jones"][quote="Stefan Ritt"][quote="Steve Jones"]Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum.
This is occurring under rev 1660. [/QUOTE]
|
|
[Segmentation Fault source identified] Verbose Output: Re: Crafted URL causes elog to coredump, posted by Steve Jones on Wed Mar 8 20:19:14 2006
|
[quote="Steve Jones"][quote="Steve Jones"][quote="Steve Jones"][quote="Stefan Ritt"][quote="Steve Jones"]Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum.
This is occurring under rev 1660. [/QUOTE]
|
OPTION <attribute> not working right in [ global <name>] Top Group, posted by Steve Jones on Wed Mar 8 22:33:56 2006
|
I've verified that when the following is part of the definition of a [logbook] OR is part of a regular [global] config:
[code]
|
|
Removing 'New' from "List Menu commands" prevents saving elogd.cfg, posted by Steve Jones on Thu Mar 9 04:46:42 2006
|
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. |