Adaptation of the language, posted by Markus Grosse-Kock on Thu Feb 20 12:27:42 2014
|
Hello,
I want to change the language to German. But it does not work.
Here my config:
Theme = default
Resource dir = D:\Elog
Language = german
Where is the problem? Or is it not possible to change the language in Windows?
Best regards,
Markus
|
Re: Adaptation of the language, posted by Stefan Ritt on Thu Feb 20 16:36:06 2014
|
| Markus Grosse-Kock wrote: |
|
Hello,
I want to change the language to German. But it does not work.
Here my config:
Theme = default
Resource dir = D:\Elog
Language = german
Where is the problem? Or is it not possible to change the language in Windows?
Best regards,
Markus
|
You put the "Language = german" statement into the logbook section, but it has to be placed in the [global] section as written in the documentation. Unfortunately this section of the configuration file cannot be accessed through the web interface, so you have to edit the elogd.cfg file manually, which might require admin rights.
Viele Grüsse nach Reken,
Stefan |
Re: Adaptation of the language, posted by Markus Grosse-Kock on Thu Feb 20 17:37:06 2014
|
| Stefan Ritt wrote: |
|
| Markus Grosse-Kock wrote: |
|
Hello,
I want to change the language to German. But it does not work.
Here my config:
Theme = default
Resource dir = D:\Elog
Language = german
Where is the problem? Or is it not possible to change the language in Windows?
Best regards,
Markus
|
You put the "Language = german" statement into the logbook section, but it has to be placed in the [global] section as written in the documentation. Unfortunately this section of the configuration file cannot be accessed through the web interface, so you have to edit the elogd.cfg file manually, which might require admin rights.
Viele Grüsse nach Reken,
Stefan
|
Danke, hat funktioniert.
Gruß Markus |
|
Re: Unable to resize images in browser, posted by Stefan Ritt on Fri Feb 21 13:09:48 2014
|
| Matthew Deller wrote: | I am unable to resize/ manipulate images in browser. Image Magick detected Version: ImageMagick 6.6.9-7 2012-08-17.
Output when running elog with verbose option shows buffer overflow when resize attempted:
[[Going to execute: /bin/sh -c "identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png'" > /tmp/elog-shell 2>&1
Falling back to default group "elog"
Falling back to default user "elog"
*** buffer overflow detected ***: elogd terminated
Any ideas how to fix this? I'm not sure if this is a problem with the elog / Ubuntu / Image Magick? |
What happens if you execute the command manually, like
$ identify -format '%wx%h %c' '/home/elog/elog-2.9.2/logbooks/HardwareLog/140218_120423_2014-02-18_remod_(extended_II).png.png
The "identify" command just checks the size in pixels of your image and expects something like 800x600. Let me know if this command returns something completely different.
/Stefan |
|
Re: Google Places API AutoComplete, posted by Stefan Ritt on Fri Feb 21 13:43:03 2014
|
| Garret Delaronde wrote: |
|
G'day everyone.
Looking for some input on this idea.
I work for an organization which uses elog extensively for day to day operations.
In several of our logbooks we use a "location" attribute where we would enter an address or intersection.
I am working with the google places api and am able to create the auto complete form in a separate html page, but am interested if anyone has a good direction how i could change the input box into the google map autocomplete search box.
I have the code already for the api search box. but when i add it to the config it doesn't really do anything different.
Attached is the html file i setup with the api code.
the autocomplete works great, now i just want it to work in elog.
Any help is much appreciated!
And perhaps the Elog Powers that be might be interested in making it a function down the road? :)
|
Looks like a nice idea. You can sneak in any JavaScript code into elog pages with the "Top text" option. Like
Top text = <script>window.onload = function() {...}</script>
Then you parse the DOM tree to find your input field for the location, and attache your JS code to it. All the input fields have the "name" attribute in the HTML code set, so it should be easy to find the input field in the DOM tree.
/Stefan
|
XML import Error, posted by Donald on Thu Feb 27 15:15:55 2014 
|
Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type |
|
Re: XML import Error, posted by Andreas Luedeke on Mon Mar 3 15:42:29 2014
|
| Donald wrote: |
|
Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type
|
Hi Donald,
yes, the import function gave me some headache in the past, too.
⇄
English (auto-detected) » English
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)
I hope this helps. |
|
Re: XML import Error, posted by Donald on Tue Mar 4 19:48:02 2014
|
| Andreas Luedeke wrote: |
|
| Donald wrote: |
|
Hi
I've written a powershell script parse a html table that contains old log book data that i would like to import to a elog book. I've attached a example of the output.
When i attempt a import i get this error
"XML file does not contain <ENCODING> element"
The file does contain an encoding for utf-8 I've tried converting the xml to ANSI and ISO-8859-1 encodings but i get the same error.
is there something obvious that I'm missing?
here is the config of the log book:
[WLTST]
Theme = default
Comment = Test Logbook
Attributes = Author, Object, Action
Comment Author = Username
Comment Action = What
Comment Text = Why
Required Attributes = Author, Object, Action, Text
Page Title = Test Logbook
Reverse sort = 1
Quick filter = Date, Type
|
Hi Donald,
yes, the import function gave me some headache in the past, too.
⇄
English (auto-detected) » English
Here it appears that <ENCODING> </ENCODING> became somehow mandatory. But it has a different meaning then what you expect: it is the type of code in the text field, one out of HTML, ELCode or plain.
(Stefan: is this needed to be mandatory? Couldn't you just have some default ?)
In your case: you can just add the XML code "<ENCODING> </ENCODING>" before the <TEXT> token.
My problems were always related to the date format: elogd is very restrictive about what date format it is accepting. that will be your next pproblem ;-)
I hope this helps.
|
Hi Andreas
That worked, thank you so much. now I'm on to a new error.
Now every time i try to do the import it crashed the elogd.
OS is windows server 2008 R2. I have the elogd installed as a service.
here is the even log:
Faulting application name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Faulting module name: elogd.exe, version: 0.0.0.0, time stamp: 0x51248707
Exception code: 0xc0000417
Fault offset: 0x000682da
Faulting process id: 0x558
Faulting application start time: 0x01cf37d8870fc9a1
Faulting application path: D:\Program Files (x86)\ELOG\elogd.exe
Faulting module path: D:\Program Files (x86)\ELOG\elogd.exe
Report Id: defc3f39-a3cb-11e3-9dd5-005056954c86
I have attached the Data file I'm using to generate the fault every time. same config as before. Any Ideas?
|
|