Hi, thanks to everyone involved for giving us the elog.

A question:

Is it possible to submit entries to an elog on a remote machine by email?

Thanks, Thorsten

We have a logbook in which we use two "Status" attributes, both of which are MOptions. What we want to do is have the corresponding line of the list change its colour depending on the combination of those attributes. I have done so successfully using "Style" for a single Options or MOptions or even two Options (using conditionals and a third attribute), but up until now I have no luck with two MOptions. Conditionals do not seem to work with MOptions (the manual only mentions Options and when I tried anyway, it did not work... ) and multiple "Style" statements also do not seem to work. I've tried the following:

MOptions StatusA = Status-A-red, Status-A-orange, Status-A
MOptions StatusB = Status-B-red, Status-B-orange, Status-B

Style StatusA Status-A-red = background-color:red
Style StatusA Status-A-red | Status-A-orange = background-color:red
Style StatusA Status-A-red | Status-A = background-color:red
Style StatusA Status-A-red | Status-A-orange | Status-A = background-color:red
Style StatusA Status-A-orange = background-color:orange
Style StatusA Status-A-orange | Status-A = background-color:orange
Style StatusB Status-B-red = background-color:red
Style StatusB Status-B-red | Status-B-orange = background-color:red
Style StatusB Status-B-red | Status-B = background-color:red
Style StatusB Status-B-red | Status-B-orange | Status-B = background-color:red
Style StatusB Status-B-orange = background-color:orange
Style StatusB Status-B-orange | Status-B = background-color:orange

As far as I can see, the "Style" statement for StatusB only gets evaluated if none of the statements for StatusA matches (i.e. StatusA = Status-A). What I would want to achieve is that any "red" condition in either StatusA or StatusB takes precedence over "orange" and "none" and that "orange" takes precedence over "none".

Is there any solution for this problem short of merging both status attributes into one (which would be very unwieldy, especially, as StatusB is not used at all in some cases)? Any suggestions are most welcome!

Thanks in advance,

Thomas

We've been having toruble with uploads not working and I notice that every time someone uploads to our elog the same error message appears in /var/log/syslog:

Cannot restore original GID/UID.

How can I fix thsi error? Or, perhaps more importantly, could it cause elog to "lock up" (note, it doesn't crash)?

I'm runing elog on Ubuntu kernel version 2.6.24-server.

I have two logbooks running, one for current accounts and one for non-active ones. The idea is to move an entry from one logbook to the other once an account becomes non-active. Both logbooks share some attributes (e.g. the name of the account, its creation date, ...), but both also have some uniqe attributes.

While I was playing with this set-up, I ran into a problem:

1. Move an existing entry from current to non-active.
   • "Type" and "Status" have options. "Created" and "Archived" are in date format.
   • "Created" and "Type" are supposed to be locked in non-active. This works.
   • "Archived" and "Status" are empty, as they do not exist in current. This also works.
   • Depending on the "Type", only certain of the additional attributes are shown on edit. This works as well.
   • I would also like "Status" to have some influence on how certain other attributes are preset and/or shown. This is where the problem starts...
2. Edit the entry in current.
   • As expected, "Created" and "Type" are shown as locked.
   • As soon as I change the selector for "State", the whole edit mask is redrawn - and the date shown in "Created" is deleted.

I've been experimenting with this quite a while and as far as can see the following applies:

• Only date format attributes are affected
• Only locked attributes seem to be deleted completely
• If I have a date attribute that is not locked and I set it partially in the edit mask (e.g. only select the month or enter a year), it is also deleted
• If I have a date attribute that is not locked and I set it completely in the edit mask (i.e. day, month and year), it is not deleted

During the experiments I came up with a stripped down version of the non-active logbook configuration, which does show the bug. It only contains Type, Created, Status, Archived. To make an entry to experiment, you'll have to comment out the "Locked attributes" line, make a new entry (with "Created" date), the uncomment that line.

I hope my description isn't too confusing - please don't hesitate to ask if anything is unclear. I'd be much obliged if you saw a chance to fix this at some point...

Best regards,

Thomas

Hi ,

i have a little problem with the guest access. There is no acces to the logbooks as a guest. Evereytime i see the loginbox after clicking the logbook.

[Informations]
Guest menu commands = List, Back, Find, Login, Help
Guest find menu commands = List, Find, Select, Login, Help
Password file = ./passwd
Self register = 1
Logfile = elogd.log
Logging level = 3
Login expiration = 24
Admin user = testuser

Theme = default
Preset Author = $long_name
Attributes = Author, Subject
Locked Attributes = Author
Required Attributes = Author, Subject
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Subtext

Thanks for help, Brassmann

[global]
.......

Logfile = elogd.log
Logging level = 3
Login expiration = 24
Password file = ./passwd
.......

[Informations]
.......

Logout to main = 1
Logbook tabs = 1
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help


Preset Author = $long_name
Attributes = Author, Subject
Required Attributes = Author, Subject
........

 Thanks, works fine.

Regards Brassmann

[global]
.......

Logfile = elogd.log
Logging level = 3
Login expiration = 24
Password file = ./passwd
.......

[Informations]
.......

Logout to main = 1
Logbook tabs = 1
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Select, Login, Help


Preset Author = $long_name
Attributes = Author, Subject
Required Attributes = Author, Subject
........

 Thanks, works fine.

Regards Brassmann