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

Hello to all,

I'm trying to get ELOG to run several separate logbooks which will
eventually have their own password/user files and other little things.
The problem I have is I want to have a main selection type page so when a
user enters ELOG they see this page with links on it to main logbook groups.

So, for my example I'd have a main page INDEX1.HTML which has links to:
  /Server_Logbooks
  /Other_Logbooks

but I want those top groups to just show standard ELOG generated logbook
list once you select a link on index1.html page.
Unfortunately "Selection page = index1.html" if defined in [global] just
gets used everywhere, so once I click on a link to go to
http://elog.blah.internal/Server_Logbooks it just shows the same index1.html
selection page. So I never get to the actual logbook list...
I could make separate selection pages for each top logbook group,
but that means that I have to alter those HTML files every time I add or
remove a logbook. I'd ruther have ELOG generate those pages on the fly.

Is there any way to do this?
Could I tell ELOG not to use a selection page at all for a particular group
of logbooks, and just show the logbook list.

Thank you very much.

GL.

//ELOG on FreeBSD 5.2//

> The problem I have is I want to have a main selection type page so when a
> user enters ELOG they see this page with links on it to main logbook groups.

I added a new flag

Show top groups = 1

which shows the list of to groups. Hope this is what you want. The new version
is available from CVS (see download page).

Great! That takes care of the problem for sure.

Cheers once again for such a quick response.

GL.


//we use ELog very extensively internally, it's great, especially now with
replication//


> > The problem I have is I want to have a main selection type page so when a
> > user enters ELOG they see this page with links on it to main logbook groups.
> 
> I added a new flag
> 
> Show top groups = 1
> 
> which shows the list of to groups. Hope this is what you want. The new version
> is available from CVS (see download page).

Hi,

Is it possible to restrict the display of logbook entries to the entries 
created by the currently logged-in user?

I'm thinking of using the ELOG system in a school laboratory environment: 
students must write entries in the logbook about their excersises, but I 
would like that students can not "see" what other students have written. To 
make it even more complicated, I would like that students can see their own 
entries and the teacher entries.....

Is something like this possible?

Thanks in advance
Bartjan Wattel
the Netherlands

One way would be to create a seperate logbook for each student including the
teacher. It should then be fairly simple to set up the permissions however you
would like. For a large class it might be a bit cumbersome to set it up this way.
 
Ralph Kuehn

> Hi,
> 
> Is it possible to restrict the display of logbook entries to the entries 
> created by the currently logged-in user?
> 
> I'm thinking of using the ELOG system in a school laboratory environment: 
> students must write entries in the logbook about their excersises, but I 
> would like that students can not "see" what other students have written. To 
> make it even more complicated, I would like that students can see their own 
> entries and the teacher entries.....
> 
> Is something like this possible?
> 
> Thanks in advance
> Bartjan Wattel
> the Netherlands

> For a large class it might be a bit cumbersome to set it up this way.

What you can do is put most of the configuration options into the [global] section,
such as

[global]
Attributes = ...
Password file = ...
...
Admin user = teacher

[John]
Login user = john
[Joe]
Login user = joe
[Fred]
Login user = fred

In this case, each logbook only requires two lines, while all the other options are
inherited from the [global] section. The "login user" restricts logins only to a
single student, which the teachis has admin rights for all logbooks. The teacher can
reply to individual students by writing into their "personal" logbook, or he can set
up a dedicated teacher logbook which everybody can read (Just omit the 'login user').