elog client cmd line submission of attributes with spaces., posted by Darren Hollinrake on Fri Aug 19 19:39:50 2016
|
I was setting of a local test copy of my logbooks on my Windows 7 PC to begin testing automation of submissions without spamming the live logbooks. While
trying to make entries from the command line I get an error that I am missing a required attribute. I have multiple attributes that have spaces in them
an the verbose output indicates that the space in the name is being changed to an underscore. Is this the expected behavior or a bug when submitting to |
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 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 |
Re: notification error services in CentOS 6.5, posted by Darren Hollinrake on Sun Sep 18 03:31:42 2016 
|
The quick fix I found was to uncomment line 10 in the init.d file. (This was tested on a CentOS 6.8 AWS instance.)
. /etc/rc.d/init.d/functions
This will allow the status command to function properly. |
|
Change / List Change doen't work anymore?, posted by Holger Mundhahs on Thu Sep 17 15:52:36 2009
|
Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my |
|
List view for CHANGE attributes, posted by Holger Mundhahs on Wed Feb 22 13:49:03 2006
|
Hello @all,
I've tried to implement an attribute with Change. The detail view works well,
but in the list view the field is empty (see screen shots). Can somebody help me?
|
|
Re: List view for CHANGE attributes, posted by Holger Mundhahs on Wed Feb 22 15:47:45 2006
|
Hello Mr. Ritt,
6 min 5 sek to answer - great. :D :D
|