Ah, the GET /nor/elog.rdf gave me somt hint: Your Firefox browser checks the RSS feed of elog regularly. If the logbook is empty, the routing producing the elog.rdf file went into some kind of infinite loop, but this only happens on an empty logbook. If fixed this and updated the 276-2 file just now, so try again.

When adding a log entry containing a datetime field using the IE7 browser a Javascript warning is displayed - see the attachment.  This is due to a change in the naming of the "seconds" field of a datetime entry (made in version 2143) not being propagated to the code that generates the Javascript that checks the supplied values.

Suggested patch follows.

Change "s%d" to "c%d" in lines 9675 and 9678.

Showing lines 9675-9680 below, change from:

               rsprintf("  if (document.form1.s%d.value == \"\") {\n", i);
               sprintf(str, loc("Please enter second for attribute '%s'"), attr_list[i]);
               rsprintf("    alert(\"%s\");\n", str);
               rsprintf("    document.form1.s%d.focus();\n", i);
               rsprintf("    return false;\n");
               rsprintf("  }\n");

to:

               rsprintf("  if (document.form1.c%d.value == \"\") {\n", i);
               sprintf(str, loc("Please enter second for attribute '%s'"), attr_list[i]);
               rsprintf("    alert(\"%s\");\n", str);
               rsprintf("    document.form1.c%d.focus();\n", i);
               rsprintf("    return false;\n");
               rsprintf("  }\n");

Regards,

Richard Stamper

Have a few issues here. The big one is that I have some users of our elog books
that are in India, while the server is in USA. When they click on thumbnail images
then press their browser back-button they get a page expired message and are
unable to see what they were looking at before unless they go back to the main
page. Is this an elog problem or something with Apache?

Also when these users in India write messages sometimes we end up with
duplicate messages seconds apart. I'm not sure if they are pressing the submit
button repeatedly or pressing their browser back button. I've suggested they
try not to do that.

Last issue, is there a way to make thumbnail images open in a new window by default rather then the same window? This would help fix the first issue at least. Is there some setting to fix the page expiration/time-out issues?

That's strange. Normal pages are set to "pre-expire" (expiration date 1983...) which forces the browser to always load them from the server. This is necessary since someone else could have modified that page and you would look at an old page in your browser's cache. But using this, I never saw a "page expired" message. The browser simply reloads the page. Maybe if the internet connection got lost in between and the browser cannot load the page from the server, you have a problem. Attached pictures have a expiration date of +1 day. So even if you span different time zones, that should be fine. Can they try to access https://midas.psi.ch/elogs/Linux+Demo/14 and see if they get the same problem there? This is my demo setup and resides in Switzerland.

The only way to get two entries is if you submit your entries twice. The same problem exists on some credit card payment sites, which explicitly state "please be patient, don't press submit twice, don't press back". The same applies for elog. 

No, this is not implemented right now. But if nothing else helps, I can add a new option.

 Stefan,

Thanks for writing back so fast. I'll have the folks in India check that link and see if the problem exists there.
I couldn't duplicate the problem here on my end. I'm beginning to think that it's a connection problem. They
tell me that the elog site (our site) is slow for them. It's only capable of 118kb/sec which, coupled with
the distance from USA to India might make things slow. In the USA I found the site to be usable and not that
slow. I'll let you know what they say about the test link.

Mike

I talked to my associate from India. He tried that link you provided and claims that even on your

site the "page expired" message occurs. Weird eh? Any ideas?