| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66412
|
Thu Jun 25 09:07:51 2009 |
 | Michael Husbyn | michael.husbyn@gmail.com | Bug report | Windows | 2.7.6 | Re: (my) Firefox breaks Elog with this config file |
| Stefan Ritt wrote: |
| Michael Husbyn wrote: |
| Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn |
This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog. |
Sure I will try, but I cannot find the version you are talking about in the download section. Should I find it there or any other place?
Thanks for quick feedback |
|
66413
|
Thu Jun 25 09:26:00 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.6 | Re: (my) Firefox breaks Elog with this config file |
| Michael Husbyn wrote: |
|
| Stefan Ritt wrote: |
|
| Michael Husbyn wrote: |
| Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn |
This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog.
|
Sure I will try, but I cannot find the version you are talking about in the download section. Should I find it there or any other place? Thanks for quick feedback |
It's here. |
|
66415
|
Thu Jun 25 10:21:10 2009 |
| Michael Husbyn | michael.husbyn@gmail.com | Bug report | Windows | 2.7.6 | Re: (my) Firefox breaks Elog with this config file |
| Stefan Ritt wrote: |
| Michael Husbyn wrote: |
|
| Stefan Ritt wrote: |
|
| Michael Husbyn wrote: |
| Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn |
This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog.
|
Sure I will try, but I cannot find the version you are talking about in the download section. Should I find it there or any other place? Thanks for quick feedback |
It's here. |
Looks more stable, but it still quits. Sometimes just entering the logbook, sometimes when I hit the config button.
==== Return ================================
<549 bytes of favicon.ico>
TCP connection broken
GET /nor/elog.rdf HTTP/1.1
Host: XXSERVERNAMEHEREXX:8091
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.11) Gecko/2
009060215 Firefox/3.0.11 (.NET CLR 3.5.30729)
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-gb,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 300
Connection: keep-alive
Cookie: elmode=Summary
and just quits
Strange |
|
66416
|
Thu Jun 25 10:51:12 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.6 | Re: (my) Firefox breaks Elog with this config file |
| Michael Husbyn wrote: |
|
| Stefan Ritt wrote: |
|
| Michael Husbyn wrote: |
|
| Stefan Ritt wrote: |
|
| Michael Husbyn wrote: |
| Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn |
This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog.
|
Sure I will try, but I cannot find the version you are talking about in the download section. Should I find it there or any other place? Thanks for quick feedback |
It's here.
|
Looks more stable, but it still quits. Sometimes just entering the logbook, sometimes when I hit the config button. ==== Return ================================ <549 bytes of favicon.ico> TCP connection broken GET /nor/elog.rdf HTTP/1.1 Host: XXSERVERNAMEHEREXX:8091 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.11) Gecko/2 009060215 Firefox/3.0.11 (.NET CLR 3.5.30729) Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-gb,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Cookie: elmode=Summary and just quits Strange |
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. |
|
66417
|
Thu Jun 25 11:04:53 2009 |
| Michael Husbyn | michael.husbyn@gmail.com | Bug report | Windows | 2.7.6 | Re: (my) Firefox breaks Elog with this config file |
| Stefan Ritt wrote: |
| Michael Husbyn wrote: |
|
| Stefan Ritt wrote: |
|
| Michael Husbyn wrote: |
|
| Stefan Ritt wrote: |
|
| Michael Husbyn wrote: |
| Hi, Did a fresh install on a Windows 2003 server (and tried it on my personal computer) After startup I can click on Norway/nor, and then the server just stops responding. I see in the log nothing, the last line: Received unknown cooke "style" Then it stops responding and after a few seconds I see the dos window returns to commandline prompt. Probably a very bad config file. On Windows XP it informs we of Dr Watson, memory could not be read message. Using Firefox 3.0.11 But if I use IE 7, no problem at all.. Any suggestion? Best regards Michael Husbyn |
This must be related to the unknown cookie "style". There was some work recently on elog to make it robust against unknonw cookies. The latest modification was on version 2192, and you probably have an older version. I made a release elog276-2.exe for you. Try it and let me know. You can also just delete your cookies in Firefor and it should be fine, but it's better not being able to crash elog.
|
Sure I will try, but I cannot find the version you are talking about in the download section. Should I find it there or any other place? Thanks for quick feedback |
It's here.
|
Looks more stable, but it still quits. Sometimes just entering the logbook, sometimes when I hit the config button. ==== Return ================================ <549 bytes of favicon.ico> TCP connection broken GET /nor/elog.rdf HTTP/1.1 Host: XXSERVERNAMEHEREXX:8091 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.11) Gecko/2 009060215 Firefox/3.0.11 (.NET CLR 3.5.30729) Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-gb,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Connection: keep-alive Cookie: elmode=Summary and just quits Strange |
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. |
Looks like problem is fixed :)
Thanks for your help |
|
66428
|
Wed Jul 1 17:00:30 2009 |
 | Richard Stamper | r.stamper@rl.ac.uk | Bug report | Windows | 2.7.6-2227 | Checks on datetime seconds field generate warning in IE7 | 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 |
| Attachment 1: Javascript_warning.jpg
|
|
|
66429
|
Thu Jul 2 08:36:57 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.6-2227 | Re: Checks on datetime seconds field generate warning in IE7 |
| Richard Stamper wrote: |
|
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
|
This is absolutely correct, even the right fix. I put that into the distribution. Thanks a lot. |
|
66435
|
Mon Jul 6 17:20:36 2009 |
 | Mike | mike@raghuexim.com | Bug report | Linux | 2.7.6-2207 | Page Expired, Duplicate Entries & Thumbnail Woes? | 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?
Regards,
Mike |
|