ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66297
|
Fri Apr 10 17:41:25 2009 |
| Hal Proctor | hproctor@mpm.com | Question | Windows | 2.7.5-2175 | Allow password change ??? | 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
|
66296
|
Thu Apr 9 13:04:51 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2185 | Re: Error Message in "Demo of database-like elog" |
mike cianci wrote: |
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
|
Thanks for reporting that bug. I fixed it in SVN revision 2188, and the fix will be contained in the next release. |
66295
|
Thu Apr 9 12:50:03 2009 |
| mike cianci | mike2.cianci@comcast.net | Question | Windows | 2.7.5-2185 | Error Message in "Demo of database-like elog" | 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 |
66294
|
Thu Apr 9 12:05:55 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V2.7. | Re: export the elog data |
urian bardulla wrote: |
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.
|
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. |
66293
|
Thu Apr 9 11:53:19 2009 |
| urian bardulla | urian.bardulla@gmail.com | Question | Windows | ELOG V2.7. | export the elog data | 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. |
66292
|
Thu Apr 9 10:52:29 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | Other | V2.7.5-213 | Re: conditional attributes | > 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. |
66291
|
Thu Apr 9 10:39:34 2009 |
| W.Koster | W.Koster@rug.nl | Request | Linux | Other | V2.7.5-213 | conditional attributes | 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). |
66290
|
Thu Apr 9 09:54:39 2009 |
| W.Koster | W.Koster@rug.nl | Question | All | 2.7.5-2168 | Re: How to configure eLog to send an e-mail notification when new logbook entry time is reached? |
Tero Suominen wrote: |
Hi! Thanks for the quick response. Do you have any suggestions on which calendar applications I should start looking for for this purpose?
Thanks,
Tero
|
You could write a shell script, run it through cron and send mail from that. (even in windows I assume)
|
|