Thank you very much!

> Just since some people asked for: Here is the elogd.cfg for this demo 
> logbooks:
> 
> ========= cut here ===================
> 
> [global]
> logbook tabs = 1
> tab cellpadding = 2
> SMTP host = mailsend.psi.ch
> URL = http://midas.psi.ch/elogdemo/
> user = midas
> group = midas
> 
> [Linux]
> Theme = default
> Comment = General linux Tips & Tricks
> Data dir = /usr/local/elogdemo/logbooks/Linux
> Attributes = Author, Type, Icon, Category, Subject
> Options Type = Routine, Software Installation, Problem Fixed, 
> Configuration, Tips & Tricks, Info, Other
> IOptions Icon = icon1.gif, icon3.gif, icon4.gif, icon5.gif, icon6.gif, 
> icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
> Options Category = General, Hardware, Software, Network, Applications, 
> Shell, Account, Packages, Daemons, Other
> Required Attributes = Author
> Subst Author = $author
> Summary on default = 1
> Summary lines = 0
> Email all = stefan.ritt@psi.ch
> Email message body = 1
> 
> [Database]
> Theme = default
> Comment = Demo of database-like elog
> Data dir = /usr/local/elogdemo/logbooks/database
> Attributes = Type, Operating system, Location, Status, Comment
> Required Attributes = Type, Operating system, Location, Status
> Options Type = PC, Router, Bridge
> Options Operating system = Linux, Windows NT, Windows 2000, Windows XP, 
> Windows ME, Embedded
> Options Location = Building1, Building2, Building3
> Options Status = working, defect, in repair
> Show text = 0
> Start page = ?cmd=Search&mode=summary
> Display search = #, Type, Location, Status
> Summary lines = 0
> Find menu commands = New, Find, Last
> Menu commands = Back, New, Edit, Delete, Find, Config, Help
> Number Attachments = 0
> Suppress default = 2
> Entries per page = 10
> 
> [Forum]
> ; general options
> Password file = /usr/local/elogdemo/logbooks/forum/passwd
> Admin user = stefan
> Self register = 2
> Theme = default
> Comment = Discussion forum about ELOG
> Data dir = /usr/local/elogdemo/logbooks/forum
> Display mode = threaded
> Start page = ?cmd=Search&mode=threaded
> Menu commands = Back, New, Edit, Reply, Find, Last day, Last 10, Admin, 
> Config, Logout, Help
> Find menu commands = New, Find, Last x, Admin, Config, Logout, Help
> Guest menu commands = Back, Find, Login, Help
> Guest find menu commands = Find, Login, Help
> Number Attachments = 1
> Message comment = <img src=icons/icon6.gif> Please enter only serious 
> messages here, for testing use the <b>Linux</b> Logbook:
> Filtered browsing = 0
> Entries per page = 8
> Reverse sort = 1
> Restrict edit = 1
> 
> ; Attributes
> Attributes = Icon, Author, Author Email, Category, Subject
> IOptions Icon = icon1.gif, icon2.gif, icon3.gif, icon4.gif, icon5.gif, 
> Options Category = Info, Bug report, Bug fix, Question, Request, Comment, 
> Other
> icon6.gif, icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
> Required Attributes = Author, Author Email, Subject, Icon
> Subst on reply subject = Re: $subject
> Thread display = $subject, posted by $author on $Entry date
> Thread icon = Icon
> Remove on reply = Author, Author Email
> Date format = %B %d, %Y
> Preset Author = $long_name
> Preset Author Email = $user_email
> Locked Attributes = Author
> 
> ; Email notification
> Email message body = 1
> Display Email recipients = 0

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

> > Can you consider implementing the following additions to the functionality
> > 
> > 1) Subt on edit <attribute> = xyz 
> > 
> > This would be fantastic for implementing version control so you can see 
> who 
> > has edited a posted or a db entry.
> 
> Can you give me an example of how you would use that?

-----

Lets say you are storing configuration information relating to a customers 
solution, you need the ability to track who has made what changes to the 
config information stored in the log book so you can backtrack who changed 
what and when, for example

If you have a field name called Last Edited by this field is locked and not 
editable using the Lock attributes flag, but if you had Subt on edit 
everytime that entry is updated it places your login name into this field and 
therefore stamps it to say you have edited it, as the field isnt free txt it 
cant be spoofed as the $long_name comes from your login details.

-----
>  
> > 2) Have a SORT fieldname flag so you can decide which column to sort 
> things 
> > by on a display listing in conjunction to the display flags, it current 
> > defaults to the # column and I find i am directly linking to a sorted 
> > display
> 
> Sorting is not done by the "#" column but by the sequence when messages 
have 
> been entered. You can sort the table differently by clicking on the table 
> titles (twice for reverse sort). To sort by default on a column, for 
example 
> sort by the author, you can add
> 
> Start page = ?sort=author
> 
> into elogd.cfg which does the job.
----
Excellent I didnt know what Ill try that tomorrow

----

 

> > > Can you consider implementing the following additions to the 
functionality
> > > 
> > > 1) Subt on edit <attribute> = xyz 
> > > 
> > > This would be fantastic for implementing version control so you can see 
> > who 
> > > has edited a posted or a db entry.
> > 
> > Can you give me an example of how you would use that?
> 
> -----
> 
> Lets say you are storing configuration information relating to a customers 
> solution, you need the ability to track who has made what changes to the 
> config information stored in the log book so you can backtrack who changed 
> what and when, for example
> 
> If you have a field name called Last Edited by this field is locked and not 
> editable using the Lock attributes flag, but if you had Subt on edit 
> everytime that entry is updated it places your login name into this field 
and 
> therefore stamps it to say you have edited it, as the field isnt free txt 
it 
> cant be spoofed as the $long_name comes from your login details.

Ok, I implemented "Subst on edit", it will be contained in Version 2.3.1 
which is supposed to come out next week.

- Stefan

> I was wondering if you can help me understand the concept and if i am doing 
> something wrong with securing Elog via SSL
> 
> Basically im running elog on a redhat 8 box with stunnel already installed 
> as part of OpenSSL, on the server i ran the command specified in the 
> instructions
> 
> stunnel -d 443 -r 172.16.24.108:81
> 
> This command runs on the server, but when I access https://172.16.24.108/ i 
> get a page cannot be displayed, ive also put the URL = 
> https://172.16.24.108 entry in the elogd.cfg file
> 
> HELP!!!!!!!

Can you access your server locally under http://172.16.24.108:81 ??? If not, 
then you maybe specified the wrong port, so check elogd.cfg and the "-p" flag 
when starting elogd. If you can access it, and cannot access it under 
https://, then something must be wrong with your stunnel configuration. Maybe 
you run already a secure server under port 443? User "netstat -a" to check 
that.

Ooops, I destroyed the original post, now how can we fix this :)