| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1170
|
Fri Jun 3 18:02:25 2005 |
 | Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | Windows | 2.6.0-beta | Re: 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"  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 |
| Geoffrey Carman | geoffc@yorku.ca | Bug report | Windows | 2.6.0-beta | Re: 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 |
 | Gary Clayson | g_clayson@sbcglobal.net | Info | Windows | latest | A 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 |
 | Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.9 | Re: 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 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.5.9 | Re: 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". |
|
|
|
1165
|
Wed Jun 1 16:14:22 2005 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.9 | Re: Logbook locking issue |
| 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". |
|
Hmmm, I don't seem to be seeing any responses - is email being generated? |
|
1164
|
Tue May 31 09:07:37 2005 |
 | Alex H | alex@synergie-inf.com | Request | Windows | 2.5.8-6 | Re: password encryption | | Thanks Stefan 8) |
|
1163
|
Mon May 30 20:16:11 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 2.5.8-6 | Re: password encryption |
| Emiliano Gabrielli wrote: |
I don't have double checked .. but .. why we need to pass the sensible information in the Query String ??
Are you sure that putting it in an hidden field (and eventualli using a GET methon in the <form>-tag) can't be a solution? |
Hidden means only these fields are not shown in the form, but they are added to the URL in the same way as non-hidden fields. But I got another idea: I will try to use a POST form instead of the GET form. Using the POST method, fields are attached to the request and not present in the URL. Hope this will work. When I find some time to work on it I will let you know. |
|
|
ELOG V3.1.5-3fb85fa6 |