[global]
port = 8080
password file = passwd
smtp host = your.smpt.host

[demo]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject, Email Type
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Options Email Type = plain{1}, html{2}

{1}Email encoding = 1
{2}Email encoding = 2

Options Email Type = plain{1}, html{2}

   If you have only one entry in the logbook and have it set up in threaded 
mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon 
of the entry or the number of the entry to see it, it does not allow you 
to.  If there is more than one entry, it works fine.  
   Also I wanted to make a submit page from where you could either go back 
to the logbook which you just entered a message for or type a new entry for 
that logbook.  First of all, is there a way to have only one file called 
submitpage.html in which I can define this for all logbooks or do i need it 
for ever logbook.  And also, is there a way I can even set a link that will 
allow to create a new entry.  I tried: 
    <a href="demo/?cmd=new">Enter</a> another message<p>

but for some reason it does not work.  Is there a way to implement this?

Thanks,
Mo

>    If you have only one entry in the logbook and have it set up in threaded 
> mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon 
> of the entry or the number of the entry to see it, it does not allow you 
> to.  If there is more than one entry, it works fine.  

Ok, has been fixed. Will come in 2.0.5

>    Also I wanted to make a submit page from where you could either go back 
> to the logbook which you just entered a message for or type a new entry for 
> that logbook.  First of all, is there a way to have only one file called 
> submitpage.html in which I can define this for all logbooks or do i need it 
> for ever logbook.  And also, is there a way I can even set a link that will 
> allow to create a new entry.  I tried: 
>     <a href="demo/?cmd=new">Enter</a> another message<p>
> 
> but for some reason it does not work.  Is there a way to implement this?

The documentation was wrong about that which has been corrected. The proper 
file contents should be

<h1>You successfully submitted a message</h1>
<a href="?cmd=Back">Back</a> to the logbook<p>
<a href="?cmd=New">Enter</a> another message

This way one only needs one file for all logbooks.

• Do the self registration by sending a key to the registered email address. Only by using that key the account can be activated. This way at least on ensures a proper email address initially. There are however ways to temporaryly generate email accounts, which kind of bypasses this system. Furthermore, if an email address becomes invalid because the domain is switched off, this does not help.
  
• Email at least an error notification to the admin in case of failure.
  

Cannot restore original GID/UID.
Cannot remove pidfile "/var/run/cr-elogd.pid"
; Permission denied
Cannot restore original GID/UID.
Cannot remove pidfile "/var/run/cr-elogd.pid"
; Permission denied

Just answer it myself : I thought of the checkboxes in front of the attributes as boolean. However, it has to to with the browse feature filtered browsing =1= In this way you can, when checking one of the checkboxes, browse to the same item clicking the next and previous button. Sorry , my question was about RTFM ( Read The Fucking Manual ) So this question is solved.

However , it would be nice to have a checkbox in front of one attribute. Suppose you have a lot a entries in a record ,that are readonly( predefined). The user of the form must only confirm that a job is done by checking the checkbox without going to the edit mode. So, the checkbox is writable in readonly mode. I can inmagine something like : attribute record check = attribute in the configuration file. In this way the user of the form says : job done. There can be only one checkbox for the record.

[ job done]  [ customer ] [ activity ] [ What should be done ]
[X]           BLA          Check job1   Backup mail check
[]            BLA1         Check job2   check error report
[X]           Bla2         Check job3   check MQ jobs

Thanks for your reading this

[ job done]  [ customer ] [ activity ] [ What should be done ]
[]            BLA          Check job1   Backup mail check
[]            BLA1         Check job2   check error report
[]            Bla2         Check job3   check MQ jobs