| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
255
|
Thu Mar 20 21:07:09 2003 |
 | djek | djek@nospam.invalid | Bug report | | | Re: Elog 2.3.3, problems of 2.3.2 solved | > > After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> > as stylesheets, images or passwordfiles.
> >
> > Cannot open file /usr/local/elogdata/logbooks/djeks/password!
>
> If you installed from the RPM, elogd runs under the user "elog". If you have
> installed a previous version under a different user, it might be that elogd
> does not have read or write access to it. A
>
> "chown -R elog.elog /usr/local/elogdata"
>
> might help.
>
It did, a lot, guess I missed that one in the changelog.
Had some trouble with subdir too:
changed it to its full path
restarted elogd
worked
As a test I changed subdir to it's relative path
restarted
It kept working
mmmm, I wonder where that twighlight tune comes from ... |
|
66546
|
Wed Sep 16 23:54:12 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
| Chuck Brost wrote: |
|
We use eLOG with IE. Once we turned on SSL, it is no longer possible to "Export to CSV" and save the output.
The error that we get is:
Internet Explorer was not able to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later.
This is documented on Microsoft's site: http://support.microsoft.com/kb/316431
It is considered a feature with no fix. Basically the browser is honoring a request from the server which is "Pragma: no-cache". Problem can be reproduced in IE versions 6 through 8.
|
I see the same problem with IE. The knowledge base says that one should remove the "no-cache" statement from the header, but that has strange side effects: Assume you export a logbook to a CSV file, and a few days later you export it again, since many things changed. But you browser will in that case not retrieve the new logbook, but read the old CSV file from the cache. But the browser does not tell you this, so you see an old version of the logbok without knowing this, which can be dangerous. So I better leave the "no-cache" in the header. The workaroung is not to click on "Save" on the file download dialog, but on "Open". You see then the CSV data inside the browser and can copy/paste it into a notepad document, then save it. |
|
66549
|
Thu Sep 17 18:31:44 2009 |
| Chuck Brost | Brost_chuck@solarturbines.com | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
| Stefan Ritt wrote: |
|
| Chuck Brost wrote: |
|
We use eLOG with IE. Once we turned on SSL, it is no longer possible to "Export to CSV" and save the output.
The error that we get is:
Internet Explorer was not able to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later.
This is documented on Microsoft's site: http://support.microsoft.com/kb/316431
It is considered a feature with no fix. Basically the browser is honoring a request from the server which is "Pragma: no-cache". Problem can be reproduced in IE versions 6 through 8.
|
I see the same problem with IE. The knowledge base says that one should remove the "no-cache" statement from the header, but that has strange side effects: Assume you export a logbook to a CSV file, and a few days later you export it again, since many things changed. But you browser will in that case not retrieve the new logbook, but read the old CSV file from the cache. But the browser does not tell you this, so you see an old version of the logbok without knowing this, which can be dangerous. So I better leave the "no-cache" in the header. The workaroung is not to click on "Save" on the file download dialog, but on "Open". You see then the CSV data inside the browser and can copy/paste it into a notepad document, then save it.
|
Ah, now this is humorous, when the client first came to me, that was almost exactly the work around I gave him, open it, CTRL-A to highlight it all, CTRL-C to copy it, Move to the excel spreadsheet, CTRL-V to paste it into Excel. Select Data, Text to Columns, and you have an Excel Spreadsheet. They wanted me to post the change in function anyway, though I told Vamsi, "just watch, someone will post the same workaround that I already gave to the clients". So you see why I find it amusing. I would say Great Minds Think Alike, but that would be giving myself a bit too much credit (grin). First, thank you for proving me right on my prediction and if you should happen to make a change that would get around this SSL change in behavior, it would make a group of manufacturing types that are not quite as comfortable with computers as we are, very happy. Please let us know. |
|
66551
|
Thu Sep 17 18:44:52 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
| Chuck Brost wrote: |
|
Ah, now this is humorous, when the client first came to me, that was almost exactly the work around I gave him, open it, CTRL-A to highlight it all, CTRL-C to copy it, Move to the excel spreadsheet, CTRL-V to paste it into Excel. Select Data, Text to Columns, and you have an Excel Spreadsheet. They wanted me to post the change in function anyway, though I told Vamsi, "just watch, someone will post the same workaround that I already gave to the clients". So you see why I find it amusing. I would say Great Minds Think Alike, but that would be giving myself a bit too much credit (grin). First, thank you for proving me right on my prediction and if you should happen to make a change that would get around this SSL change in behavior, it would make a group of manufacturing types that are not quite as comfortable with computers as we are, very happy. Please let us know.
|
I can easily remove the "no-cache" from the header, but as I wrote you, people can then shoot themselves into the foot by getting an old document, and I guess they become even less happy then. So you tell me which way you prefer. |
|
66552
|
Thu Sep 17 20:46:51 2009 |
| Chuck Brost | Brost_chuck@solarturbines.com | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
| Stefan Ritt wrote: |
|
| Chuck Brost wrote: |
|
Ah, now this is humorous, when the client first came to me, that was almost exactly the work around I gave him, open it, CTRL-A to highlight it all, CTRL-C to copy it, Move to the excel spreadsheet, CTRL-V to paste it into Excel. Select Data, Text to Columns, and you have an Excel Spreadsheet. They wanted me to post the change in function anyway, though I told Vamsi, "just watch, someone will post the same workaround that I already gave to the clients". So you see why I find it amusing. I would say Great Minds Think Alike, but that would be giving myself a bit too much credit (grin). First, thank you for proving me right on my prediction and if you should happen to make a change that would get around this SSL change in behavior, it would make a group of manufacturing types that are not quite as comfortable with computers as we are, very happy. Please let us know.
|
I can easily remove the "no-cache" from the header, but as I wrote you, people can then shoot themselves into the foot by getting an old document, and I guess they become even less happy then. So you tell me which way you prefer.
|
Trust me, I don't want them getting old data either.. that would be a nightmare..
of course, the little voice at the back of my head (note, not IN the back of my head) has offered up this tidbit for you to consider.
Stefan, would it be possible to make the following change so that the document is not cached and at the same time it is possible to save it.
The change would entail replacing the "Pragma: no-cache" directive with an "Expires: " <HTTP-date> where <HTTP-date> is the same as Date header value. Please see section 14.21 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
Hopefully there are no other side effects to this change.
|
|
66582
|
Sun Nov 8 23:25:25 2009 |
| soren poulsen | soren.poulsen@cern.ch | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
| Chuck Brost wrote: |
|
| Stefan Ritt wrote: |
|
| Chuck Brost wrote: |
|
Ah, now this is humorous, when the client first came to me, that was almost exactly the work around I gave him, open it, CTRL-A to highlight it all, CTRL-C to copy it, Move to the excel spreadsheet, CTRL-V to paste it into Excel. Select Data, Text to Columns, and you have an Excel Spreadsheet. They wanted me to post the change in function anyway, though I told Vamsi, "just watch, someone will post the same workaround that I already gave to the clients". So you see why I find it amusing. I would say Great Minds Think Alike, but that would be giving myself a bit too much credit (grin). First, thank you for proving me right on my prediction and if you should happen to make a change that would get around this SSL change in behavior, it would make a group of manufacturing types that are not quite as comfortable with computers as we are, very happy. Please let us know.
|
I can easily remove the "no-cache" from the header, but as I wrote you, people can then shoot themselves into the foot by getting an old document, and I guess they become even less happy then. So you tell me which way you prefer.
|
Trust me, I don't want them getting old data either.. that would be a nightmare..
of course, the little voice at the back of my head (note, not IN the back of my head) has offered up this tidbit for you to consider.
Stefan, would it be possible to make the following change so that the document is not cached and at the same time it is possible to save it.
The change would entail replacing the "Pragma: no-cache" directive with an "Expires: " <HTTP-date> where <HTTP-date> is the same as Date header value. Please see section 14.21 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
Hopefully there are no other side effects to this change.
|
You can also try to use a different browser.
Soren |
|
66593
|
Tue Nov 10 14:56:07 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.6-2236 | Re: Elog & SSL Export to CSV , Problem |
| Chuck Brost wrote: |
|
Stefan, would it be possible to make the following change so that the document is not cached and at the same time it is possible to save it.
The change would entail replacing the "Pragma: no-cache" directive with an "Expires: " <HTTP-date> where <HTTP-date> is the same as Date header value. Please see section 14.21 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
Hopefully there are no other side effects to this change.
|
ok, so I removed the "Pragma: no-cache". With IE it looks fine now, and if I repeat it two times it always gets is from elog and not from the cache due to the "Expires:" statement. The "no-cache" came from old days when some browsers did not yet support the "Expires" tag. I hope that this is better now, so let's see when we get the first complaints. The modification is in SVN revision 2265. |
|
69037
|
Tue Oct 15 10:37:29 2019 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.4 | Re: Edit of multiple posts | I use editing of multiple entries frequently and it works fine for me.
To understand your problem I would suggest that you try a minimal configuration. If you have a test logbook with just one or two fields and it still does not work, then post the config here that people can reproduce your problem - and hopefully find a fix.
Cheers, Andreas
| Finn Junker wrote: |
|
Hello Elog Forum
There is i ELOG the function to edit multiple posts eg. to change the staus from "ongoing" to "finished" -> in danish translation "igangværende" and "afsluttet", see the attached pictures.
When I select multiple post and want to edit them to status "afsluttet" i get the "udklip_2.jpg" entry form and change only the status to "afsluttet" (Finished)
The result is a error informing that the attribut "gem oprindelige værdier" does not exist. As a test i changed the text in the translation file from "Keep origianl values = gem oprindelige værdier" to "Keep origianl values = Keep origianl values" but the result is the same error: Attribut Keep original values does not exist.
Is there a solution to this or is or is mutiple editing of post not allowed?
Kind Regards Finn
|
|
|