|
|
|
Demo
Discussion
|
|
Forum
Config Examples
Contributions
Vulnerabilities
|
| Discussion forum about ELOG, Page 48 of 806 |
Not logged in |
 |
|
|
|
|
Re: Automatic Export, posted by Tim Fowler on Fri Jan 28 18:04:03 2005
|
> > Is there any way to automatically export the logbook(s)?
>
> Kind of. You can use "wget" under Linux (use cygwin under Windows to get wget
> under Windows). Then issue a
>
> wget "http://midas.psi.ch/elogs/forum/?cmd=Search&mode=xml"
>
> and you will get an XML export. Same works with CSV export. If you put that
> command in cron, you have this on an automatic basis.
Thanks Stefan! That was exactly what I was looking for! |
ELOG Command Line Utility, posted by Tim Fowler on Wed Feb 9 15:40:12 2005
|
I am trying to use the command line utility elog. Some of the attributes
that I have setup are multiple options. When I run the command line
utility to create a new message, any attribute that is setup with multiple
options will not be filled in. The syntax I am using is as follows:
elog -h localhost -p 8080 -l Lab -a "Site=xxxx" -a "Area=System" -
a "Priority=Low" -a "Shift=1" -a "Status=Open" -m text.txt
Site and Area are defined in the config file as MOptions. Is there a way
to use this feature with multiple options on attributes with the
attributes = to one or more variables? |
|
Re: changing the default to plain text rather than elcode, posted by Tim Fowler on Thu Jul 7 02:41:40 2005
|
| Stefan Ritt wrote: |
| John Habermann wrote: | | I just shifted our elogs to a new server and in the process upgraded to the latest debian version which is 2.5.9+r1674-1. I am just wondering how to change the default for the text body area from "elcode" to plain text? I can't see anything in the admin configuration syntax guide and the HTML default = 2 option no longer seems to work. |
The HTML default option has been replaced by the Default encoding option, with which one can set the default encoding style to plain text (Default encoding = 1).
| John Habermann wrote: | | Also is there anything in particular that you have to do to get the elcode editor to work. Although the elcode buttons appear highlighting text and clicking on them doesn't actually do anything although it works fine in my browser when using these elog forums. I don't get any errors in mozilla but trying it in IE under cxoffice gives an "error on page" message in the bottom of the browser. |
The ELCode editor requires the JavaScript file elcode.js to be present in the scripts directory under your elog root directory. Future installations will handle this correctly. |
The installation did not include scripts directory. Where can I download the elcode.js file? |
|
Re: changing the default to plain text rather than elcode, posted by Tim Fowler on Thu Jul 7 22:31:40 2005
|
I said future installations will handle this. This feature is still in beta becaus it's not finished completely. You can get the elcode.js from CVS.
- Stefan |
Thanks Stefan! This is an excellent application. |
|
Elogd.exe crashes on windows, posted by Tim Fowler on Thu May 4 16:01:29 2006
|
I have elog setup to send emails based on the priority of one of the attributes. When a new entry is created, the emails are sent successfully, however if the entry is edited or if you changed the attribute, elogd.exe will crash with a memory access error.
I have tried this and received the same results on different computers and different versions on Elog down to versions 2/6.0 beta 5. (it works correctly in that version).
The attribute in question is setup something like below:
Attributes = Ticket #, Site, Shift, Type, Area, System Name, Description, Priority, Status, Total Down Time, Last Revision
...(omitted config)
Options Priority = High, Medium, Low
...(omitted config)
Use Email Subject = $Site -- $System Name $Description
Use Email From = testuser@myexample.com
;Send email if priority is set to high
Email Priority High = testuser2@myexample.com
Display Email recipients = 1
Email Format = 14 |
test, posted by Tim Schel on Wed Mar 25 10:36:15 2015
|
zezerze |
Strange browser behaviour with chrome?, posted by Tim Schel on Mon Mar 30 14:46:28 2015 
|
Hello there,
I have been using ELOG for 4 years now and all of a sudden I see a strange behaviour.
As you can see in the screenshots below I have configured 6 logbooks (tabs) ... only 2
display (colors in CSS?) correctly as configured.
There haven't been any changes recently configuration wise .. but I suspect my chrome
has been upgraded silently.
Any ideas why one logbook (see screenshot 2) called Kandidaten would display
correctly and the other called DSP doesn't?
The first screenshot displays all rows in blue and purple letters ....
The Logbook Stagiairs even has multiple behaviours .... some of it sub books display correctly
and some don't.
I have a new colleague since a few days who uses the ELOG as well but using Internet Explorer
and she doesn't have this strange behaviour. I can rule out configuration error since
I stripped configuration and added verbosity logging level up and nothing was detected.
Is this possible solely due to chrome update (of which I am not even sure).
I looked at the CSS source of both screenshots and I notice that in the first case (wrong!)
there is no CSS class attributed to the TD elements.
Anyway I can understand that the browser displays everything wrong ... but this behaviour
I cannot explain. |
|
Re: Strange browser behaviour with chrome?, posted by Tim Schelfhout on Wed Apr 1 11:01:14 2015
|
Thank you all of you for your notes ...
Anyway I have no time at the present to debug this ... at the level of configuration file.
I discovered however that the Incognito Mode of Chrome does NOT seem to have this problem??
Chrome version is 41.0.2272.101
Don't know why ??? ... tried disabling all of the added extensions in chrome but to no avail.
Don't know what else can be different in both modes.
| Andreas Luedeke wrote: |
| Stefan Ritt wrote: | The (correct) display tells me that the colours are user-defined, probably by the configuration option
Style <attribute> <value> = <style>
which selects different styles for different rows. Now I do not know why your browser should change behaviour all over sudden, but I would double check the configuration. Like removing all style additions in the config file, then try again, then add one by one. There could also be a class defined with the "style" option which has not been added to the default style file themes directory of the elog installation.
Stefan |
Just my two cent:
the content of a particular entry can change the rendering. If you have an HTML end tag like </table> or </font> in your entry, then the display after that entry may be spoiled.
You could try to select the very same entries in both browsers, to see if it does depend on the specific entry content.
If the problem persists, then I would suggest that you post the following:
- a minimal configuration for a logbook that reproduces the problem; and
- the actual entries, exported in XML or RAW format; and
- screenshots on how it displays with IE (add version number) and with Chrome (add version number).
Cheers
Andreas |
|