> How do I preset the reply date to an empty box(es)?
> 
> In 2.5.x it worked as
> 
> Preset on reply Plan Date = ""
> 
> gave me an empty date, which is what I wanted. Now in 2.6.3 I get some date in there (...1969) and have to
> manually set it to empty again ?
> 
> Thanks

I fixed that in SVN revision 1777 again, so it will be included in the next release.

> Hi Stefan,
> 
> I'm having a problem with 'Preset Text' now behaving differently in the latest release (2.9.1)?
> My config file for example has always had: 'Preset Text = This is a test.', previously 'This is a test' was put
> verbatim into the text area, now it seems to think whatever follows 'Preset Text =' is always a file and I end
> up with 'File <i> This is a test. <i> cannot be found'?
> 
> I did notice a 'Print warning if "preset text" file cannot be found' line in the latest release notes, does this
> now mean wherever I have used the method above I will now need to make a text file to match?
> 
> I'm using them embedded in conditional attributes if that makes any difference?
> 
> Thanks for your help.

Thanks for reporting this bug. I fixed it in SVN revision 2447.

I always chose the safe solution: I provide the full path to the document. For example (under Linux):

Preset text = /usr/local/elog/logbooks/inc/test.txt

Well, I only know that the following config file works fine for me on Linux:

[test]
Attributes = xx
Preset text = /tmp/xx

with the file /tmp/xx containing "test: ignore". When opening a new entry, then the text "test: ignore" is written in the editors text area.

I'm using Version 2.9.2

My suggestion: download the latest Windows Version and try again.

> Title says all :)
> 
> Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
> 
> Thanks :)

Quick and simple answer: No.

But please explain me what your case is. Maybe this can be done differently.

> > Title says all :)
> > 
> > Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
> > 
> > Thanks :)
> 
> Quick and simple answer: No.
> 
> But please explain me what your case is. Maybe this can be done differently.

That's clear :)

So basically, I have a list of 5-10 workers. I'll have to choose one for each entry I make into the logbook. But these workers will change from time to time 
(students) and I don't want the staff to manipulate the config file manually..("Extendable options" is not an option as I will get to many "Darth Vader" entry for 
sure..)

I asked if I could populate that option box from another logbook attribute and Andreas told me only possible via external scripts. 
https://midas.psi.ch/elogs/Forum/67877

I investigate a little but I found that :

a) I couldn't make shell command to execute while elogd was running as a service (I'm running windows and $shell was just returning weird stuff ); shell script was 
working only when I launch elogd.exe from a command line:

-elogd as a Service running the following : Subst Infographiste = $shell(dir c:\) 
will return : Shell execution not enabled via -x flag

-modifying the Windows Service to add "-X" and running the following :Subst Infographiste = $shell(dir c:\) 
will return : a empty attribute

-running elogd "-x" from a command line, the following : Subst Infographiste = $shell(dir c:\) 
will return : the dir result..

(I also tried to change under witch user the service was running..)

b) I just couldn't figure how to build that script....

But that would be so nice ! I can see so many situations where I could use such a scenario (loading options from another logbook or from a txt/csv file 
somewhere...)

Thanks,

:)