But it says locked on "websubmission" in the instructions for the command "Locked attributes".

Doesnt it  mean that for instance a logged in admin should be able to change a value of a submitted locked attribute.

I am looking for a possibility to have have certain attributes locked on submission but for instance admin should be able to change the data in them after they has been submitted.

 OK!

Thank you for a fast response!

Do you plan to implement this feature in later releases?

 Is it possible in some other way to make certain attributes preset but readonly for normal user at submission but afterwards changed by admin user?

 First, I really appreciate this software. Thank you.

Next, I have question - am wanting to have a 'dashboard' of sorts that shows all entries that are 'open'. That part is easy enough. But, then I want to color the time (or some other field) if the ELOG has not been updated/created for more than X hours. This will help us keep track of events that need status updates.

Doable?

Thanks!

In the elogd.c file nearly at the very top is the following line:

char svn_revision[] = "$Id: elogd.c 2411 2011-04-01 14:39:35Z ritt $";

How does this information get into the source file?  Is it a script used when the svn changes are committed, or perhaps when they are checked out?  Any details or pointers to info on the web would be greatly appreciated.

Thank you for the answer, but it didn't solve the problem.

• I used Self Register instead of Self Authentication. I deleted the complete path and only used the Filename.

• The Account which is used to start the Elogd process is local system. System has full right at the logbook directory

 Should I use an Admin Account for the elogd process? The error message is always the same (page not reachable) The File is also not created in the logbook dir.

Is there a limit on the number of conditions that can be simultaneously active in a log?  When I activate more than 10 conditions I start to see side effects with other conditions being deactivated.  I think this is due to the hard-coded array size of 10 for clist in the match_param function in elogd.c.  If so, could this limit be increased?  

Are there other limits on the number of conditions, or the length of condition names?  If I've understood the code right, the _condition string holds a comma-separated list of the active conditions, so the 256 byte length of this will also put some limit on the number of conditions that can be active.

 I'm having some confusion with configuring my logbook.  In the global section of the logbook I have the quick filter enabled, but it is not a drop down list, only an editable text field:

I think it is an attributes issue, but I'm having some trouble making sense of those from the syntax page.  Here is my config file:

[global]

port = 8080

usr = vulcanstaff

Max content length = 1073741824

Menu commands = New, Edit, Delete, Reply, Find, Last day, Move to, Copy to, Import, Help

RSS Title = $subject, posted by $author on $entry time

RSS Entries = 10

Quick filter = Date, Subject, Subtext

Use Lock = 1

Reverse sort = 1

Required Attributes = Author, Subject

[Experiment_Logbook]

Theme = default

Comment = Experiment Logbook

Attributes = Author, Author Email, Type, Category, Subject

Options Type =  Other

Options Category = Start Up

Extendable Options =Category

Page Title = $Subject