Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 669 of 808  Not logged in ELOG logo
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  1173   Sat Jun 4 12:21:21 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.5.9Re: reverse sort option does not work for quick filter

Heiko Scheit wrote:
The 'reverse sort' option does not work for quick filter searches. In the
URL there is always written 'reverse=0'. For normal 'Find' it works OK.


I don't understand the problem. If I take the example elogd.cfg from the distribution, it sorts in reverse order, since the file contains Reverse sort=1. If I apply a quick filter, the result is still sorted in reverse order (entry ID from high to low). If I set Reverse sort=0, the even after applying a quick filter, the entries are sorted with their ID from low to high. Applying a quick filter should not put a reverse=0 into the URL, so it's strange to me where this comes from. Can you try to reproduce the problem with the demo elogd.cfg?
  1172   Sat Jun 4 10:59:52 2005 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.6.0-betaRe: Incorrect Display
I finally found some time to fix the pippo-bug Wink.

It had to do with the request that one can turn on and off the summary lines of the text body in Guest list display. So if this option does not contain Text, the text summary is not shown for guest access, but only for registered access. This modification had the side effect that one column was dropped on the non-guest access.
  1171   Fri Jun 3 18:11:09 2005 Question Emiliano GabrielliAlberT@SuperAlberT.itInfoWindowslatestRe: A comprehensive listing of all commands elog performs

Gary Clayson wrote:
Can someone please enter a comprehensive list of the commands eLog will honor. I'm trying to build a 'decent' start page and am not totally familiar with eLog just yet. Thanks Stefan for an awesome application. The documentation is really decent, too. I just have been unable to locate a list of all commands available.
Thanks in advance.
Gary ;->


there's a link in the main elog web page.. it's under the Admin guide and it is the elog.cfg syntax guide
  1170   Fri Jun 3 18:02:25 2005 Entry Emiliano GabrielliAlberT@SuperAlberT.itBug reportWindows2.6.0-betaRe: Incorrect Display

Geoffrey Carman wrote:

David Spindler wrote:

BTW, I love elog and have it running at work. It is being used extensively.


We just did the 2.60 beta upgrade, and now our pre-existing logbooks, with a
List Display = Name, Author, Date for example will only show the first two fields.

It seems like Elog is dropping the last attribute in the List Display line.

We can 'fix' it by making it say:
List Display = Name, Author, Date, Date
so that it drops the second Date, but that is a bad workaround.

Anyone else seeing this?

Elog 2.60 beta on Linux, Firefox 1.04 as the client. Or IE fully patched on WinXP SP2.

PS: Love Elog at work here too! Truly has made our documentation way better. And RSS feeds of the logbooks is just wonderful.


I just reported it to Stefan last week ... it's the "pippo-bug" Smile I called it this way becouse you can put anything you want as garbage Attribute to go around the bug .. I temporary corrected my elogs configs addig a ", pippo" to every "List Display" line ...
  1169   Fri Jun 3 17:34:44 2005 Entry Geoffrey Carmangeoffc@yorku.caBug reportWindows2.6.0-betaRe: Incorrect Display

David Spindler wrote:

BTW, I love elog and have it running at work. It is being used extensively.


We just did the 2.60 beta upgrade, and now our pre-existing logbooks, with a
List Display = Name, Author, Date for example will only show the first two fields.

It seems like Elog is dropping the last attribute in the List Display line.

We can 'fix' it by making it say:
List Display = Name, Author, Date, Date
so that it drops the second Date, but that is a bad workaround.

Anyone else seeing this?

Elog 2.60 beta on Linux, Firefox 1.04 as the client. Or IE fully patched on WinXP SP2.

PS: Love Elog at work here too! Truly has made our documentation way better. And RSS feeds of the logbooks is just wonderful.
  1168   Thu Jun 2 06:45:55 2005 Question Gary Claysong_clayson@sbcglobal.netInfoWindowslatestA comprehensive listing of all commands elog performs
Can someone please enter a comprehensive list of the commands eLog will honor. I'm trying to build a 'decent' start page and am not totally familiar with eLog just yet. Thanks Stefan for an awesome application. The documentation is really decent, too. I just have been unable to locate a list of all commands available.
Thanks in advance.
Gary ;->
  1167   Wed Jun 1 21:00:01 2005 Cool Steve Jonessteve.jones@freescale.comBug reportAll2.5.9Re: Logbook locking issue

Steve Jones wrote:
Stefan, not a problem. ITMT, any idea how I can manually clear this "lock"? Is it embedded in the logbook itself?


Stefan Ritt wrote:
Sorry about my unusual slow response, but I'm pretty busy these days. I hope I will be able to address this problem in a two weeks from now.


Steve Jones wrote:
Stefan, any ideas on this problem?


Quote:
Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.

SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.

PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset".
  1166   Wed Jun 1 16:33:54 2005 Warning Stefan Rittstefan.ritt@psi.chBug reportAll2.5.9Re: Logbook locking issue
Sorry about my unusual slow response, but I'm pretty busy these days. I hope I will be able to address this problem in a two weeks from now.


Steve Jones wrote:
Stefan, any ideas on this problem?


Quote:
Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.

SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.

PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset".
ELOG V3.1.5-3fb85fa6