When I create a new logbook (I used an existing one as a template) elog  
does not works anymore...  
  
- The problem is on elog user's file.. It seems elogd can't read it  
anymore:  
  
Cannot open file arco.users: Success  
Please use your browser's back button to go back  
  
- Here are some informations:  
sparcserv:/usr/share/elog# ps U elog  
  PID TTY      STAT   TIME COMMAND  
 5165 ?        Ss     0:08 /usr/sbin/elogd -f /var/run/elogd.pid  
-c /etc/elog.conf -d /var/lib/elog -s /usr/share/elog -p 8080 -n  
sparcserv:/usr/share/elog# id elog  
uid=106(elog) gid=106(elog) gruppi=106(elog)  
sparcserv:/usr/share/elog# ls -lha arco.us*  
-rw-------  1 elog elog 1,8K 2005-03-24 12:21 arco.users  
-rw-r--r--  1 elog elog  473 2005-03-23 10:41 arco.users_bak  
sparcserv:/usr/share/elog#                  
  
giving the arco.users file chmod a+wr does *not* make it work ...  
 
re-chmod-ing to -rw-------  AND restarting the daemon solves the problem 
and everything works nice ...  
 
any idea?  
  
 
 

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

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 

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

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

:-) yes I do 

A way may be using cookies, otherwise one can implement a kind o session mechanism
(using cookies or QS to pass sessid and storing user data on the server for a limited
time...)
the session method may be useful, but more difficult to implemnet, of course

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

it is attached

> > A way may be using cookies, otherwise one can implement a kind o session mechanism
> > (using cookies or QS to pass sessid and storing user data on the server for a limited
> > time...)
> > the session method may be useful, but more difficult to implemnet, of course
> 
> The concept of a session ID is not present in elog, so implementing it would be harder
> than writing elog from scratch. Keeping the thousand 'expansion' flags in cookies is bad
> as well, because your browser will send them all each time you request a page, which can
> then slow down things considerably over slow lines.

ok, i've downgraded my request then ...

it will be still useful to have the possibility of expland selectively a single thread :-)

> > ok, i've downgraded my request then ...
> > 
> > it will be still useful to have the possibility of expland selectively a single thread :-)
> 
> That you can do by clicking on the thread and look at the thread at the top of the page (;-))
> 
> That's exactly the same number of clicks as you would need to expand a thread (:-)))

LOL ..this way I can't see the list of other threads .. so il my goal is to inspect the thread
looking for something I have to:
- open the 3d
- return to 3d list
- open another 3d ..
[loop]

my wish would be to reduce it to
- open the 3d
- open another 3d ..
[loop]

of course I'm thinking to a big number of entries in a short number of 3ds .. making ugly to
simply expand everything .. :-)