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