Also having the ability to subscribe to notifications for one or more 
logbooks (if access is given - along with the ability to choose which 
categories, etc notifications are sent.


> Couple Wish List Items for the Self Register:
> 
> -allow the user to pick which type of log entries (which categories, etc) 
> they would like to subscribe to and receive notifications on.   
> 
> -Option to use an existing LDAP database to authenticate users instead of 
> maintaining a password file.

Is it possible to make the author and pwd check case in-sensitive??  I 
noticed that unless you type your userid and password in the same case each 
time, the system doesn't recognize your or thinks the info is invalid.

thanks,
eric

Some options for the password setting:
The ability that if admin creates a temporary password for the user, force 
the user to change the password once logged in.

User forgets password, system generates a random pwd and sends it to user 
via email, after they log in force pwd change. 

option to expire an account or expire a pwd after so many days??

just some ideas..

still loving the new features!!

> Is it possible to make the author and pwd check case in-sensitive??  I 
> noticed that unless you type your userid and password in the same case each 
> time, the system doesn't recognize your or thinks the info is invalid.
> 
> thanks,
> eric

Well, that's how it should be. All other systems I know like Windows NT 
Login, Linux login etc. are case-sensitive, so we should follow that standard.

> Some options for the password setting:
> The ability that if admin creates a temporary password for the user, force 
> the user to change the password once logged in.
> 
> User forgets password, system generates a random pwd and sends it to user 
> via email, after they log in force pwd change. 
> 
> option to expire an account or expire a pwd after so many days??
> 
> just some ideas..
> 
> still loving the new features!!

Ok, put on the wish list.

Hi,

I am having trouble modifying the elog client to allow larger attachment.  I
have elogd configure for attchment sizes of 10Meg and I would like the
option to be able to use the elog client.  Can anyone give me key points as
to how to go about doing this?  I have tried but I must be missing something.

Also, as a suggestion, it might make sense to add a MAX_ATTACHMENT_SIZE def
in a common header file.

Thanks
Kevin

> Hi,
> 
> I am having trouble modifying the elog client to allow larger 
attachment.  I
> have elogd configure for attchment sizes of 10Meg and I would like the
> option to be able to use the elog client.  Can anyone give me key points 
as
> to how to go about doing this?  I have tried but I must be missing 
something.
> 
> Also, as a suggestion, it might make sense to add a MAX_ATTACHMENT_SIZE 
def
> in a common header file.
> 
> Thanks
> Kevin

I modified the elog program such that the attachment buffer is dynamically 
allocated which means that it works with any size. Please find the updated 
version at

http://midas.psi.ch/cgi-bin/cvsweb/~checkout~/elog/elog.c?rev=1.10

Note that for attachments larger than ~2MB, one hase to increase the 
WEB_BUFFER_SIZE in elogd.c.

- Stefan

I noticed a long url got hard-wrapped when I entered a long one, I patched 
the source code. I don't know if this was done intentionally, otherwise you 
might want to change this also.

diff elogd.c elogd.c.org 
4468c4468
<     rsprintf("<textarea rows=20 cols=%d wrap=soft name=Text>", width);
---
>     rsprintf("<textarea rows=20 cols=%d wrap=hard name=Text>", width);

BTW, why is the editor window 20 rows by 76 columns ?
(20 is fixed in the source code, but 76 is the width-variable that is set 
hard to:

  /* set textarea width */
  width = 76;

Now I don't like both parameters. 20 is too long for my display (1024x768) 
and 76 is too short. Something dynamically would be cool, but a parameter 
somewhere in a config file would also be acceptable. (just a thought, makes 
it easier to upgrade)