First of all, why do you a reply to a very old message? For each new topic you should start a new thread.

I don't know exactly what goes wrong in your case. Just a few ideas:

• Having a '.' in a logbook name can cause trouble, better remove it
• Having a subdir starting with '\\' might work, but I never tried it, does it work if you use a subdirectory on the same drive just with "Subidr = \elog\..." ?
• There is also the option "Logbook dir = ..." which you might try

Hi,

One of my logbooks is a fault reporting system; it emails a group of people when a fault is reported. There is an MOption 'Technical Groups', and I want to have a tooltip for each checkbox which shows who is referred to by each group name. However, individual tooltips for each MOption attribute don't seem to work. I've looked at the HTML code, and there's no 'title' attribute for the checkboxes, so it's not a browser problem. I've attached my config file. Any idea what's going wrong?

ben

The syntax for tooltips is

Tooltip <attribute option> = <tooltip>

but you have

Tooltip "<attribute>" "<attribute option>" = <tooltip>

which is not correct, but would make more sense, since you could have an attribut option being valid for several attributes. So I changed elogd to accept both syntax in revision 2158. Please note that you should not put "quotes" around attribute values or options.

 Thanks! I got rid of the quotes around everything, and it works now.

ben

When submitting entries via the elog client, I find that I can set arbitrary values for attributes that are supposedly "preset" and "locked".

As an example, I have in my elogd.cfg file:

[global]

...

Group Operations = Accelerator

Top group ATLAS = Operations

...

[global ATLAS]

Attributes = Experiment, Author, Author Email, Category, Subject
Required Attributes = Category, Subject
Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other
Extendable Options = Category

Preset Experiment =
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Experiment, Author, Author Email

...

[Accelerator]
Attributes = Author, Author Email, Category, Subject
Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other

...

This works as intended with a web client (firefox). The Author and Author Email attributes are preset and unchangeable.

However, if I use the elog client, as in:

elog -v -h my.apache-proxy.server -d elog -l Accelerator -p 443 -s -u johndoe xxxxx -a Category=LN -a Subject=Test -a Author=IDoNotExist -n 1 -m entry.txt 
(johndoe is an existing user)

 

The entry is created with "IDoNotExist" as the Author name, instead of the correct name for the user johndoe,
and the Author Email attribute is blank.

Is there a way to enforce preset and locked attributes in the elogd server? (As a client could connect
with any arbitrary software, not just elog.)

elog -v -h my.apache-proxy.server -d elog -l Accelerator -p 443 -s -u johndoe xxxxx -a Category=LN -a Subject=Test -a Author=IDoNotExist -n 1 -m entry.txt 
(johndoe is an existing user)

 

The entry is created with "IDoNotExist" as the Author name, instead of the correct name for the user johndoe,
and the Author Email attribute is blank.

Is there a way to enforce preset and locked attributes in the elogd server? (As a client could connect
with any arbitrary software, not just elog.)

Indeed "preset" and "locked" attributes are not obeyed if entries are submitted via the elog tool. The is because if you use a browser, the input form is created by elogd. If you use a locked attribute, the input filed for that attribute is not shown for example. If you use the elog tool, it directly submits an entry not knowing anything about the input form. To make this work, elog would first have to request the input form, then interprete all the HTML, figure out if an attribute is locked or not, then display an error if you try to submit that attribute. Since parsing of HTML is not implemented in elog, this is currently not possible. 

Originally I thought that this is not such a problem. Mostly elog is used to produce some automatic entries, where the authorship is of minor interest. But I guess you are afraid that one use could submit an entry under another user's name, right? Well, I hoped that in scientific collaborations nobody is that evil ;-)

Well, I will try to do something here in order to fix this. Will come back to you.

Actually I found a way around. The "Subst xxx" is evaluated after you submit an entry, so it also works for the elog tool. So all you need in your config file is:

Subst Author = $long_name

and it will do the job.

Hi,

how can i make the author field read only on new postings? It should take the value from $long_name after login and without login there is no way to make new postings.

This is a part of my elogd.cfg

[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 Brassmann