| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68341
|
Thu Jun 23 15:57:34 2016 |
 | Rudy Taraschi | rudy.taraschi@L-3com.com | Question | Linux | Windows | Mac OSX | All | Other | 3.1.1 | Hide blank fields when displaying logbook entry |
Hi, I have a logbook with attributes Tool1, Tool2, and Tool3. When viewing a completed entry, what I want to do is see Tool2 or Tool3 only if they are non-zero, and don't want to see them if blank. Basically, a "Hide if blank" option. I couldn't find it - if it doesn't exist, are there any tricks to simulate it? |
|
68386
|
Fri Aug 19 22:43:21 2016 |
 | Rudy Taraschi | rudy.taraschi@L-3com.com | Question | Windows | V3.1.1-3f311c5 | Re: elog client cmd line submission of attributes with spaces. |
| Try commenting out the Required Attributes line in your elogd.cfg file before submitting. I think it's a bug but this work-around gets around it. |
|
68406
|
Thu Aug 25 18:45:48 2016 |
| Rudy Taraschi | rudy.taraschi@L-3com.com | Question | Windows | V3.1.1-3f311c5 | Re: elog client cmd line submission of attributes with spaces. |
| Darren Hollinrake wrote: | | Thanks for the response. You are indeed correct that the issue disappears when I comment out my required attributes line. If I just remove my "Start Time" attribute, all the other attributes work as well. |
I used to just comment out that one field in Required Attributes as well, but it was a pain to edit the CFG file, so I took the lazy approach and just commented out the whole line - less typing  |
|
68913
|
Tue Mar 19 23:24:48 2019 |
| Ross Gibson | ross.gibson@newcastle.edu.auSince updating to ver | Question | Windows | 3.1.4 | HTML editor not working after updating to V3.1.4 |
Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify? |
|
68915
|
Wed Mar 20 06:50:57 2019 |
| Ross Gibson | ross.gibson@newcastle.edu.au | Question | Windows | 3.1.4 | Re: HTML editor not working after updating to V3.1.4 |
Thanks Stefan. Tried these without success. I tried opening in another browser and it works fine in Firefox or Internet Explorer - the problem only appears in Microsoft Edge. Perhaps its an issue with a Microsoft update (corporate rollout) to Edge and just a coincidence that I noticed it after updating Elog.
| Stefan Ritt wrote: | Have you cleared your browser cache? There might be some old JavaScript stored there. If that does not help, remove elog and reinstall it to make sure to have the correct libraries on the server (first back up you logbooks, then restore them afterwards).
Stefan
| Ross Gibson wrote: | Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify? |
|
|
|
67393
|
Mon Dec 10 16:28:27 2012 |
 | Ron Beekman | ron.beekman@gmail.com | Bug report | Windows | 2.7.5-2130 | Error 554 MailTransferAgentServer ESMTP not accepting messages |
Hello,
We use ELOG for many years and enjoy it's functions every day!
Lately, we see errors whenever we add an entry in elog: 554 MailTransferAgentServer ESMTP not accepting messages
We see this from various ELOG servers. Other (non ELOG) servers using the same MailTransferAgentServer do not heve this error.
We are able to send mail messages from the ELOG machines manually via TELNET. So, from a functional point of view, all works well.
We had this error in the past and found out that the cause of this error lies in (network) time-outs.
Questions:
1) Has anyone seen this error before?
2) Is it possible to increase the timeout value used by ELOG?
3) Are the emails that could not be sent stored in a queue/resent later or are they lost?
4) is there a fix?
Any replies are highly appreciated!
T I A !
|
|
67395
|
Tue Dec 11 09:43:33 2012 |
| Ron Beekman | ron.beekman@gmail.com | Bug report | Windows | 2.7.5-2130 | Re: Error 554 MailTransferAgentServer ESMTP not accepting messages |
> Just my 2 cent: did you try to reproduce the problem with the latest ELOG version 2.9.2?
Hi Andreas,
Thank you very much for your reply. Thsi problem occurs also with the latest ELOG version 2.9.2
It would be nice if the timeout value(s) can be edited via the elogd.cfg file. Maybe this can be added in a new
version.
Best regards,
Ron |
|
67397
|
Tue Dec 11 10:17:11 2012 |
| Ron Beekman | ron.beekman@gmail.com | Bug report | Windows | 2.7.5-2130 | Re: Error 554 MailTransferAgentServer ESMTP not accepting messages |
| Stefan Ritt wrote: |
|
| Ron Beekman wrote: |
|
Hello,
We use ELOG for many years and enjoy it's functions every day!
Lately, we see errors whenever we add an entry in elog: 554 MailTransferAgentServer ESMTP not accepting messages
We see this from various ELOG servers. Other (non ELOG) servers using the same MailTransferAgentServer do not heve this error.
We are able to send mail messages from the ELOG machines manually via TELNET. So, from a functional point of view, all works well.
We had this error in the past and found out that the cause of this error lies in (network) time-outs.
Questions:
1) Has anyone seen this error before?
2) Is it possible to increase the timeout value used by ELOG?
3) Are the emails that could not be sent stored in a queue/resent later or are they lost?
4) is there a fix?
Any replies are highly appreciated!
T I A !
|
Could you run elogd interactively with the "-v" flag to log the communication between elogd and the ESMTP server and send me the traffic log?
|
Hello Stefan,
Thanks you for entering this thread !
Fortunately, we were able to solve the problem. A reboot of the DNS server used by the MTA (Mail Transfer Agent Server) to check the from and to address did the trick.
This server now responds within the timeout period in ELOG.
It still would be handy if you could add a parameter to the config file that allows us to fiddle with the timeout value. The DNS server used by the MTA has to deal with heavy load.
Best regards,
Ron
|