HI 
I have setup top group in my elog . I will want to restrict the different 
admin user on the global and the global on top groups .
But however i am not able to use the configuration on "admin user" on the 
global portion to strict admin of top group to access the main global 
config .
Did i configure it wrongly or is there a way?

And for email notification , is there a way which i can select who to email 
it to ? like check box etc.

And is there a way which i can setup the summary page to refresh every 
15mins , so that new entry can be shown ?

And can i make the message id unique , when i move the messages from one 
log book to another log book , the messages id change accorddingly based on 
the number or messages . Anyway for me to make it fixed even i moved to 
another log book , i need the running number still .

Sorry for the many questions
Thanks for your help

> I have setup top group in my elog . I will want to restrict the different 
> admin user on the global and the global on top groups .
> But however i am not able to use the configuration on "admin user" on the 
> global portion to strict admin of top group to access the main global 
> config .
> Did i configure it wrongly or is there a way?

There was indeed a bug which I fixed. Please obtain the newest snapshot (see
download page). If an admin user is defined in a top group, it does not gain
access to the global if the admin of the global is different, like

[gloabl]
password file = passwd
admin user = joe

Top group g1 = demo1, demo2
Top group g2 = demo3, demo4

[global g1]
admin user = joe

[gloabl g2]
admin user = jack

[demo1]
....

So if user "jack" is logged in to demo3 and therefore g2, he can change the
[global g2] section, but not the [global] section, since only user "joe" is
allowed to so do.

> And for email notification , is there a way which i can select who to email 
> it to ? like check box etc.

This is not directly implemented, but one can configure this kind of "manually",
like

Attributes = ..., Send Email, ...
ROptions Send Email = joe, jack, ...

Email "Send email" joe = joe@some.domain
Email "Send email" jack = jack@other.domain

The option "Email <attribute> <value> = <email address>" gets executed when the
attribute "Send email" has the value "joe" in the first line, so email is sent
to joe@some.domain. It's a bit cumbersome since one cannot use the email
addresses from the password file, but better than nothing. 

> And is there a way which i can setup the summary page to refresh every 
> 15mins , so that new entry can be shown ?

No, this is not foreseen. One should use email notification for that, which
tells you immediately (not after 15 mins) when a new entry has been submitted.

> And can i make the message id unique , when i move the messages from one 
> log book to another log book , the messages id change accorddingly based on 
> the number or messages . Anyway for me to make it fixed even i moved to 
> another log book , i need the running number still .

The message id must be unique in a logbook (like in a relational database). If I
would keep the id when moving entries to another logbook, this could cause a
conflict. Assume you have two logbooks both with three entries having ID's
1,2,3. Now you move ID 3 from the first logbook to the second, but ID 3 exists
already in the second logbook, so you would have that ID twice, which breaks the
database structure. What you can do however is user an "numbered" attribute like

Attributes = ..., tag, ...
Preset tag = ID%d

For each new submission, the attribute "tag" gets a new number, like ID1, ID2
etc. These attributes are not modified when moving an entry to another logbook,
but if the target logbook has already an entry with the same tag, you get this
tag twice. I don't know if that is what you want...

Hi Stefan
Thanks for your reply
Can i check , with the new snap shot , can i disable the capability for the admin 
to delete the logbook and create new logbook
I tried with the config -
Allow Delete the logbook = admin 
 but cannot , please advise

And As for the id , can i have the month and the day in the id , what is the 
corresponding field for just the month and day , if there is .

And is there a way to prevent preset value get overwritten when user do a reply
Example , i preset a field with 
Preset test = "9v"
so when the user submit , it will have 9v and they may have enter some following 
value. but when a user reply , the test field get reset back to 9v

Thanks 


> > I have setup top group in my elog . I will want to restrict the different 
> > admin user on the global and the global on top groups .
> > But however i am not able to use the configuration on "admin user" on the 
> > global portion to strict admin of top group to access the main global 
> > config .
> > Did i configure it wrongly or is there a way?
> 
> There was indeed a bug which I fixed. Please obtain the newest snapshot (see
> download page). If an admin user is defined in a top group, it does not gain
> access to the global if the admin of the global is different, like
> 
> [gloabl]
> password file = passwd
> admin user = joe
> 
> Top group g1 = demo1, demo2
> Top group g2 = demo3, demo4
> 
> [global g1]
> admin user = joe
> 
> [gloabl g2]
> admin user = jack
> 
> [demo1]
> ....
> 
> So if user "jack" is logged in to demo3 and therefore g2, he can change the
> [global g2] section, but not the [global] section, since only user "joe" is
> allowed to so do.
> 
> > And for email notification , is there a way which i can select who to email 
> > it to ? like check box etc.
> 
> This is not directly implemented, but one can configure this kind of "manually",
> like
> 
> Attributes = ..., Send Email, ...
> ROptions Send Email = joe, jack, ...
> 
> Email "Send email" joe = joe@some.domain
> Email "Send email" jack = jack@other.domain
> 
> The option "Email <attribute> <value> = <email address>" gets executed when the
> attribute "Send email" has the value "joe" in the first line, so email is sent
> to joe@some.domain. It's a bit cumbersome since one cannot use the email
> addresses from the password file, but better than nothing. 
> 
> > And is there a way which i can setup the summary page to refresh every 
> > 15mins , so that new entry can be shown ?
> 
> No, this is not foreseen. One should use email notification for that, which
> tells you immediately (not after 15 mins) when a new entry has been submitted.
> 
> > And can i make the message id unique , when i move the messages from one 
> > log book to another log book , the messages id change accorddingly based on 
> > the number or messages . Anyway for me to make it fixed even i moved to 
> > another log book , i need the running number still .
> 
> The message id must be unique in a logbook (like in a relational database). If I
> would keep the id when moving entries to another logbook, this could cause a
> conflict. Assume you have two logbooks both with three entries having ID's
> 1,2,3. Now you move ID 3 from the first logbook to the second, but ID 3 exists
> already in the second logbook, so you would have that ID twice, which breaks the
> database structure. What you can do however is user an "numbered" attribute like
> 
> Attributes = ..., tag, ...
> Preset tag = ID%d
> 
> For each new submission, the attribute "tag" gets a new number, like ID1, ID2
> etc. These attributes are not modified when moving an entry to another logbook,
> but if the target logbook has already an entry with the same tag, you get this
> tag twice. I don't know if that is what you want...

> Can i check , with the new snap shot , can i disable the capability for the admin 
> to delete the logbook and create new logbook
> I tried with the config -
> Allow Delete the logbook = admin 
>  but cannot , please advise

No, disabling the capability to delete the logbook is not implemented. Usually the
admin user is an experienced user who knows what she/he does. The admin user typically
also was write access directly to the elogd.cfg file, and no flag in the world can
then prevent them from adding/removing logbooks by changing elogd.cf directly.

> And As for the id , can i have the month and the day in the id , what is the 
> corresponding field for just the month and day , if there is .

No, but it's on the wishlist. I added your vote there.

> And is there a way to prevent preset value get overwritten when user do a reply
> Example , i preset a field with 
> Preset test = "9v"
> so when the user submit , it will have 9v and they may have enter some following 
> value. but when a user reply , the test field get reset back to 9v

This is clearly a bug. The 'Preset test = 9v' should not be evaluated on a reply. I
fixed that and updated the CVS and snapshot.

- Stefan

Hi - again a configuration question.

How can I suppress all email notifications? The "Suppress default = 2" flag 
allows me to always produce a notification, but the flag does not provide 
an option to never produce a notification. The flag "Suppress Email on 
edit" does help a bit, but still notifications for new messages will be 
sent.

I'm looking forward to your fast response... So far your support is 
fantastic!

Bartjan Wattel

> How can I suppress all email notifications? The "Suppress default = 2" flag 
> allows me to always produce a notification, but the flag does not provide 
> an option to never produce a notification. The flag "Suppress Email on 
> edit" does help a bit, but still notifications for new messages will be 
> sent.

Suppress email to users = 1

RTFM

Hi, 

I was just searching your online discussion forum for entries with the 
word 'password' in the subject. I noticed that the 'Full' option in 
the 'full/summary/threaded' line displays the results of all entries in the 
logbook, and not only the entries with the word 'password' in the subject.

I think there is an error in the URL, because when looking for the word 
password in the subject, the URL for the 'Full' option is:
http://midas.psi.ch/elogs/Forum/page1?mode=full&reve&npp=8&Subject=password

If I change the word 'reve' in this URL to 'reversed=1', the results are 
correct

Bartjan Wattel

Thanks for pointing out this bug. I fixed it. New version under CVS.

Hi,

I want to create a series of logbooks, say logbook A, and logbooks B up to 
including S. I want the logbooks B,C,D,E,...S to have the same options and 
layout, the only difference is: the name of the logbook, and an options or 
extendable options list. All other settings of logbooks B-S are the same, 
while logbook A is a completely different logbook. 

I know I can simply copy the settings for logbook B and repeat the settings 
for all logbooks C-S. But is there a better way to accomplish this?

Thanks, 
Bartjan Wattel

> I know I can simply copy the settings for logbook B and repeat the settings 
> for all logbooks C-S. But is there a better way to accomplish this?

Yes. Put all common settings into the [global] section, only differences into
the individual logbook sections. Like

[global]
Attributes = ....
Options ....

[A]
; Logbook A is different
Attributes = ....
Options = ...

[B]
Option X = ...

[C]
Option X = ...

[D]
Option X = ...

This way all logbooks "inherit" the settings from the [global] section, only the
differents are superseeded in the individual sections. Still you need two lines
for each logbook, but all recurring configuration can be omitted.

> > I know I can simply copy the settings for logbook B and repeat the settings 
> > for all logbooks C-S. But is there a better way to accomplish this?
> 
> Yes. Put all common settings into the [global] section, only differences into
> the individual logbook sections. Like
> 
> [global]
> Attributes = ....
> Options ....
> 
> [A]
> ; Logbook A is different
> Attributes = ....
> Options = ...
> 
> [B]
> Option X = ...
> 
> [C]
> Option X = ...
> 
> [D]
> Option X = ...
> 
> This way all logbooks "inherit" the settings from the [global] section, only the
> differents are superseeded in the individual sections. Still you need two lines
> for each logbook, but all recurring configuration can be omitted.

Thanks for you quick and correct answer. I have one question left ;-)

Suppose I want to have different password files for all the logbooks, but I want to 
have a single (admin) user that can log in to all logbooks... Do I need to specify 
the admin data in all the different password files, or can I use one global 
password file containing the login name and password for the administrator?

> Suppose I want to have different password files for all the logbooks, but I want to 
> have a single (admin) user that can log in to all logbooks... Do I need to specify 
> the admin data in all the different password files, or can I use one global 
> password file containing the login name and password for the administrator?

I would not recomment different password files for all logbooks, but a common one and
individual "login user" options on the logbooks, like

[global]
Password file = xxx
Admin user = xxx
...

[A]
Options X = ...
Login user = <user1>,<admin user>

[B]
Option X = ...
Login user = <user2>,<admin user>

This has the advantage that there is only a single password file which is easier to
maintain.

Is it possible to add one more "text entry" field ?

> Is it possible to add one more "text entry" field ?

I guess you mean the main body text, which is multi-line. No, this is not
possible right, now, but I added your vote to the wishlist istem "Multi-line
attributes".

Your guess is correct. I would like to have that feature in ELOG.

Thanks

> > Is it possible to add one more "text entry" field ?
> 
> I guess you mean the main body text, which is multi-line. No, this is not
> possible right, now, but I added your vote to the wishlist istem "Multi-line
> attributes".

An options list that starts with a double-quotes character (") is handled 
incorrectly. 

Try the line: 
Options Student name  = "Doe, John", "Foo, Bar".

The ELOG list will have four entries, namely:
 - Doe
 - John
 - "
 - Foo, Bar

> Options Student name  = "Doe, John", "Foo, Bar".

I fixed this bug. Please obtain the newest snapshot (see download page).

Is there a way to disable editing of the textarea, but still allow editing 
of other fields in the entry? (e.g. Fixed Attributes Edit = Text)
Also, is the data entered in that field accessible through a variable like 
$author? I tried $text, but that doesn't seem to work.

Thanks,
-Todd

By the way... Nice work on this. It has a lot of good features.

> Is there a way to disable editing of the textarea, but still allow editing 
> of other fields in the entry? (e.g. Fixed Attributes Edit = Text)

I could add that option, but I don't know if it helps you (see below).

> Also, is the data entered in that field accessible through a variable like 
> $author? I tried $text, but that doesn't seem to work.

No, that won't work. Attributes are limite to some 500 characters, while the
text body is limited to 250000 characters. If you add $text to an attribute, it
would overflow or you would have to truncate the text, which I guess is not
good in both cases.

If you still want "Fixed attributes edit = text", please explain me you exact
case and I will consider implementing it.

> > Is there a way to disable editing of the textarea, but still allow editing 
> > of other fields in the entry? (e.g. Fixed Attributes Edit = Text)

I added a flag

Fix text = 0|1

A division in "fix text edit/fix text reply" does not make sense here, since I only
can lock the whole textfield, therefor just the switch.

New version under CVS (see download page).

> > > Is there a way to disable editing of the textarea, but still allow editing 
> > > of other fields in the entry? (e.g. Fixed Attributes Edit = Text)
> 
> I added a flag
> 
> Fix text = 0|1
> 
> A division in "fix text edit/fix text reply" does not make sense here, since I only
> can lock the whole textfield, therefor just the switch.
> 
> New version under CVS (see download page).

Thanks Stefan. Again, my hat is off to you for a great app.

Todd

I have some problems of understanding how the "Format <attribute>" parameter
is working. It may be, that there was a similar question in the forum, but I
didn't find it. I'm sorry if I come back with an old question.

I would like to have 2two attributes in the same line. As ex. PersonName,
PersonCity.

If I understand the handbook correctly, it should be posslible with "Format
<attribute> = 1". However, I'm not able to use the "Format <attribute>"
correctly because I do not understand how to use it correctly in the cfg file.

Is there a possibilty of an example by Stafan or does anybody else already
use this feature successfuly and is able to post a example here?

Thank's a lot!

> I have some problems of understanding how the "Format <attribute>" parameter
> is working. It may be, that there was a similar question in the forum, but I
> didn't find it. I'm sorry if I come back with an old question.
> 
> I would like to have 2two attributes in the same line. As ex. PersonName,
> PersonCity.
> 
> If I understand the handbook correctly, it should be posslible with "Format
> <attribute> = 1". However, I'm not able to use the "Format <attribute>"
> correctly because I do not understand how to use it correctly in the cfg file.
> 
> Is there a possibilty of an example by Stafan or does anybody else already
> use this feature successfuly and is able to post a example here?

This forum uses that feature. As you can see, if you display a single entry, the
author, subject etc. are on a single line. This is achieved with

Format Author = 1
Format Author email = 1
Format Category = 1
Format OS = 1
Format ELOG Version = 1

Note that in the entry form, each attribute is on a separate line no matter what
the format specifiers are. The single line option only works for the display page.

Thank you Stefan! Just was out of the office for some days.

There ar 2 questions in addition:

1. Is there a possiblity to fix the position of the attribut fields if they are in
the same line? As. ex. if one attribute is empty or contain a very short value it may
be possible that the position of the following atrributes in the line are moving to
the left, if the value is very long, they move to the right side. This make it
sometime not easy to read the informations, specially if the user browses trough some
entries, the picture the eyes are scanning is changing.

2. Did I understand you right, that tis will not work while editing? I would like to
put this to the wish list for a uppcoming version (not very importand, but VERY nice
to have), that it may be possible to use Format in the new and edit mode too, because
it is somtimes more comfortable to have some attributes grouped locically in one line
or to have a overview over all attributes on one screen without scrolling while editing.

ELOG has e very big flexibility and I'm amazed how fast and stable it's running under
Linu xas well as under Windows! - I love it!  :-)

Ueli

> > I have some problems of understanding how the "Format <attribute>" parameter
> > is working. It may be, that there was a similar question in the forum, but I
> > didn't find it. I'm sorry if I come back with an old question.
> > 
> > I would like to have 2two attributes in the same line. As ex. PersonName,
> > PersonCity.
> > 
> > If I understand the handbook correctly, it should be posslible with "Format
> > <attribute> = 1". However, I'm not able to use the "Format <attribute>"
> > correctly because I do not understand how to use it correctly in the cfg file.
> > 
> > Is there a possibilty of an example by Stafan or does anybody else already
> > use this feature successfuly and is able to post a example here?
> 
> This forum uses that feature. As you can see, if you display a single entry, the
> author, subject etc. are on a single line. This is achieved with
> 
> Format Author = 1
> Format Author email = 1
> Format Category = 1
> Format OS = 1
> Format ELOG Version = 1
> 
> Note that in the entry form, each attribute is on a separate line no matter what
> the format specifiers are. The single line option only works for the display page.

> 1. Is there a possiblity to fix the position of the attribut fields if they are in
> the same line? As. ex. if one attribute is empty or contain a very short value it may
> be possible that the position of the following atrributes in the line are moving to
> the left, if the value is very long, they move to the right side. This make it
> sometime not easy to read the informations, specially if the user browses trough some
> entries, the picture the eyes are scanning is changing.

Yes there is a possibility. In the format option, you can specify two CSS names, one for the
attribute and one for it's value. The default ones are "attribname" and "attribvalue". Just
make new ones by copying these two, renaming it to something like xxxname and xxxvalue where
"xxxx" is the name of the attribute. You find that in the file themes/default/default.css.
They contain a field called "width:" which can be changed:

.typename {
  width:150px;             <-- must be changed
  background-color:#CCCCFF;
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  padding:3px;
}

By having separate classes for all attributed, you can change their width separately,
accomplishing hopefully what you need.

> 2. Did I understand you right, that tis will not work while editing? I would like to
> put this to the wish list for a uppcoming version (not very importand, but VERY nice
> to have), that it may be possible to use Format in the new and edit mode too, because
> it is somtimes more comfortable to have some attributes grouped locically in one line
> or to have a overview over all attributes on one screen without scrolling while editing.

I will put this on the wishlist.

Stefan

Thank you Stefan!

1. Will help in the real hard cases!

2. Great! Specially editing adresses or some stutus overviews will be easier with a compleate
overview!

> > 1. Is there a possiblity to fix the position of the attribut fields if they are in
> > the same line? As. ex. if one attribute is empty or contain a very short value it may
> > be possible that the position of the following atrributes in the line are moving to
> > the left, if the value is very long, they move to the right side. This make it
> > sometime not easy to read the informations, specially if the user browses trough some
> > entries, the picture the eyes are scanning is changing.
> 
> Yes there is a possibility. In the format option, you can specify two CSS names, one for the
> attribute and one for it's value. The default ones are "attribname" and "attribvalue". Just
> make new ones by copying these two, renaming it to something like xxxname and xxxvalue where
> "xxxx" is the name of the attribute. You find that in the file themes/default/default.css.
> They contain a field called "width:" which can be changed:
> 
> .typename {
>   width:150px;             <-- must be changed
>   background-color:#CCCCFF;
>   border:1px solid #0000FF;
>   border-top:1px solid white;
>   border-left:1px solid white;
>   padding:3px;
> }
> 
> By having separate classes for all attributed, you can change their width separately,
> accomplishing hopefully what you need.
> 
> > 2. Did I understand you right, that tis will not work while editing? I would like to
> > put this to the wish list for a uppcoming version (not very importand, but VERY nice
> > to have), that it may be possible to use Format in the new and edit mode too, because
> > it is somtimes more comfortable to have some attributes grouped locically in one line
> > or to have a overview over all attributes on one screen without scrolling while editing.
> 
> I will put this on the wishlist.
> 
> Stefan