| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66752
|
Fri Mar 12 12:28:36 2010 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.8-2280 | Re: could not get the threaded display working |
| FX FRERE wrote: |
|
I have been trying to get the display mode into threaded by default, it does not work on any of my logbooks. I saw related threads in this forum but none gave me a solution (unless the 2.7.8-2282 is available for download).
|
The display mode is taken from the configuration option "Display mode = ..." only the very first time a users accesses a logbook. When the user switches to any other mode (summary, full) by clicking on the according menu option, the new mode is stored in a cookie in the browser and overrides the "Display mode = ..." setting. Maybe that is what you see. |
|
66751
|
Fri Mar 12 11:26:27 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.8-2280 | Re: can one use a IOption field for conditional tests? |
| FX FRERE wrote: |
|
Hi again,
I was wondering if one could use a conditional statement on an IOption attribute? Indeed i try to do a visual logbook (a green check for OK result, a red cross for NOK result), unfortunately i cannot refer to the attributes value for conditional test, e.g:
IOptions Status= "Delete-icon.png" {1}, "Check-icon.png"{2}
Icon comment Delete-icon.png = Failed
Icon comment Check-icon.png = OK
{1} Show Attribute Edit = Attribute1, Attribute2
Thread Icon = Status
Attribute1 and 2 do not have any sense if the result was successful,
ELOG interprets the {1} and {2} as being part of the icon name!
thanks again for your help
FX
|
Conditions won't work for IOption attributes. You need an additional attribute like:
Attributes = Status, Subject, Icon
Options Status = OK{1}, Failed{2}
Ioptions Icon = icon1.gif, icon2.gif
{1}Preset icon = icon1.gif
{2}Preset icon = icon2.gif
|
|
66750
|
Fri Mar 12 10:15:20 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2140 | Re: Grouping Logbooks |
| mike cianci wrote: |
|
Stefan, sorry to bother you yet again. but I can not seem to get the "Subdir" to do what I want (user error I am sure). Thanks for any help you can give.
[OnlineHelps]
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0
List Menu commands = New, Find, Config
Thread display = -------------- $Title --------------
Comment = On-Line Helps
Attributes = Title
Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 1
[OLH.gsh]
Subdir = \\ssoelog\ELOG\logbooks\OnlineHelps
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0
List Menu commands = New, Find, Config
Thread display = -------------- $Title --------------
Comment = On-Line Helps
Attributes = Title
Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 1
|
First of all, why do you a reply to a very old message? For each new topic you should start a new thread.
I don't know exactly what goes wrong in your case. Just a few ideas:
- Having a '.' in a logbook name can cause trouble, better remove it
- Having a subdir starting with '\\' might work, but I never tried it, does it work if you use a subdirectory on the same drive just with "Subidr = \elog\..." ?
- There is also the option "Logbook dir = ..." which you might try
|
|
66749
|
Fri Mar 12 09:27:25 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.8-2282 | Re: Problem using attribute type |
| soren poulsen wrote: |
|
| 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
|
Indeed it was the JavaScript line
if (document.form1.Number.value != '- garder les valeurs d'origine -') {
which caused the trouble. The "'" character closed the string '- garder les valeurs d', which caused an exception. I changed it to
if (document.form1.Number.value != "- garder les valeurs d'origine -") {
and now it should work fine. |
|
66748
|
Fri Mar 12 09:18:11 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | latest | Re: Log Thread Close Automatically |
| tom wrote: |
|
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.
|
What you need is
Restrict edit time = ...
as written in the manual. |
|
66747
|
Fri Mar 12 09:16:28 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | V2.7.8-228 | Re: Last 3 days of log entries |
> It is a good point, and surprised that this particular number of days was overlooked.
>
> It only needs four lines added into elogd.c to achieve this. Even with my notorious
> c coding, I did it first time, but as I'm on linux, not a great help for you. Indeed,
> any other arbitary number of days could be added in, if you have the sources and means
> to recompile.
David send me his modification and I put it into the main source code, so it will be contained in the next Windows
version.
> I think windows versions are only updated on version number, not svn number, so it will
> require a request to the great man himself(*) to produce a new version for windows.
>
> (*)Hint; Stefan likes the occasional beer.
Yepp ;-) |
|
66746
|
Fri Mar 12 08:57:07 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.8.2282 | Re: Limit elog e-mail to only people involved with an entry |
| Paul Paquette wrote: |
|
Can I limit an elog entry mails to only go to my e-mail, my supervisor and the person who is entering the elog entry. I have the Elog server on Windows XP Pro running version 2.7.8.2282.
|
That should be possible with the following configuration options:
Suppress email to users = 1
Email all = <your e-mail>, <your supervisor e-mail>, $user_email |
|
66745
|
Fri Mar 12 08:18:06 2010 |
 | Cliff Shaw | cliff.shaw@stratosglobal.com | Bug report | Mac OSX | 2.7.8 | Elogd crashes when closing more than ten entries |
Hi Stefan,
I have noticed a problem when closing multiple log entries i.e entries which have more than 10 threads. I use Select -> Click the box that appears next to the thread I wish to close -> Edit.
As soon as I click on Edit the elogd service crashes and Windows displays an error message window. The only work around has been opening up all the threads and individually changing the "Status" to Closed.
Forgive me if this issue has been raised before but I have looked throughout the Forum and could not see anyone experiencing the same problem.
Thanks
Cliff |