Re: elog client cmd line submission of attributes with spaces., posted by Andreas Luedeke on Sat Aug 20 12:17:10 2016
|
If the "Start Time" attribute is of the type "datetime", then you cannot assign a date string to it.
Instead you'll have to assign the seconds of the epoch.
Try assigning a "0", that should be the 1st of January 1970.
|
|
Re: elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Thu Aug 25 18:18:57 2016
|
Thanks for the reply. You're correct that the "Start Time" attribute is a datetime field. I tried your suggestion and placed "0" for that field but it still
returns the same error: Error: Missing required attribute "Start Time"
I tested after commenting out the required attribute line and the command was accepted. However, the datetime field does not display a valid date/time |
Re: elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Thu Aug 25 18:32:13 2016
|
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.
|
|
Re: elog client cmd line submission of attributes with spaces., posted by Rudy Taraschi on Thu Aug 25 18:45:48 2016
|
[quote="Darren Hollinrake"]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.[/quote]
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 |
|
Re: elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Thu Aug 25 19:04:11 2016
|
Agreed, I just wanted to clarify for anyone else though that the issue seems to be centered on my "Start Time" attribute which is a datetime field. All
the other attributes (with spaces) allowed submission of the entry so long as the "Start Time" attribute wasn't set to required. That appears to be the
one with the actual issue. Giving a valid epoch time when that field isn't required allows the field to be populated correctly. However, if the "Start |
Gmail email smtp settings, posted by Devrim Esenturk on Mon Jan 2 16:32:18 2017
|
Hi all
I am trying to send email via Gmail smtp with no success. Elog uses port 25 which is not allowed. I need to use 587 or 465 ports to send mail.
How can I change the port? |
|
Re: subject line bug on resumit elog entries as new?, posted by David Pilgram on Tue Jun 9 16:17:06 2015
|
Hi Stefan,
I see that you've updated the elog running this forum today, 5 versions after you reported fixing the "A new elog entry has been entered"
and "An old elog entry has been updated" issue. But the emails coming out are still all of the "An old elog entry...", rather |
|
Re: subject line bug on resumit elog entries as new?, posted by Stefan Ritt on Tue Jun 9 16:46:48 2015
|
Any better now?
David
Pilgram wrote:
Hi Stefan, |