| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1152
|
Wed May 18 14:20:23 2005 |
 | Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | | ? | error message from this forum | Just after submitting the last message, the following error message was displayed:
Error sending Email via "mailsend.psi.ch": malformed address: synergie-infcom> |
|
1153
|
Wed May 18 19:52:41 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | | ? | Re: error message from this forum |
| Heiko Scheit wrote: | Just after submitting the last message, the following error message was displayed:
Error sending Email via "mailsend.psi.ch": malformed address: synergie-infcom> |
Sombody used an invalid formed email address, like user<at>domain<dot>com, on which the SMTP server complained. I would like to note here that the email addresses registered in this forum are not published in any way, so there is no risk to get spam from that (except the normal elog notifications, which can be turned off easily). |
|
1155
|
Sat May 21 15:05:23 2005 |
 | David Spindler | dsspindler@earthlink.net | Bug report | Windows | 2.6.0-beta | Incorrect Display | I hope this is the correct place for an apparent bug report. The display is incorrect except when displaying a particular entry. I just downloaded 2.6.0-beta thinking I was getting 2.5.9. Nice surprise. The elcode (bbcode? ) is a great idea, but the display, when showing the main screen of a logbook does not have the correct fields showing in the correct places. I will attach two screen captures for illustraton. Never mind, I guess not. It is not letting me upload the screen captures. On the main screen, for example, my field contents for "Route" appear in the "Text" field. But when on the specific entry screen, these field contents are in the correct field. I will be glad to eamil the screen captures, if anyone wants.
I am running Firefox 1.0.3 (same results with IE 6, BTW), on a WinXP OS (sorry fellows, but I am still in process of learning Linux, so I have not tried this version of elog on it, yet), on a Gateway 2.2 GHZ, 1 GB RAM PC.
BTW, I love elog and have it running at work. It is being used extensively. |
| Attachment 1: capture-firefox-1.03.JPG
|
|
|
1156
|
Sat May 21 15:23:08 2005 |
| David Spindler | dsspindler@earthlink.net | Bug report | Windows | 2.6.0-beta | Re: Incorrect Display |
| David Spindler wrote: | I hope this is the correct place for an apparent bug report. The display is incorrect except when displaying a particular entry. I just downloaded 2.6.0-beta thinking I was getting 2.5.9. Nice surprise. The elcode (bbcode? ) is a great idea, but the display, when showing the main screen of a logbook does not have the correct fields showing in the correct places. I will attach two screen captures for illustraton. Never mind, I guess not. It is not letting me upload the screen captures. On the main screen, for example, my field contents for "Route" appear in the "Text" field. But when on the specific entry screen, these field contents are in the correct field. I will be glad to eamil the screen captures, if anyone wants.
I am running Firefox 1.0.3 (same results with IE 6, BTW), on a WinXP OS (sorry fellows, but I am still in process of learning Linux, so I have not tried this version of elog on it, yet), on a Gateway 2.2 GHZ, 1 GB RAM PC.
BTW, I love elog and have it running at work. It is being used extensively. |
I guess it did upload. Here is the other screen capture.
BTW, I received the following message upon submitting my last post:
| Quote: | | "Error sending Email via "mailsend.psi.ch": malformed address: <>" |
|
| Attachment 1: capture-firefox-1.03-log-entry.JPG
|
|
|
1157
|
Mon May 23 17:47:24 2005 |
| David Spindler | dsspindler@earthlink.net | Bug report | Windows | 2.6.0-beta | Re: Incorrect Display | Never mind. I figured it out. I used two fields (date and time) that are automatically placed in elog. It messed up the spacing, altough what was puzzling was that it displayed correctly on the entry itself, but not the list. Anyway, I renamed the date and time to another name and it is ok.
Thanks, anyway. Keep up the good work.
| David Spindler wrote: |
| David Spindler wrote: | I hope this is the correct place for an apparent bug report. The display is incorrect except when displaying a particular entry. I just downloaded 2.6.0-beta thinking I was getting 2.5.9. Nice surprise. The elcode (bbcode? ) is a great idea, but the display, when showing the main screen of a logbook does not have the correct fields showing in the correct places. I will attach two screen captures for illustraton. Never mind, I guess not. It is not letting me upload the screen captures. On the main screen, for example, my field contents for "Route" appear in the "Text" field. But when on the specific entry screen, these field contents are in the correct field. I will be glad to eamil the screen captures, if anyone wants.
I am running Firefox 1.0.3 (same results with IE 6, BTW), on a WinXP OS (sorry fellows, but I am still in process of learning Linux, so I have not tried this version of elog on it, yet), on a Gateway 2.2 GHZ, 1 GB RAM PC.
BTW, I love elog and have it running at work. It is being used extensively. |
I guess it did upload. Here is the other screen capture.
BTW, I received the following message upon submitting my last post:
| Quote: | | "Error sending Email via "mailsend.psi.ch": malformed address: <>" |
|
|
|
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? |
|
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". |
|
|
|
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". |
|
|
|
|
|
ELOG V3.1.5-3fb85fa6 |