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

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

> 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

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

Well, I also spend like an hour on it.

Hi,

After working many years with previous versions of ELOG, I decided to update to the latest version.
I have installed ELOG version 3.1.0 on a WIndows 2012R2 server with IE 1. The editor is showing up, but everything is greyed out, execpt for some items on the bottom row. (Style, Lettertype...) and after I do load a preset text form with different colors, the page remains white. The tables and text in the form is showing up.

The previous version with the older editor was working great on the same server.

Any suggestions? 

Seriously "IE 1" ??? Javascript was invented in 1995 just before IE 1 came out, I doubt it was supported by IE 1 ;-) I guess it was supposed to read IE 11?

As far as I know the Javascript code of the CKeditor runs on the client, I would not expect the server to be the culprit. I would first try a different browser, then check if the ELOG installation was complete (check for warnings?)

Do you have a Javascript error console in your browser? It should tell you something about what is going wrong.

Cheers, Andreas

Sorry for the typo,of course I meant IE 11.

I do get on "Error on page" error. After switching on the developer tools, I get the following output:

{exception} The value of the property 'dndInit' is null or undefined, not a Function object. I get this error when I trying to make a new entry.

If I use ELOG version 2.9.2-2455 it all works fine, but that version has an different editor.

Marty.

Another thing appeared in the IE message ribbon at the bottom before it states "Error on page" . I do get a message that ELOG is trying to download data from http://latex.codecogs.com/css/equation-embedde.css.....
Well, this server has no internet connection and will not get an internet connection.
Is there a way around this issue? I do not want to use an equation editor

Marty