Server derived time, posted by Grant Jeffcote on Thu Oct 23 10:21:06 2008
|
Hi Stefan,
Is it possible to derive the time in a 'date/time' attribute from the Elog server?
We would like all our entries in GMT/UTC time and unfortunately as the time is currently derived from the client machines there are often entry descrepancies if the regional settings are not set correctly.
The '$entry time' variable can be used but seems to put a 1970 date in the field so bears no relevancy to an 'Event' time?
I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?
Hope that makes a little sense?
Many thanks |
Re: Error Message in HTML or Java Script alert, posted by Stefan Ritt on Wed Oct 29 05:35:05 2008
|
Carsten Elftmann wrote: |
I have there a problem with the error message at required attributes.
I have two logbooks with identical settings,
in one the errror message appears as Javascript Alert,
in the other one as html-page, and after using the back button the entered text disapear.
Same I have in this forum.
|
Can you describe what you exactly enter in this forum to produce the error so that I can reproduce it? |
Re: Server derived time, posted by Stefan Ritt on Thu Oct 30 03:30:59 2008
|
Grant Jeffcote wrote: |
Hi Stefan,
Is it possible to derive the time in a 'date/time' attribute from the Elog server?
We would like all our entries in GMT/UTC time and unfortunately as the time is currently derived from the client machines there are often entry descrepancies if the regional settings are not set correctly.
The '$entry time' variable can be used but seems to put a 1970 date in the field so bears no relevancy to an 'Event' time?
I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?
Hope that makes a little sense?
Many thanks
|
There are several methods to get the server time:
Via presets of attributes
Attributes = Author, Event time, ...
Preset Event time = $utcdate
which gives you actually the UTC time.
Via the editor
The editor toolbar contains a little clock. If you click on it, you insert the current server time (but localized, not UTC).
Hope one of the two methods work for you.
The problem with the conditional attributes in the find page is I believe fixed in the current version. |
Re: Standard login Screen - bottom text, posted by Stefan Ritt on Thu Oct 30 04:28:05 2008
|
Barend wrote: |
Hi Stefan.
I have been "playing" around with this great tool and found an interesting "issue" ...
I use multiple logbooks and have both "Protect Selection page = 1" and "Expand Selection Page = 1".
When I open my elog, I get a Standard Login Screen with the Standard Bottom Text "ELOG V2.7.5-2130" which will link to your this website.
When I "Logout" and "Login" again from the Logbook page, I get another Login Screen with my own "Bottom text login" which will link to my own elog page.
How can I apply my own Bottom Text to the Standard Login Screen ?
Thanks & Regards, Barend
|
By using the configuration option "Bottom Text Login = ..." |
Re: Server derived time, posted by Grant Jeffcote on Thu Oct 30 08:39:34 2008
|
Stefan Ritt wrote: |
Grant Jeffcote wrote: |
Hi Stefan,
Is it possible to derive the time in a 'date/time' attribute from the Elog server?
We would like all our entries in GMT/UTC time and unfortunately as the time is currently derived from the client machines there are often entry descrepancies if the regional settings are not set correctly.
The '$entry time' variable can be used but seems to put a 1970 date in the field so bears no relevancy to an 'Event' time?
I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?
Hope that makes a little sense?
Many thanks
|
There are several methods to get the server time:
Via presets of attributes
Attributes = Author, Event time, ...
Preset Event time = $utcdate
which gives you actually the UTC time.
Via the editor
The editor toolbar contains a little clock. If you click on it, you insert the current server time (but localized, not UTC).
Hope one of the two methods work for you.
The problem with the conditional attributes in the find page is I believe fixed in the current version.
|
Thanks Stefan, the preset UTC date works well. RTFM on my part perhaps. 
I'm running version 2.7.5.2127 and am still having the issue with conditional attributes in the find area as mentioned above though.
Is it the latest SVN **.2135 that addresses this?
Many thanks |
Re: Standard login Screen - bottom text, posted by Barend on Thu Oct 30 21:14:32 2008
|
Stefan Ritt wrote: |
Barend wrote: |
Hi Stefan.
I have been "playing" around with this great tool and found an interesting "issue" ...
I use multiple logbooks and have both "Protect Selection page = 1" and "Expand Selection Page = 1".
When I open my elog, I get a Standard Login Screen with the Standard Bottom Text "ELOG V2.7.5-2130" which will link to your this website.
When I "Logout" and "Login" again from the Logbook page, I get another Login Screen with my own "Bottom text login" which will link to my own elog page.
How can I apply my own Bottom Text to the Standard Login Screen ?
Thanks & Regards, Barend
|
By using the configuration option "Bottom Text Login = ..."
|
Stefan,
I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.
Barend
|
Re: Standard login Screen - bottom text, posted by Stefan Ritt on Mon Nov 3 07:33:08 2008
|
Barend wrote: |
Stefan,
I have defined the "Bottom Text Login = ..." in each Logbook Configuration section. But when I use this option in the Global Section, ELOG fails to start.
Barend
|
That's strange. I just tried myself following configuration file:
[global]
port = 8080
Bottom text = <center>Hello</center>
Bottom text login = <center>Login Hello</center>
Password file = passwd
[demo1]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Page Title = ELOG - $subject
[demo2]
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
and everything works fine as can be seen from the login screen:

so can you check if above file works for you? |
Re: Server derived time, posted by Stefan Ritt on Mon Nov 3 13:15:52 2008
|
Grant Jeffcote wrote: |
I'm also having issues with conditional entries in the Find page. If a conditional statement is used to hide attributes or change displayed attributes in the entry page then the attribute that is used in the conditional statement is not permanently selectable in the 'Find' page. It is available as a choice but as soon as selected the conditional action removes it? Is it possible to make conditional options/actions in the 'Find' page optional?
Hope that makes a little sense?
Many thanks
|
Many people want conditional attributes on the find page, so I cannot remove it. Before adding another parameter to disable this optionally, I would like to ask you to first try the "Show attributes edit = ..." option, which is not evaluated in the "find" page. Maybe you can achieve what you want with this option. |