Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 211 of 795  Not logged in ELOG logo
ID Dateup Icon Author Author Email Category OS ELOG Version Subject
  1751   Mon Mar 6 13:50:07 2006 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.6.1-1668Re: require smileys to have whitespace on either side?

Glenn Horton-Smith wrote:
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.]

Is there already a way to solve this issue (other than always previewing your entries and adding spaces before parans)? Is the feature hard to implement?


Interpreting smileys only if they are surrounded by whitespace does not solve the problem completely. It will solve it for (1\8), but not if you have (1, \8) (1, 9) in your text. So it's not a good solution. If you have problems with simleys, I would post my text in plain mode, or surround your numbers with [code]...[/code] tags. If you write

[code](1\8)[/code]

then it will look like
(18)

which should be fine.
  1752   Mon Mar 6 14:04:12 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

Steve Jones wrote:
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?


No. This forum has the "elog" as the top group, "Forum" as the logbook, so if I write

http://midas.psi.ch/elogs/elog/Forum

it does not crash.
  1753   Mon Mar 6 17:35:52 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

Stefan Ritt wrote:

Steve Jones wrote:
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?


No. This forum has the "elog" as the top group, "Forum" as the logbook, so if I write

http://midas.psi.ch/elogs/elog/Forum

it does not crash.



Quote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.
  1754   Mon Mar 6 17:43:11 2006 Reply Steve Jonessteve.jones@freescale.comRequestAll2.6.1Re: Allow $attributes in "Comment = " option

Stefan Ritt wrote:

Steve Jones wrote:
Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks?


The "Comment =" option for logbooks gives a general comment, like Discussion forum about ELOG for this forum. Since this comment is global, it does not make sense to have $attribute substitution.



Quote:
Ok, just a thought. Thanks
  1755   Mon Mar 6 17:45:18 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

Steve Jones wrote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.


No, the above link just works fine, just click it.
  1756   Mon Mar 6 18:04:39 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

Stefan Ritt wrote:

Steve Jones wrote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.


No, the above link just works fine, just click it.



Quote:
I was afraid to try Big grin . Ok, then the issue *might* be rev 1660 or perhaps the fact that compiled under Solaris it does this. Any suggestions on how to find out?
  1757   Mon Mar 6 18:06:32 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.1-1660Re: Crafted URL causes elog to coredump

Stefan Ritt wrote:

Steve Jones wrote:
Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring under rev 1660.


No, the above link just works fine, just click it.



Quote:
I was afraid to try Big grin . Ok, then the issue *might* be rev 1660. On my production version running 2.5.3 I get the expected "Invalid URL: <name>" box. Any suggestions on how to find out?
  1758   Mon Mar 6 18:36:34 2006 Smile Steve Jonessteve.jones@freescale.comQuestionAll2.5.9[RESOLVED] eLog Version number as eLog attribute?

Steve Jones wrote:

Stefan Ritt wrote:

Steve Jones wrote:
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?

Thanks!


I added that feature, but will not be able to commit it before the next weekend.



Quote:
Not a problem! Thanks



Steve Jones wrote:
Works as requested!!
ELOG V3.1.5-fe60aaf