Re: a bug and a question, posted by Stefan Ritt on Thu Jul 11 10:36:09 2002
|
> If you have only one entry in the logbook and have it set up in threaded
> mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon
> of the entry or the number of the entry to see it, it does not allow you
|
convert: unrecognized option '-set', posted by Devin Bougie on Mon Jan 26 22:01:07 2009
|
Hello,
We are now running elog-2.7.5 in a Scientific Linux 4 (RHEL4) system, which uses ImageMagick 6.0.7.1. After uploading an image, the image
|
|
Re: convert: unrecognized option '-set', posted by Stefan Ritt on Tue Jan 27 09:19:22 2009
|
> Hello,
>
> We are now running elog-2.7.5 in a Scientific Linux 4 (RHEL4) system, which uses ImageMagick 6.0.7.1. After uploading an image, the image
|
Long cookie content is not handled properly., posted by Simon Patton on Tue Apr 14 22:51:15 2009
|
I discovered the infinite loop in 2.7.5 which can happen when a cookie's content is longer that the cookie array
designed to hold it. I also note that this issue has been addressed in 2.7.6, but the solution does not appear
to be correct and it can end up completely confusing the cookie extraction.
|
|
Re: Long cookie content is not handled properly., posted by Stefan Ritt on Wed Apr 15 09:26:37 2009
|
[quote="Simon Patton"]I discovered the infinite loop in 2.7.5 which can happen when a cookie's content is longer that the cookie array
designed to hold it. I also note that this issue has been addressed in 2.7.6, but the solution does not appear
to be correct and it can end up completely confusing the cookie extraction.
|
|
Auto-increment substitutions broken with records for multiple days, posted by Richard Stamper on Wed Jun 24 15:02:49 2009
|
With a logbook defined by
[test]
|
|
Re: Auto-increment substitutions broken with records for multiple days, posted by Stefan Ritt on Thu Jun 25 10:09:18 2009
|
> An alternative patch:
>
> /* if date part matches */
|
elogd keeps crashing, any thoughts?, posted by Allen on Thu Dec 3 20:25:50 2009
|
We are trying to track down an issue where elogd just stops, and I cannot seem to find a cause.
In the logs, I see: |