Problem submitting entries in ELOG after migrating from Windows to Linux, posted by Edmundo T Rodriguez on Thu Mar 9 21:10:18 2006
|
I was able to install ELOG v2.61. in a Compaq ProLiant DL360 running with SUSE Linux v10
The migration/implementation went quiet well ...
|
Re: Problem submitting entries in ELOG after migrating from Windows to Linux, posted by Steve Jones on Fri Mar 10 06:12:55 2006
|
[quote="Edmundo T Rodriguez"]I was able to install ELOG v2.61. in a Compaq ProLiant DL360 running with SUSE Linux v10
The migration/implementation went quiet well ...
|
|
Strange "bug?" report - disappearing data when attribute is "Locked", posted by Steve Jones on Thu Mar 9 06:04:46 2006
|
[quote="Steve Jones"]I have come across an issue where an attribute value is "blanked" upon either editing or replying. The interesting thing is this is
a logbook entry that was "Moved" from one logbook to another, all under the same Top Group. All configs are done under the [global <topgroup>] so the
attribute is not being reset on purpose. Most interesting of all is this only happens:
|
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. |
|
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]
|
|
Crafted URL causes elog to coredump, posted by Steve Jones on Sat Mar 4 06:08:29 2006
|
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.
|
|
Re: Crafted URL causes elog to coredump, posted by Stefan Ritt on Mon Mar 6 14:04:12 2006
|
[quote="Steve Jones"]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.
|
|
Re: Crafted URL causes elog to coredump, posted by Steve Jones on Mon Mar 6 17:35:52 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]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.
|
|
Re: Crafted URL causes elog to coredump, posted by Stefan Ritt on Mon Mar 6 17:45:18 2006
|
[quote="Steve Jones"]Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660. [/QUOTE]
No, the above link just works fine, just click it. |
|
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]
|
|
[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]
|
require smileys to have whitespace on either side?, posted by Glenn Horton-Smith on Sat Mar 4 05:17:14 2006
|
It would be nice if elog would only interpret something as a smiley if it is surrounded by whitespace. It can be particularly annoying that an 8 followed
by a right paren becomes a "cool" smiley -- e.g., a parenthetical reference to event eighteen (18) becomes mangled... [That was "18" inside the parens.]
|
|
Re: require smileys to have whitespace on either side?, posted by Stefan Ritt on Mon Mar 6 13:50:07 2006
|
[quote="Glenn Horton-Smith"]It would be nice if elog would only interpret something as a smiley if it is surrounded by whitespace. It can be particularly
annoying that an 8 followed by a right paren becomes a "cool" smiley -- e.g., a parenthetical reference to event eighteen (18) becomes mangled... [That
was "18" inside the parens.]
|
|
Provide option to require smileys to be bracketed a la ELCode?, posted by Glenn Horton-Smith on Mon Mar 6 20:51:57 2006
|
[quote="Stefan Ritt"][quote="Glenn Horton-Smith"]It would be nice if elog would only interpret something as a smiley if it is surrounded by whitespace.
It can be particularly annoying that an 8 followed by a right paren becomes a "cool" smiley -- e.g., a parenthetical reference to event eighteen (18)
becomes mangled... [That was "18" inside the parens.] ...
|
|
eLog Version number as eLog attribute?, posted by Steve Jones on Fri Feb 24 16:40:38 2006
|
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?
|
|
Re: eLog Version number as eLog attribute?, posted by Stefan Ritt on Wed Mar 1 10:31:33 2006
|
[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?
|
Re: eLog Version number as eLog attribute?, posted by Steve Jones on Wed Mar 1 20:22:28 2006
|
[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?
|
[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?
|
|
Allow $attributes in "Comment = " option, posted by Steve Jones on Fri Mar 3 18:02:59 2006
|
| Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks? |
|
Re: Allow $attributes in "Comment = " option, posted by Stefan Ritt on Mon Mar 6 13:40:40 2006
|
[quote="Steve Jones"]Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks?[/quote]
The "Comment =" option for logbooks gives a general comment, like [b]Discussion forum about ELOG[/b] for this forum. Since this comment is global, it does |
|
Re: Allow $attributes in "Comment = " option, posted by Steve Jones on Mon Mar 6 17:43:11 2006
|
[quote="Stefan Ritt"][quote="Steve Jones"]Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks?[/quote]
The "Comment =" option for logbooks gives a general comment, like [b]Discussion forum about ELOG[/b] for this forum. Since this comment is global, it does |