Forgot password option generates an error message

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.

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

HELP

> > 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

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 ?

> > 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.


I tried that but on the summary screen it displays a list of all the logbook 
regardless of group, also im not using public groups im using a seperate 
password file.

> > I tried that but on the summary screen it displays a list of all the 
> logbook 
> > regardless of group, also im not using public groups im using a seperate 
> > password file.
> 
> Ah, you mean by "summary screen" the initial logbook selection screen where 
> each logbook is displayed in one line. For that case, I just added a 
> flag "Hide from selection". If set to "1", this logbook is not dispalyed 
> among the list of logbooks. Is this what you want? New version under CVS.

Yes thats wicked perfect, now im prob being thick but is there a way to hide 
logbook tabs in the same way, as i dont really want to use groups as the 
people that use the system arent really techie and the titles will confuse 
them :)

Im trying to make it idiot proof for them 

Cheers

> > Yes thats wicked perfect, now im prob being thick but is there a way to 
> hide 
> > logbook tabs in the same way, as i dont really want to use groups as the 
> > people that use the system arent really techie and the titles will 
confuse 
> > them :)
> 
> Well, I changed the flag from "hide from selection = 1" to "hidden = 1", 
> which hides it now also from the logbook selection tabs on the top row. But 
> this means that the only way to access the hidden logbooks is by entering 
> their URL directly (or from a bookmark). I'm not sure how useful this is...
> 
> New version under CVS.

Thats perfect, administrator such as myself can access those books directly 
from the URL, and can be used as an archive logbook running in sync with the 
live one, so hold records such as completed tickets in a request system once 
completed can be moved to the archive logbook.

Cheers fella  that is gonna help me a great deal.

We are using elog as a small database system, today we came across a 
problem where 2 people were editing the same record and the first one to 
submit his changes were overwritten when the second person submitted his.

Is there anyway to lock a logbook record when someone has pressed EDIT, 
maybe set a flag in the logbook entry so it has to be unlocked when its 
submitted by the originator or by an administrator.

Many Thanks

> No, but I will put it on the wishlist. Anyhow it is hard to implement 
> something like this. Assume that I would lock a page whenever it's edited 
by 
> someone. This person can edit it and forget to submit the changes, just 
close 
> the browser. Since the elogd server does not know when a remote browser 
is 
> closed, it cannot determine if the editing is just taking long or if the 
> person closed the browser. In the latter case, the message would be 
locked 
> forever and nobody could change it any more. If I put a timeout, like 
keep 
> locked for N minutes, it's again not 100% safe. I saw people doing shift 
work 
> with elog, opening a page, keeping it open for 8 hours and then submit 
it. 
So 
> if I set the timeout to 8h, and someone abandons editing a message, this 
> message would be blocked for 8h, which is probably also not what you 
want. 
> 
> Alternatively, I just can display a messge: Warning: this message is 
> currently edited by user xxx on host xxx. But if the warning is ignored 
by 
> the user, then again we have the same problem.
> 
> Do you see a clever solution to that?


I was thinking of having an icon on the page that administrator can click 
to 
unlock a record that has been left locked by someone, perhaps using 
something 
like 

Allow Unlock = admin (or even just have the option on the top like 
(Admin/Config) for administrators

Just like the delete function works, in addition to the Warning message as 
you suggested