> do not use confused name in attributes
> **************************************
> like
> Attributes Type, Type2
> the info on Type2 will be placed in the Type also
> see attachment 1
> 
> Never use confused name like '
> Attributes PC_Memory, Memory

I acknowledge the problem. It had to do with the fact that for checkbox 
options, the first checkbox is submitted in the above case as "Type0", the 
second as "Type1", and the third as "Type2" which conficts with the other 
attribute. I fixed that and use now "Type#0" and so on which should be fine.

The fix will be included in V2.2.6.

Stefan

I'm interested using elog for a lab notebook.  Once entries have been
entered they cannot be changed/edited.
Is it possible for elog to be setup to support something like this?  A write
only mode?

> I'm interested using elog for a lab notebook.  Once entries have been
> entered they cannot be changed/edited.
> Is it possible for elog to be setup to support something like this?  A write
> only mode?

What you need is an entry in the elogd.cfg file:

Manu commands = Back, New, Reply, Find, Config, Logout, Help

As you see, the "Edit" and "Delete" commands are missing here and therefore 
do not get displayed. So you can enter a message with "New", but you cannot 
change it afterwards.

Does this truly disable the edit command or just hide it?

> > I'm interested using elog for a lab notebook.  Once entries have been
> > entered they cannot be changed/edited.
> > Is it possible for elog to be setup to support something like this?  A write
> > only mode?
> 
> What you need is an entry in the elogd.cfg file:
> 
> Manu commands = Back, New, Reply, Find, Config, Logout, Help
> 
> As you see, the "Edit" and "Delete" commands are missing here and therefore 
> do not get displayed. So you can enter a message with "New", but you cannot 
> change it afterwards.

> Does this truly disable the edit command or just hide it?

You're right! In some earlier versions, it did disable it, but in 2.2.5 it 
just hides it. I fixed that bug and from 2.3.0 on it will really disable 
that command again, such that if someone enters manually

http://midas.psi.ch/elogdemo/Forum/202?cmd=Edit

will produce and error if the command is not in the menu list.

When ELOG is configured for Self-Register=3, is it still possible
to use the Author attribute as a Quick Filter? 

When I try it, the Author drop down box doesn't display anything.

Thanks,
Eric

> When ELOG is configured for Self-Register=3, is it still possible
> to use the Author attribute as a Quick Filter? 
> 
> When I try it, the Author drop down box doesn't display anything.
> 
> Thanks,
> Eric

The "Quick Filter" facility only works for attributes which are avaiable as 
an "Options <attribute> = ..." list. So if you have a "free" attribute like 
the author, the systen would have to scan the whole logbook to find all 
possible authors, which would result in some unacceptable performance 
degradation. Nevertheless, in systems with a limited number of authors one 
can add the "options author = ..." statement to get the selection box. The 
behaviour is independent of the "Self-Register" setting.

Ive got 2 issues which I cant see to resolve I was wondering if anyone can 
help.

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.

Is there a flag or setting to the make the first field a link?


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.

Any help or advice ??????