> Is there a way to hide logbooks from all views.
> 
> Basically i want to use the move function to move old entries to another 
> logbook but only want administrators to be able to see the logbooks in the 
> view, everyone will just see the primary ones.
> 
> At the min im having to put Archive logbook, everyone is complaining at me 
> that there is too many to choose from :)
> 
> Any suggestions ?

What about grouping the archive logbooks into a logbook group? Like:

Group Pubilc = Logook1, Logbook2, ...
Group Archive = Archive1, Archive2, ...

So if a "normal" user is in the public group, it only sees Logoook1, ... and 
a single tab "archive", which is then (I hope) not too much to choose from.

Is there a way to hide logbooks from all views.

Basically i want to use the move function to move old entries to another 
logbook but only want administrators to be able to see the logbooks in the 
view, everyone will just see the primary ones.

At the min im having to put Archive logbook, everyone is complaining at me 
that there is too many to choose from :)

Any suggestions ?

> > I am using 2.3.4 and I am still having this problem.  If someone posts a
> > message with an attachment, and I then reply to that message, the 
attachment
> > gets 'deattached' from that message.  However, the file is still in the
> > logbook directory, so it is possible to recover it, but it did cause a 
> slight
> > panic the first time it happened :)
> 
> Uups, that is indeed a problem. I found that it was unrelated to the first 
> one, so it was there since quite some time now. I fixed it. It will come 
out 
> in 2.3.6 or can be obtained already now from CVS. It is trongly recommended 
> to upgrade all installations to avoid this problem.

Just as a test, I reply to my previous message... looks like it works.

> I am using 2.3.4 and I am still having this problem.  If someone posts a
> message with an attachment, and I then reply to that message, the attachment
> gets 'deattached' from that message.  However, the file is still in the
> logbook directory, so it is possible to recover it, but it did cause a 
slight
> panic the first time it happened :)

Uups, that is indeed a problem. I found that it was unrelated to the first 
one, so it was there since quite some time now. I fixed it. It will come out 
in 2.3.6 or can be obtained already now from CVS. It is trongly recommended 
to upgrade all installations to avoid this problem.

I am using 2.3.4 and I am still having this problem.  If someone posts a
message with an attachment, and I then reply to that message, the attachment
gets 'deattached' from that message.  However, the file is still in the
logbook directory, so it is possible to recover it, but it did cause a slight
panic the first time it happened :)

I see there is a 2.3.5 version now, but the changelog doesn't say anything
about this problem, so I have not tried it yet.

Is there a 'trick' to fix this problem?

EDIT: I noticed when I replyed to your message, your elog.cfg attachment is
no longer there.  So it appears it's not fixed in 2.3.5 either..


> This is a known problem and has been fixed in version 2.3.4, which has been 
> released today. To prove that it's working, I attached the current 
> elogd.cfg from this forum.

> Error sending Email 
> Please use your browser's back button to go back  

This error is caused if elogd cannot contact your SMTP server for sending 
email. Can you please check the "SMTP host" entry in the configuration file?

> Is there a way to convert all the hashes from one system to another, the 
> problem ive got is my password files are quiet large and want upgrades of 
> this nature to go seemlessly without people complaining about it.

Unfortunately not. The old system had a bug which deleted the last one or two 
characters, if the password length was dividable by three. Since the 
characters were deleted, there is no way to reconstruct the full password. I 
apoligize for the inconveniences, I know that this can cause lot of trouble, 
but therefore I implemented the "Forgot password?" functionality, so that 
users can log in again. Alternatively, one can edit the password file, delete 
all passwords, and ask the users to log in without password and change it 
afterwards immediately.

> > Forgot password option generates an error message
> 
> Which error? Can you be more specific. I tried it myself with this forum 
and 
> it worked for me.

Error sending Email 
Please use your browser's back button to go back  

HTTP/1.1 200 Document follows Server: ELOG HTTP 2.3.5 Content-Type: 
text/html;charset=iso-8859-1 Connection: Keep-Alive Keep-Alive: timeout=60, 
max=10 
User name "nickc" not registered 
Please use your browser's back button to go back  

Yet nickc is in the password file, it generates the same message for any 
other users in there too.


> 
> > Password file hashes are different causing migrated password files to 
fail 
> > but only for certain users, try password 516135 hashed in 2.3.4 and 
compare 
> > to version 2.3.5 they are different.
> 
> Yes indeed. Please see elog:273 for more details

Is there a way to convert all the hashes from one system to another, the 
problem ive got is my password files are quiet large and want upgrades of 
this nature to go seemlessly without people complaining about it.

> 
> > Summary page title = string doesnt work also it results in the default 
ELOG 
> > DB Name
> 
> Thanks, has just been fixed, new version under CVS.
> 
> - Stefan
Ta

> Forgot password option generates an error message

Which error? Can you be more specific. I tried it myself with this forum and 
it worked for me.

> Password file hashes are different causing migrated password files to fail 
> but only for certain users, try password 516135 hashed in 2.3.4 and compare 
> to version 2.3.5 they are different.

Yes indeed. Please see elog:273 for more details

> Summary page title = string doesnt work also it results in the default ELOG 
> DB Name

Thanks, has just been fixed, new version under CVS.

- Stefan