> Problem 1 - Since upgrading to version 2.3.0 I seem to have lost the some 
> functionality explained below.  When i first log into my logbook (i only 
> have a single one) it defaults to the summary view and the first field is 
> one called Customer Name as opposed to # as i wanted the list sorted by 
> this field, the link for that logbook entry is no longer available on the 
> first field (being Customer Name) but only on the # field), however if you 
> use Summary threaded view the whole line is a link.

I revised the way links are placed into the summary table, so I could have 
lost some functionality (I did not try all config combinations since there 
are too many now). So I can fix your problem in two ways now: Either always 
have the first item in a list be a link, or have each item be the (same) 
link. What do you think is a better solution?

> Problem 2 - no matter what i try in the config file i cannot get elogd to 
> use stylesheets ive tried specifying and even editing and removing the 
> default.css style sheet i downloaded but it just seems to ignore its there.

First question: Does your elog pages have color? If so, the default.css is 
loaded correctly. Otherwise your page would contain text but all would be 
white.

So I presume you see color, that means your default.css is loaded correctly. 
It can now be that your browser caches that stylesheet. I use MS Internet 
Explorer and Mozilla and a "reload" on the browsers refreshes the 
stylesheet, but you really have to press the "reload" button (or clear the 
browser cache). Have you tried that?

- Stefan

> I revised the way links are placed into the summary table, so I could have 
> lost some functionality (I did not try all config combinations since there 
> are too many now). So I can fix your problem in two ways now: Either always 
> have the first item in a list be a link, or have each item be the (same) 
> link. What do you think is a better solution?

I think the first option is the better one, having the first columns data in 
the list be linkable for example i am using this to store customer 
configuration and the list needs to be in alphabetical order so it has to be 
the first column but needs to be linkable :)

Would be nice if you can specify which columns data has links as a flag or 
setting of some sorts, as opposed to either the first or all, but given a 
choice I would want the first column to be the linkable one 

My config looks like this

Display search = Customer Name, Account ID, Author, Date, #

I think the better option is first item (being the first column entries) all 
have links to the logbook entries (which is how it was in the previous 
version) 

> 
> > Problem 2 - no matter what i try in the config file i cannot get elogd to 
> > use stylesheets ive tried specifying and even editing and removing the 
> > default.css style sheet i downloaded but it just seems to ignore its 
there.

I resolved this problem, many thanks for your help

> I just noticed that the notifications I receive from your ELOG system, 
> doesn't show anyone in the "TO:" section but myself.  Or is ELOG 
configured 
> to only send myself a message?

This is on purpose. I have many people registered for the Forum. So when a 
notification is sent, it is not a good idea if everybody sees everybody 
else's mail addresses. Therefor I have 

Omit Email to = 1

in the config file. This way the "To:" field is omitted to "hide" the mail 
recipients from each other. Your mail client realizes that and fills in your 
own address automatically, that's why you only see yourself. Maybe you try 
that option, might help with your previous problem as well.

- Stefan

> Would be nice if you can specify which columns data has links as a flag or 
> setting of some sorts, as opposed to either the first or all, but given a 
> choice I would want the first column to be the linkable one 

Well, I decided to make all entries in a table a link, to be consistent with 
the threaded display. But I changed the style such that they look like 
before, but are actually links. This way it cannot hurt (like having too 
much underlined text). The style can be changed via classes ".list1" 
and ".list2" in the style sheet.

The modification will come in 2.3.1, or you can get the source code from CVS 
under 

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c

and

http://midas.psi.ch/cgi-bin/cvsweb/elog/themes/default/default.css

> > > Problem 2 - no matter what i try in the config file i cannot get elogd 
to 
> > > use stylesheets ive tried specifying and even editing and removing the 
> > > default.css style sheet i downloaded but it just seems to ignore its 
> there.
> 
> I resolved this problem, many thanks for your help

What happened. If you tell your initial problems, I can maybe put something 
into the docs so that others won't have it...

- Stefan

> > > > Problem 2 - no matter what i try in the config file i cannot get 
elogd 
> to 
> > > > use stylesheets ive tried specifying and even editing and removing 
the 
> > > > default.css style sheet i downloaded but it just seems to ignore its 
> > there.
> > 
> > I resolved this problem, many thanks for your help
> 
> What happened. If you tell your initial problems, I can maybe put something 
> into the docs so that others won't have it...
> 
> - Stefan

I upgraded to version 2.3.0 the previous version didnt seem to work with 
stylesheets, when you viewed the html source there was no stylesheet defined 
in it.

Please see my other posts for feature requests.

Many Thanks - FANTASTIC program btw

> > Can you consider implementing the following additions to the functionality
> > 
> > 1) Subt on edit <attribute> = xyz 
> > 
> > This would be fantastic for implementing version control so you can see 
> who 
> > has edited a posted or a db entry.
> 
> Can you give me an example of how you would use that?

-----

Lets say you are storing configuration information relating to a customers 
solution, you need the ability to track who has made what changes to the 
config information stored in the log book so you can backtrack who changed 
what and when, for example

If you have a field name called Last Edited by this field is locked and not 
editable using the Lock attributes flag, but if you had Subt on edit 
everytime that entry is updated it places your login name into this field and 
therefore stamps it to say you have edited it, as the field isnt free txt it 
cant be spoofed as the $long_name comes from your login details.

-----
>  
> > 2) Have a SORT fieldname flag so you can decide which column to sort 
> things 
> > by on a display listing in conjunction to the display flags, it current 
> > defaults to the # column and I find i am directly linking to a sorted 
> > display
> 
> Sorting is not done by the "#" column but by the sequence when messages 
have 
> been entered. You can sort the table differently by clicking on the table 
> titles (twice for reverse sort). To sort by default on a column, for 
example 
> sort by the author, you can add
> 
> Start page = ?sort=author
> 
> into elogd.cfg which does the job.
----
Excellent I didnt know what Ill try that tomorrow

----

 

> > > Can you consider implementing the following additions to the 
functionality
> > > 
> > > 1) Subt on edit <attribute> = xyz 
> > > 
> > > This would be fantastic for implementing version control so you can see 
> > who 
> > > has edited a posted or a db entry.
> > 
> > Can you give me an example of how you would use that?
> 
> -----
> 
> Lets say you are storing configuration information relating to a customers 
> solution, you need the ability to track who has made what changes to the 
> config information stored in the log book so you can backtrack who changed 
> what and when, for example
> 
> If you have a field name called Last Edited by this field is locked and not 
> editable using the Lock attributes flag, but if you had Subt on edit 
> everytime that entry is updated it places your login name into this field 
and 
> therefore stamps it to say you have edited it, as the field isnt free txt 
it 
> cant be spoofed as the $long_name comes from your login details.

Ok, I implemented "Subst on edit", it will be contained in Version 2.3.1 
which is supposed to come out next week.

- Stefan

Stefan,

When will you have 2.3.1 out? I just upgraded to 2.3.0 and would like to see
the links in my summary view. If it is going to be out soon I will wait
instead of compiling from source.

Thanks for great software,
k.

> > Would be nice if you can specify which columns data has links as a flag or 
> > setting of some sorts, as opposed to either the first or all, but given a 
> > choice I would want the first column to be the linkable one 
> 
> Well, I decided to make all entries in a table a link, to be consistent with 
> the threaded display. But I changed the style such that they look like 
> before, but are actually links. This way it cannot hurt (like having too 
> much underlined text). The style can be changed via classes ".list1" 
> and ".list2" in the style sheet.
> 
> The modification will come in 2.3.1, or you can get the source code from CVS 
> under 
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c
> 
> and
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/themes/default/default.css
> 
> > > > Problem 2 - no matter what i try in the config file i cannot get elogd 
> to 
> > > > use stylesheets ive tried specifying and even editing and removing the 
> > > > default.css style sheet i downloaded but it just seems to ignore its 
> > there.
> > 
> > I resolved this problem, many thanks for your help
> 
> What happened. If you tell your initial problems, I can maybe put something 
> into the docs so that others won't have it...
> 
> - Stefan