| 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. |
|
1162
|
Mon May 30 19:56:01 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | Windows | 2.5.8-6 | Re: password encryption |
| Gary Clayson wrote: | Hello Alex and Stefan,
I know of only one way to "hide" the text of the status bar in a web browser;
use JavaScript - specifically the status method (as in the following example):
<!-- the following goes in the body of the document, perhaps in a link. -->
<!-- sample link -->
<a href="javascript://place link url here"
onMouseOver="window.status='Status Bar Text Goes Here'; return true">Link Text Here</a>
<!-- place the following script in the head of the document -->
<script language="JavaScript" type="text/javascript"><!--
window.defaultStatus="Default Status Bar Text Here";
--></script>
Of course the above only works in those browsers that support javascripting,
but it is one way to hide the actual text of links from the user.
Hopefully this helps you!
Gary Clayson
| Alex H wrote: | Hi Stefan,
I have found a little problem with elog. I'am using ELOG V2.5.8-6. When I'am on the logon page,
I type my Login and password and hit "submit", in the bottom of IE, we can show my password without encryption, it can be dangerous. I have made a screenshot to explain my problem better.
Could you fix it for the next release ?
Thanks a lot.
Alex |
|
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? |
|
1161
|
Mon May 30 19:18:34 2005 |
| Gary Clayson | g_clayson@sbcglobal.net | Request | Windows | 2.5.8-6 | Re: password encryption | Hello Alex and Stefan,
I know of only one way to "hide" the text of the status bar in a web browser;
use JavaScript - specifically the status method (as in the following example):
<!-- the following goes in the body of the document, perhaps in a link. -->
<!-- sample link -->
<a href="javascript://place link url here"
onMouseOver="window.status='Status Bar Text Goes Here'; return true">Link Text Here</a>
<!-- place the following script in the head of the document -->
<script language="JavaScript" type="text/javascript"><!--
window.defaultStatus="Default Status Bar Text Here";
--></script>
Of course the above only works in those browsers that support javascripting,
but it is one way to hide the actual text of links from the user.
Hopefully this helps you!
Gary Clayson
| Alex H wrote: | Hi Stefan,
I have found a little problem with elog. I'am using ELOG V2.5.8-6. When I'am on the logon page,
I type my Login and password and hit "submit", in the bottom of IE, we can show my password without encryption, it can be dangerous. I have made a screenshot to explain my problem better.
Could you fix it for the next release ?
Thanks a lot.
Alex |
|
|