ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66025
|
Thu Oct 30 04:28:05 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2130 | Re: Standard login Screen - bottom text |
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 = ..." |
66024
|
Thu Oct 30 04:17:09 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.5-2130 | Re: (How) can I hide columns in List view? |
T. Ribbrock wrote: |
Originally, all information about our machines was stored in a spreadsheet with one sheet for the hardware of the machines and one for the software. By now, I've sucessfully moved the software part to an elog logbook and am now looking at transferring the hardware part as well.
As both lists are machine-name based, one of the options would be to merge both lists, as this would place all machine-related info into one logbook. The downside of this is that I get so many columns in list view that the result is quite unwieldy. Hence, I would like to hide some columns - ideally creating a "hardware view" and a "software view".
From the documentation, the only option I could find that seemed suitable was "List conditions". Unfortunately, I do not quite understand from the manual how this is supposed to work, so I'm quite possibly doing something wrong. I've tried this:
; General settings
List conditions = 1
; Attributes
Attributes = Type, Created, StatusA, StatusB, Archived
; Options & Tooltips
Options Type = Type1{10}, Type2{11}
; Conditionals
{10}List display = Edit, Type, Created, Status
{11}List display = Edit, Type, Created, StatusA, StatusB, Archived
but no matter how I set "Type", it does not seem to have any effect on the List display. One thing I don't understand for example is how does elog decide in List view which entry sets the condition? If all entries are set to the same value (in this example e.g. "Type1")? The first entry? Or am I missing something altogether? 
Also, if there are alternative ways how I could accomplish my goal, I'd also be most grateful for suggestions.
Thanks in advance,
Thomas
|
Indeed you got something wrong. The conditional attributes are meant for the input form, so you can turn some attributes on and off or choose different options for an attribute depending on the value of another attribute.
The only way I see how you can achieve what you want is to define two separate logbooks, but serve them from the same directory (via the "Data dir" option). Both logbooks should share the same attribute definition, but use different "List display" options. |
66023
|
Thu Oct 30 03:30:59 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5 | Re: Server derived time |
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. |
66022
|
Thu Oct 30 03:10:00 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.5-2130 | Re: elogd crashes when creating new logbook using existing logbook as template | > elogd is crashing with a segv when I try to create a new logbook by clicking the "Create new logbook" button
> with an existing logbook selected in the dropdown list as a template. I've attached my config file for
> reference. As a specific example, I'm logged in as the admin user, viewing logbook "1248", which has no entries,
> and I click "Config" -> "Change config file" -> "Create new logbook", Select "1248" from dropdown list, enter
> "1250" for the new logbook name, and click "Create new logbook".
>
> The server crashes, and my web browser has the following as the (incorrect) URL it's trying to load:
> (Incorrect because the "/ATLAS" shouldn't be there.)
>
> https://localhost:8080/ATLAS/1250/?cmd=Config
>
> Nevertheless, the config file and logbook directory are properly modified for the new logbook, and on restarting
> the server, everything is fine.
>
> Oh, just noticed that if I manually enter the URL:
>
> https://localhost:8080/ATLAS/1250/
>
> or actually, any text in place of the "1250", it also crashes the elogd process. So, perhaps there are two bugs?
>
> (1) Incorrect URL being given to the web client after logbook creation
> (2) Requesting any incorrect URL of this form crashes elogd
This problems have been fixed in SVN revision 2135. |
66021
|
Wed Oct 29 07:07:47 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.5 | Re: Elogd crashes |
soren poulsen wrote: |
Dear Stefan,
Thanks for your reply.
I started running elog in February and it never failed. Then it started failing regularly towards the end of September. There were no system changes until then, except the daily automatic Yum updates (SLC4). Then I upgraded to the latest version (tar ball of 2.7.5). Then yesterday it crashed again. I saw that it crashed around the time when a user was doing something - inputting new data. I can monitor when it crashes and correlate it with user activity. But it is not easy to reproduce since I don't know exactly what the user is typing.
It would be necessary to record the user input forms and then replay them against a known server state. But that is not so easy.
I will think about doing something else - maybe running inside a debugger as you suggest.
|
Just run it inside gdb. When it crashes, you will see a segment violation and you will end up at the debugger prompt. Then do a "bt" to see the stack dump. From that I can guess where the problem happens.
|
66020
|
Wed Oct 29 05:53:39 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.5 | Re: Installation problems | > 1) "make" fails if libssl-dev package is not installed. Documentation does not mention SSL library requirements.
I added a note to the documentation, thank you.
> 2) /etc/init.d/elogd: line 10: /etc/rc.d/init.d/functions: No such file or directory (I fixed this by commenting
> out that line).
>
> 3) Starting elogd: /etc/init.d/elogd: line 34: echo_success: command not found (Fixed by search/replace "echo_"
> to "echo ").
The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the
typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package
which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian
updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then
one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain. |
66019
|
Wed Oct 29 05:41:02 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Guest Account doesnt work |
Brassmann wrote: |
Hi ,
i have a little problem with the guest access. There is no acces to the logbooks as a guest. Evereytime i see the loginbox after clicking the logbook.
[Informations] Guest menu commands = List, Back, Find, Login, Help Guest find menu commands = List, Find, Select, Login, Help Password file = ./passwd Self register = 1 Logfile = elogd.log Logging level = 3 Login expiration = 24 Admin user = testuser
Theme = default Preset Author = $long_name Attributes = Author, Subject Locked Attributes = Author Required Attributes = Author, Subject Page Title = ELOG - $subject Reverse sort = 1 Quick filter = Date, Subtext
Thanks for help, Brassmann
|
I tried your configuration and it worked as expected. Maybe you have edited the wrong configuration file, not restarted the server, or have an old page in your browser cache. |
66018
|
Wed Oct 29 05:35:05 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2130 | Re: Error Message in HTML or Java Script alert |
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? |
|