is there a way to set up a logbook so that a password is required to get
into it, but no username?

> > is there a way to set up a logbook so that a password is required to get
> > into it, but no username?
> 
> Have a look under "Access control" in the manual. What you need is "Read
> Password".

thanks. that seems to get me the functionality i needed. is there any way to
get rid of the username line when using the "Read Password" feature? as it is
now, you can either leave it blank or enter anything you want, so long as you
use the correct password it still works. however, to keep users from getting
confused, i think it would be better to only have a box asking you for the
password and not both the password and username.

there is a guide on the contributions logbook at

elog:Contributions/11

for securing Elog using SSL and Apache.

is there any way to get a larger text box to type in when making a new post?
the default box is rather small and you have to scroll up and down when
making a new post or editing an existing one.

once the post is submitted, the display goes to a larger box, but the text
only takes up the left side of the page. seems the only way to get it to go
all the way to the right is to make everything html and submit it that way.

can the normal text look like the html does without submitting it as html?

> > is there any way to get a larger text box to type in when making a new post?
> > the default box is rather small and you have to scroll up and down when
> > making a new post or editing an existing one.
> 
> Message width = <number of characters>
> Message height = <number of lines>
>  
> > can the normal text look like the html does without submitting it as html?
> 
> No. 

thanks stefan. it looks like it was right in front of my face the whole time (on
the elogd.cfg syntax page). but, somehow i missed it.

We are exploring whether it's possible/feasible to import ELog logbooks into a another database for special purposes (plotting/statisical, etc). Target database is TBD (perhaps Access).

Does anyone have or know of a logbook parser program? From cut/pasting into, for example, Excel, it does appear that the data fields are already line-feed delimited so offhand it would seem possible to parse if one really wanted to pursue it.

Regards,

- Alan

Hello Stefan.

Currently this is defined as a maximum of 100 literals in the cfg file. I would like to see the option to reference an external text file as input for this. 

As a side question, I would also like to increase the max to a greater value, for example, even 5000. I assume I can change the source (I recall var was something like "List_Option_Max") and see if that would still work, but would you know offhand if that would cause a problem anywhere else?

Regards,

Alan

(PS: Just getting started with ELog. Please excuse if these questions sound newbie. I also searched the Forum first but haven't found any answers to them yet.)