ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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. |
66414
|
Thu Jun 25 10:09:18 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | All | 2.7.6-2191 | Re: Auto-increment substitutions broken with records for multiple days | > An alternative patch:
>
> /* if date part matches */
> if (strlen(attrib[index]) > 0 && strncmp(attrib[index], retstr, loc) == 0)
> /* retrieve old index */
> if (atoi(attrib[index] + loc) > old_index)
> old_index = atoi(attrib[index] + loc);
>
> does not make this assumption and also appears to work OK when I test it.
Yes, this is the right one, it searches all entries to have the same date than the current one, and then looks for the
largest index which will be stored in old_index and later incremented by one. I committed your patch to the
repository. Thanks a lot. |
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 |
66418
|
Thu Jun 25 12:30:17 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.6 | Re: Denial of access after failed import using invalid attributes |
soren poulsen wrote: |
Hi,
A user tried to import a CSV file, which caused e-log to add a field called "date" to the list of attributes (and then crash). This caused the log-book to be blocked until someone (guess who) would go edit the elogd.cfg file and then trigger a reload.
1. suggestion : E-log should not crash in this case
2. suggestion: E-log should not allow invalid attributes to be added via CSV Import, which causes the log-book to be blocked.
For the time being, I will just "Deny import" (by the way, the doc says it is "Deny CSV import", but I think the syntax is "Deny import". Not really important.
I think this should be quite easy to reproduce.
Thanks a lot
Soren
|
If the CSV file contains a "date" column, elogd tries to interprete the date to the internal format. Now a date can be written in a huge number of variations, and I'm sure I did not cover all. So please send me your CSV file and I will fix the crash. |
66419
|
Thu Jun 25 15:02:55 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.7.6 | Re: Formatting list page data |
Steve Williamson wrote: |
Thanks for a great piece of software - it does so much and is (mostly) so simple to use. However, I do have a suggestion that (for me, at least) would make it even better -
I use elog for a variety of logging tasks but find that, because I want to see as complete a summary as possible, the list page can get very crowded with longer fields wrapping over several lines. I would like to have more control over the way attributes are displayed here. Specifically, being able to truncate data (e.g. to show just the first n characters of a description), being able to select a substring (e.g. displaying characters before the '@' character to remove the domain from an email address or displaying characters after the space to remove the day from a date in ddd dd/mm/yy format) and being able to concatenate fields (e.g. to show a reference in a single cell as "Incident 1234" by joining call type and call reference attributes).
regards
Steve
|
Something along these lines is however not implemented (and hard to do). The only chance you have is to export your data into a spreadsheet and do the reformatting/report generation there. |
66420
|
Thu Jun 25 15:37:14 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.6 | Re: Export and save problem with IE7 |
soren poulsen wrote: |
Hi
Would it be possible to use the "Export to:" function with IE7 on the Forum logbook, and save the logbook.
I can do the export but saving the file with IE7 does not work. Saving the file with Firefox, Chrome, Safari works.
This makes me think that E-log is good and IE7 is bad ?
Soren
|
Right
It seems to be a well known probmel with IE: http://classicasp.aspfaq.com/files/directories-fso/how-do-i-send-the-correct-filename-with-binarywrite.html
So I tried all variations there, but none of them worked. The interesting thing is that it works if you use it locally, but not with the forum (which has an additional "/elogs" in the URL).
|
|