> When I define 2 attributes, by default and the second one has to be showed
> depending on the first one value the elog correctly handle the thing, but
> the rss feed shows an empty comma separeted field corresponding to the
> conditional attribute not filled ...

Can you send me the part of your config files with those things so that I can
reproduce it?

> of course elog should remember the choice, so it will be possible to expand
> N threads over the M total ones..

How should elog remember that? If you put this into the URL like

http://<elog-host>/<logbook>/?exp=12&exp=14&exp=18

to expand the entries 12, 14 and 18, it might work fine. But imagine that some uses
have very long list with thousands of entries. This would make the URL very long,
everything very slow and could even crash some browsers.

What I usually do is to not expand the list. If I click on an individual entry, I
see then the expanded thread for that entry above that entry. But you probably
realized this possibility already.

is it possible to make the "+" sign, indicating a thread in the threaded
view, to be clickable in order to be able to expand a single thread each time ?

of course elog should remember the choice, so it will be possible to expand
N threads over the M total ones..

thanx :-) 

Is it possible to have last runtime filtering and viewing method to be
stored in a cookie in order to make them permanent across navigation ?

I mean:
- if I decide to view "all" entries in the elog and then open one of them, 
  I'd like not to select "show all entries" again and again
- same thing if I choose to view last week
- same for every runtime filter and/or viewing option 

hope this is simple to implement :-)  thanks in advance 

When I define 2 attributes, by default and the second one has to be showed
depending on the first one value the elog correctly handle the thing, but
the rss feed shows an empty comma separeted field corresponding to the
conditional attribute not filled ...

> What other information can I provide that might assist in diagnosing this?

Please send me your elogd.cfg configuration file.

> It's hard to tell the problem from what you report. Have you tried the latest
> release http://midas.psi.ch/elog/download/windows/elog258-6.exe ? There were
> some problems with the password file in 2.5.8 versions prior to patch level 6.

Yes, I am up to date with the latest version (2.5.8-6).

What other information can I provide that might assist in diagnosing this?

> I have an question for you :o). Is there any solution to use the filtering 
> system with an match case solution ? Add a parameter or something else to 
> add a solution ? 

I added a paramet "case sensitive search" which does this. In addition, the
switch defines the default state of the "case sensitive" check box on the find
page. The new functionality will be contained in the next release.