It was done using the "groups" feature:

https://elog.psi.ch/elog/config.html#groups

Stefan

> 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

> 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

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

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

2.3.1 will come out next week, since this week I'm at home. But you always 
can get the sources from CVS (see below).

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

> I was upgrading to the latest version and I wrote over my cfg file. I 
> still have my database files. Is there a way to put the cfg file back 
> together using the database files as a guide.  It did not seem to want to 
> upgrade until I did this and I forgot to copy and then paste the cfg files 
> back.  The latest version is now running. Before I did this I was still 
> getting the old version number at the bottom of the main screen.  Also I 
> have an RSS reader that can do user name and password, is this possible 
> with Elog if the RSS reader has the ability?

I put an extra dialog box into the installer to prevent overwriting the
original config file, but unfortunately I cannot prevent people from shooting
themselves into the foot (;-)

The database files contain at least the attributes. Just open any file with a
text editor. But the other settings, like "preset <attribute>" etc. are lost.

Concerning teh RSS authentication, I willing to implement this if you tell me
which reader you are using, so that I can test it. You could also try yourself,
maybe it works without modification. What you would need is public read access
via "Guest menu commands" option plus a "Read password". The read password
prevents again the public read access, but the RSS reader can maybe submit it.
What the RSS reader certainly cannot do is to fill out the "Login" screen of
elog, so you need the "Guest menu commands" for sure.

- Stefan