Not really...
The thing is I have to let some users the capacity of changing the content of that option list.. I was hoping there could be a different way for 
them then to edit the cfg file...

That why I came up at first ask if it could be possible to load an Option list from the content of another logbook... that way I could have made 
up some sort of "worker" logbook that would have feed the main logbook Attribute "workers" options list.


> Forget scripting under Windows, this is painful and not really working. Wrong OS for that.
> 
> But have you considered conditional attributes? With this you can load different option lists straight from the elogd.cf file. Use something 
like this:
> 
> Attributes ..., List, Person
> 
> Options List = List A{1}, List B{2}
> {1} Options Person = Person a1, Person a2, ...
> {2} Options Person = Person b1, Person b2, ...
> 
> So if you choose either "List A" or "List B", you get a different set of persons. Is it that what you want?
> 
> /Stefan
> 
> 
> > 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,
> > 
> > :)

Forget scripting under Windows, this is painful and not really working. Wrong OS for that.

But have you considered conditional attributes? With this you can load different option lists straight from the elogd.cf file. Use something like this:

Attributes ..., List, Person

Options List = List A{1}, List B{2}
{1} Options Person = Person a1, Person a2, ...
{2} Options Person = Person b1, Person b2, ...

So if you choose either "List A" or "List B", you get a different set of persons. Is it that what you want?

/Stefan


> 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,
> 
> :)

> > 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,

:)

> 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 :)

Greetings,

  Running elog 3.1.0 on CentOS 6.6.  When I try to access a nonexistent file, elog reveals a path in the 404 page.  For example:

Not Found

The requested file /usr/local/elog/themes/default/blortblortblort7854.htm was not found on this server

Hi Stefan,

When we use Webserver authentication, we have the correct username already in the variable http_user.

The old way of copying this http_user to "user" is wrong since we don't use the size of http_user.

Instead, just encode the http_user variable directly.

See attached patch against git HEAD.

Christof

Hi Stefan,

here is a draft of how you could describe the webserver authentication in your docs.

T/Christof