ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66719
|
Sat Feb 20 14:57:27 2010 |
| tom | tnielsen91@gmail.com | Question | Linux | latest | Log Thread Close Automatically |
If you have a logbook and you create a new entry, is it possible to put a time limit on that new entry so that edits/replies are only valid for certain amount of time. I am looking for a way that would allow me to have a user start a new message, but after 8 hours, that message becomes locked and no one can edit or add to the message. This is for some shift work and we do not want users to go back after their shift and edit the messages. |
66718
|
Fri Feb 19 14:12:41 2010 |
| Tony Albers | tony.albers@gmail.com | Question | Linux | 2.6.3 | Re: Remove "demo" logbook.. |
Stefan Ritt wrote: |
Tony Albers wrote: |
Tony Albers wrote: |
Hi,
Is it possible to remove the "demo" logbook?
If I rename the section in elogd.cfg , it complains:
Error: logbook "demo" not defined in elog.conf Please use your browser's back button to go back
But there are other logbooks it can show instead. Is the "demo" logbook hardcoded in elogd?
/tony
|
I now upgraded to ver. 2.7.8, but I still cannot remove or disable the demo logbook.
|
The logbook name is in the URL of your browser. In the demo installation, there is a link in the start menu pointing to http://localhost:8080/demo. If you rename your logbook to something else, you have to change the URL accordingly. The simplest thing is to point it to http://localhost:8080, then you will be presented with a list of available logbooks.
|
Thanks Stefan, I managed to get it to work now. |
66717
|
Fri Feb 19 13:10:50 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.3 | Re: Remove "demo" logbook.. |
Tony Albers wrote: |
Tony Albers wrote: |
Hi,
Is it possible to remove the "demo" logbook?
If I rename the section in elogd.cfg , it complains:
Error: logbook "demo" not defined in elog.conf Please use your browser's back button to go back
But there are other logbooks it can show instead. Is the "demo" logbook hardcoded in elogd?
/tony
|
I now upgraded to ver. 2.7.8, but I still cannot remove or disable the demo logbook.
|
The logbook name is in the URL of your browser. In the demo installation, there is a link in the start menu pointing to http://localhost:8080/demo. If you rename your logbook to something else, you have to change the URL accordingly. The simplest thing is to point it to http://localhost:8080, then you will be presented with a list of available logbooks. |
66716
|
Fri Feb 19 13:03:31 2010 |
| Tony Albers | tony.albers@gmail.com | Question | Linux | 2.6.3 | Re: Remove "demo" logbook.. |
Tony Albers wrote: |
Hi,
Is it possible to remove the "demo" logbook?
If I rename the section in elogd.cfg , it complains:
Error: logbook "demo" not defined in elog.conf Please use your browser's back button to go back
But there are other logbooks it can show instead. Is the "demo" logbook hardcoded in elogd?
/tony
|
I now upgraded to ver. 2.7.8, but I still cannot remove or disable the demo logbook. |
66715
|
Thu Feb 18 20:16:13 2010 |
| Tony Albers | tony.albers@gmail.com | Question | Linux | 2.6.3 | Remove "demo" logbook.. |
Hi,
Is it possible to remove the "demo" logbook?
If I rename the section in elogd.cfg , it complains:
Error: logbook "demo" not defined in elog.conf Please use your browser's back button to go back
But there are other logbooks it can show instead. Is the "demo" logbook hardcoded in elogd?
/tony |
66714
|
Thu Feb 18 18:50:57 2010 |
| Yoshio Imai | | Question | All | 2280 | Re: Single Button Entry |
Geoff Ellis wrote: |
For our application we have a lot of very common events we would like to log. It would be preferable that for certain events/entries we could setup a single button / quick entry method. Is there away to accomplish this?
|
You could write a script/program that calls the ELOG client with the necessary attributes to submit the entry (see the user's guide). |
66713
|
Thu Feb 18 15:37:07 2010 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Problem using attribute type |
soren poulsen wrote: |
soren poulsen wrote: |
Hi,
This little logbook has a problem:
------------------------
Attributes = Author, Category, Type, Subject, Number
Type Number = numeric
Options Category = General{1}
{1} Options Type = Routine
------------------------
(it was of course more complicated to start with).
When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.
To avoid the problem, I just comment out the line "Type Number ... "
Is this a bug ?
Thanks for your time
Soren
(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).
|
To overcome this problem it is sufficient to switch language from "Language = french" to "Language = english"
It was a mistake not to include the "global" settings in this bug report.
What probably happens is that something in the French translation (accents ?) disturbs the java scripting.
Soren
|
To use "Language = french" it is necessary to remove or substitute the accent character ' with something else in eloglang.french and then the Javascript code works again.
Soren |
66712
|
Thu Feb 18 13:21:15 2010 |
| soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.8-2282 | Re: Problem using attribute type |
soren poulsen wrote: |
Hi,
This little logbook has a problem:
------------------------
Attributes = Author, Category, Type, Subject, Number
Type Number = numeric
Options Category = General{1}
{1} Options Type = Routine
------------------------
(it was of course more complicated to start with).
When creating a new entry and selecting the Category option, there is a problem with the JavaScript which will populate the Type option.
To avoid the problem, I just comment out the line "Type Number ... "
Is this a bug ?
Thanks for your time
Soren
(P.S. Using a reserved name as an attribute name is maybe not optimal, but it does not seem to be the problem).
|
To overcome this problem it is sufficient to switch language from "Language = french" to "Language = english"
It was a mistake not to include the "global" settings in this bug report.
What probably happens is that something in the French translation (accents ?) disturbs the java scripting.
Soren
|