I don't see anyway to define a log as an attribute. May be I just don't understand
something. I have more than 50 logs anyway.

Sorting is not something I have to have but it would make the servers names a little easier
to find. However, I can get them into any order I want buy rearranging them in the config
file. I've already done that for some of them. 

Groups on the front page would make navigation easier but it really isn't necessary.

I was hoping their was a way to do this that I had overlooked.


> OK, I'm willing to give a shot but I don't know how to do it. I'll look in the docs and
> see if I can figure it out.  Thanks.
>  
> > Before I go and implement additional features, I would like to check if your problem 
> > cound not be solved easier. Whey don't you define your server as an attribute inside 
> > a logbook instead of having separate logbooks for each server? You know that you can 
> > sort by attributes (just by cliking on the column header for that attribute), so that 
> > would satisfy your need for sorting.

> I don't see anyway to define a log as an attribute. May be I just don't understand
> something. I have more than 50 logs anyway.

What I meant was having only one logbook, and having the server as an attribute like

Attributes = Server, Type, ....
Options Server = Server1, Server2 (just the names of your current logbooks)
...

If you have already 50 logbooks this would require quite some work of course, but it might 
something for the future. I don't know if this fits into your requirements. If not, please 
let me know your complete scheme (current attributes and logbooks), then I can think about.

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

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

 I put your request on the wish list.

Looks like a nice idea. You can sneak in any JavaScript code into elog pages with the "Top text" option. Like

Top text = <script>window.onload = function() {...}</script>

Then you parse the DOM tree to find your input field for the location, and attache your JS code to it. All the input fields have the "name" attribute in the HTML code set, so it should be easy to find the input field in the DOM tree.

/Stefan

> Any ideas? I run our ELOG on windows server.. maybe that has something to do with it.

I am running the server on kubuntu 8.x, and have the same issue with chrome 1.x.
Is is possible the corporate elog server is running behind apache or in some
other proxy config while the one you are having issues with is being connected
to directly by chrome?

-- rouilj