Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 274 of 807  Not logged in ELOG logo
icon5.gif   can one use a IOption field for conditional tests?, posted by FX FRERE on Tue Feb 9 18:54:22 2010 

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

    icon2.gif   Re: Grouping Logbooks, posted by mike cianci on Fri Feb 12 08:31:14 2010 

Stefan Ritt wrote:

 

mike cianci wrote:

I really appreciate your help and I hope that my questions warrant your time.

What I am trying to accomplish is two totally separate groups of logbooks that share a common logbook.

Three logbooks

Logbook A

Logbook B

Logbook C (just informational, write protected)

Two Groups

Top Group 1 = Logbook A, Logbook C

Top Group 2 = Logbook B, Logbook C

What is happening is everything looks good until you try to enter Logbook C from Group 1. You end up in Logbook C (the right logbook) but you are now in Group 2.

Actual Code:

;Groupings
Top Group Central = Centaur, On-LineHelps
Top Group Good Sam = GSH, On-LineHelps

You cannot put the same logbook into two groups. All you can do is to define two logbooks C1 and C2, and force their data directories to be the same (via the "Subdir = ..." directive), so they will actually look at the same data.

 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

icon5.gif   Single Button Entry, posted by Geoff Ellis on Tue Feb 16 04:17:24 2010 

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?

    icon2.gif   Re: Single Button Entry, posted by Yoshio Imai on Thu Feb 18 18:50:57 2010 

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).

icon5.gif   Remove "demo" logbook.., posted by Tony Albers on Thu Feb 18 20:16:13 2010 

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

    icon4.gif   Re: Remove "demo" logbook.., posted by Tony Albers on Fri Feb 19 13:03:31 2010 

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.

    icon2.gif   Re: Remove "demo" logbook.., posted by Stefan Ritt on Fri Feb 19 13:10:50 2010 

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.

    icon2.gif   Re: Remove "demo" logbook.., posted by Tony Albers on Fri Feb 19 14:12:41 2010 

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.

ELOG V3.1.5-3fb85fa6