> > 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 |
Theme = arco
Comment = ARCO eLogBook
Logfile = /var/log/elog/feedback.log
Logging level = 3
Self register = 3
Restrict edit = 1
Password file = arco.users
Admin user = albert
;no email notification by default
Suppress default = 1
Display mode = threaded
List display = Subject, Type, Author, Date
Thread display = $subject, posted by $author on $entry time
Show attachments = 1
Start page = ?mode=threaded&attach=1
Expand default = 0
Page Title = eLogbook feedback - $subject
Title image URL = http://ares.roma2.infn.it/ARCO/
Title image = <img border=0 src="ARCO_logo.jpg" alt="ARCO logo">
Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Login, Help
Attributes = Author, Type, Category, Subject
Required Attributes = Author, Type, Subject
Options Type = Suggestion{1}, Bug{2}, Other{3}
Show Attributes = Author, Subject, Type
{2}ROptions Category = opened, to be verified, solved
{2}Preset Category = opened
{2}Show Attributes = Author, Subject, Type, Category
; preset author and email
Subst on reply Author = $short_name
Subst on reply Author Email = $user_email
Preset Author = $short_name
Preset Author Email = $user_email
; these attributes cannot be changed
Locked Attributes = Author, Author Email
Fixed Attributes Reply = Subject
Reverse sort = 1
Quick filter = Date, Type
|
> > 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? |
> 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 :-) |