When I try to set

Protect Selection page = 1

in the config file elog crashes. Attached is my config file.

elog 2.7.5 built Apr  8 2009, 16:52:07 revision 130

 Thats what we get for having two people working on the install and configuration.  LOL

When first creating and setting up the configs, we had  Admin Password = xxxxx  entered in each logbook config.  Once we created a password list we no longer needed that entry.

This was why each user who had login credentials was being asked to provide the admin password when trying to change their password. 

How do you allow users to change password for a given logbook when the user keeps getting prompted for admin password to enter the change password feature?

I have Allow password change = 1 set global and at each logbook hoping that would work.

It allows them to change the password when and only when the user gets past the admin login when clicking CONFIG.

help

Thanks for reporting that bug. I fixed it in SVN revision 2188, and the fix will be contained in the next release. 

I attempted to remove the text editor (like you did in "Demo of database-like elog") using  "Show text = 0".

In both your Demo and my logbook when you hit  "New"  - Explorer generates the folowing error message

        Error: The Textarea with id or name set to "text" was not found.

Is there a solution or do we just live with it.

Thanks,    Mike

Click on Find, then select Export to: ..., then click Search.  I know it's a bit hidden, but this way one can restrict the subset of entries to be exported.

Hi guys,

Is there any simple way to export the ELOG data in a more readable way, except copying the .log files????

Thank You in advance,

Urian.

> I'm (ab)using elog as a database and would like to use conditional attributes, like:
> 
> Attributes = PC Name, Operating System, Version, Distribution
> Options Operating System = Linux{1}, Windows{2}
> {1} Show Attributes Edit = Operating System, Distribution, PC Name
> {2} Show Attributes Edit = Operating System, PC Name, Version
> 
> Problem is that there are several conditions and the list of attributes is rather long. Also, since it's a
> rather dynamic environment I have to make new attributes all the time, and adding them to all "show attributes"
>  lists is not only tedious, but bound to cause errors as well.
>  
> 
> So... 
> 
> I was thinking, would it be an idea to make the list of attributes to be shown or hidden on a per attribute base.
> 
>  
> 
> Like:
> 
> Attributes = PC Name, Operating System, Version, Distribution
> 
> # hide specific attributes
> Hide attributes = Distribution, PC Name
> 
> # or configure which fields should be shown allways
> Show Attributes = Operating System, Version
> 
> # add attributes based on OS
> Options Operating System = Linux{1}, Windows{2}
> {1} Show Attribute Edit = Distribution
> {2} Show Attribute Edit = PC Name
> 
> (just thinking out loud here).

Sure such a think can be implemented, but I have no time right now to do so. I will put it on the wish list.