There are several ways:

1) Use conditional attributes (see https://midas.psi.ch/elog/config.html#conditional). If you have several standard entries, put the into the option list of a "type" attribute. Then depending on that value, you can pre-populate other attributes/options. This is then not a single-button solution, but a single-click plus one selection from a drop-down list solution which should be pretty close.

2) You can make a bookmark in your browser. Take the URL of the logbook, add "?cmd=New" and then for each attribute you can select a preset value using "&p<attribute>=<value>". So for example on the demo logbook you can use

https://midas.psi.ch/elogs/Linux+Demo/?cmd=New&ptype=Routine&pcategory=General&pauthor=Ellis 

which opens the new entry dialog, and pre-set values for Type, Category and Author. Then you can make several bookmarks for different standard entries.

- Stefan

Hi,

Is it possible to attach multiple files at one time?  Right now I have to attach each individually, click submit, then confirm, then re-select the next file...

This is a pain if one is attaching many files as I often want to do.  It would be nice to be able to select groups of files together using Ctrl and/or Shift, and even to attach a whole directory recursively.

I looked through previous threads but did not find this question asked there.

Thanks,

Eric

This is a well known problem, but unfortunately it's a limitation of HTML and how web browsers work. If it would be easy to attach whole directories to HTML forms, it would be too easy to steal important files from your computer. So the HTML designers decided that each file hast to be confirmed manually, and that's why you have to click so often. There is no way ELOG could bypass this scheme. 

 Hi Stefan,

Okay thanks for letting me know.  That is unfortunate now.

Is there no way also to select multiple files with shift or ctrl?  Is there any usable workaround that you can see?

Thanks,

Eric

If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt."  Also, this effects
the file's displayed "Uploaded" time.  It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"

Note the attachment to this post.

----

Makefile has the line:

# flag for SSL support
USE_SSL    = 1

However setting USE_SSL = 0 does not prevent the openssl libraries from being used.  Same issue with USE_CRYPT.
 You have to comment them out.

Lines 76-85 of Makefile should be replaced with this:

ifdef USE_SSL
ifneq ($(USE_SSL), 0)
CFLAGS += -DHAVE_SSL
LIBS += -lssl
endif
endif

ifdef USE_CRYPT
ifneq ($(USE_CRYPT), 0)
CFLAGS += -DHAVE_CRYPT
LIBS += -lcrypt
endif
endif

Thanks,
amartin

> If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt."  Also, this effects
> the file's displayed "Uploaded" time.  It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"

Arghh! Why did you choose such a filename? This is the ELOG internal file format, which is YYMMDD_HHMMSS_name.ext. 
For internal reasons (mainly for synchronization) the system checks every file name, and if it contains 6 numbers 
followed by a "_" followed by 6 other numbers it thinks it's a valid date/time and uses that. Your time is however 
0.0.0000, that's why it gets converted to some date in 1999. Do you absolutely need this functionality? While I can 
easily remove the interpretation of the date, it would break the synchronization functionality and I would have to 
find some other method to pass the file date/time, which would be quite some work. So if it's not too important for 
you, I would like to keep it as it is.

> Makefile has the line:
> 
> # flag for SSL support
> USE_SSL    = 1
> 
> However setting USE_SSL = 0 does not prevent the openssl libraries from being used.  Same issue with USE_CRYPT.
>  You have to comment them out.
> 
> Lines 76-85 of Makefile should be replaced with this:
> 
> ifdef USE_SSL
> ifneq ($(USE_SSL), 0)
> CFLAGS += -DHAVE_SSL
> LIBS += -lssl
> endif
> endif
> 
> ifdef USE_CRYPT
> ifneq ($(USE_CRYPT), 0)
> CFLAGS += -DHAVE_CRYPT
> LIBS += -lcrypt
> endif
> endif

The original idea was that one outcomments the whole line, like

#USE_SSL = 1

which always worked, but I agree that your solution is more general, so I changed the official Makefile. Thanks for 
that.

> > If I upload the file "000000_000000_file.txt", elog will chop the filename to "file.txt."  Also, this effects
> > the file's displayed "Uploaded" time.  It shows the file as being uploaded on: "Tue Nov 30 00:00:00 1999"
> 
> Arghh! Why did you choose such a filename? This is the ELOG internal file format, which is YYMMDD_HHMMSS_name.ext. 
> For internal reasons (mainly for synchronization) the system checks every file name, and if it contains 6 numbers 
> followed by a "_" followed by 6 other numbers it thinks it's a valid date/time and uses that. Your time is however 
> 0.0.0000, that's why it gets converted to some date in 1999. Do you absolutely need this functionality? While I can 
> easily remove the interpretation of the date, it would break the synchronization functionality and I would have to 
> find some other method to pass the file date/time, which would be quite some work. So if it's not too important for 
> you, I would like to keep it as it is.
> 

Thank you for your response.  

I can certainly use another filename, but I'm curious why elog doesn't convert the filename "000000_000000_file.txt" to
"YYMMDD_HHMMSS_000000_000000_file.txt" when it gets uploaded.  All other files are automatically prepended with this
string.  Manually renaming the file and then editing the elog entry via text editor seems to fix the file.

thanks,
amartin

 I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?