> Apparently it was less work to fix than to isolate it ;-)

Well, I also spend like an hour on it.

> Thanks for the "boiling-down" of your config file. That helped me to reproduce the error quickly. It only occurs if you have a date/time attribute which is hidden as a conditional attribute. This is a unusual combination, that's why I haven't seen that bug before. Actually some 
> JavaScript code checks the validity of the date attribute, but since it is conditionally not there, the JavaScript code crashes, which triggers the dialog box you see. It's now fixed in the repository.
> 
> /Stefan
> 

Thank you Stefan!
That works nicely now.
Apparently it was less work to fix than to isolate it ;-)

Andreas

Thanks for the "boiling-down" of your config file. That helped me to reproduce the error quickly. It only occurs if you have a date/time attribute which is hidden as a conditional attribute. This is a unusual combination, that's why I haven't seen that bug before. Actually some 
JavaScript code checks the validity of the date attribute, but since it is conditionally not there, the JavaScript code crashes, which triggers the dialog box you see. It's now fixed in the repository.

/Stefan


> I have a little problem with elogd 3.1.0. The problem persists up to the latest ELOG version, even in the
> development branch (V3.1.0-8196b81):
> 
> When I want to "Submit" a new entry, I get a javascript pop-up that asks me:
> 
> _This page is asking you to confirm that you want to leave - data you have entered may not be saved._
> 
> with the options:
> "Stay on page" or "Leave page".
> 
> The entry is properly submitted if I agree to "Leave page".
> But it is very confusing for my users: they are afraid to loose their entry text.
> 
> This problem only shows for some specific logbook configurations.
> Below is a minimal logbook configuration that shows this problem:
> if you select "entry = short", the pop-up is shown;
> if you select "entry = long", the pop-up is not shown, the entry is created immediately.
> 
> Attributes = entry, when
> Options entry = short{1}, long
> Type when = datetime
> {1} Show Attributes Edit = entry
> 
> 
> (PS: it took me several hours to boil down my 120 line configuration into four lines :-) )

I have a little problem with elogd 3.1.0. The problem persists up to the latest ELOG version, even in the
development branch (V3.1.0-8196b81):

When I want to "Submit" a new entry, I get a javascript pop-up that asks me:

_This page is asking you to confirm that you want to leave - data you have entered may not be saved._

with the options:
"Stay on page" or "Leave page".

The entry is properly submitted if I agree to "Leave page".
But it is very confusing for my users: they are afraid to loose their entry text.

This problem only shows for some specific logbook configurations.
Below is a minimal logbook configuration that shows this problem:
if you select "entry = short", the pop-up is shown;
if you select "entry = long", the pop-up is not shown, the entry is created immediately.

Attributes = entry, when
Options entry = short{1}, long
Type when = datetime
{1} Show Attributes Edit = entry


(PS: it took me several hours to boil down my 120 line configuration into four lines :-) )

Hi Edmund,

Stefan already supplied a fix, but you could as well use a workaround: provide an empty file as text. The following works for Linux:

elog -h elog-server-adress -l EO -a Fill=111 -m /dev/null

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

Hi Francois. 
if those worker lists do change rather infrequently, then I would have an idea how to do it:

You could have an application that updates the Options or MOptions lists in the elogd.cfg file at midnight, 
and in case they actually did change the application restarts the elogd process afterwards.

I use such a mechanism to update my user list from our companies LDAP service every second Monday of a month at midnight.
This avoids misspelled user names or wrong email addresses and takes care that all employees (~2000) can log-in to our ELOG.
The passwords are handled anyway by kerberos authentication.

But I admit that it would be a cool feature to have "includes" in the configuration file for dynamic data sources. 
Shell scripts of course are useless for "Option" definitions: they would only be executed at start-up anyway,
and that can be accomplished as well by the above mentioned automatic changes to the config file.

Kind Regards
Andreas

The "command does not respond" means that the program starts reading in the main message text from the console. You can type several lines of text, and finish it off by hitting Ctrl-D (Ctrl-Z under Windows).

I see your point of having empty texts. Indeed the "" on the command line does not work presently, so you have to add a space as a workaround. I modified the elog code (committeed to bitbucket repository) to accept "" as empty text to suit your needs.

/Stefan

Hey,

I want to submit an entry to elog remotley using the "elog" command. For example:

elog -h elog-server-adress -l EO -a Fill=111

But this does not generate a new entry. Instead the terminal jumps to an empty new line and the command does not respond to any further inputs anymore (CTRL+C to get out). I have to add a message:

elog -h elog-server-adress -l EO -a Fill=111 "test"

also using an empty string does not work:

elog -h elog-server-adress -l EO -a Fill=111 ""

I could add a whitespace as a work-around, but I'm not sure if this is a bug or a feature.

To put this in some context: I want to create entries for certain measurements automatically, where all relevant parameters are already attribute fields. In the usual case the actual message will be empty but might be used if the operator wants to add a note after the meausrement has been done.