| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67670
|
Mon Mar 3 15:42:29 2014 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 2.9.2-2475 | Re: XML import Error |
| 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. |
|
67669
|
Thu Feb 27 15:15:55 2014 |
 | Donald | don.drummel@gmail.com | Question | Windows | 2.9.2-2475 | XML import Error |
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 |
| Attachment 1: new__2.xml
|
<?xml version="1.0" encoding="UTF-8"?>
<ELOG_LIST>
<ENTRY>
<MID>
2
</MID>
<DATE>
2014-02-24 22:28
</DATE>
<OBJECT>
Archived Client:
</OBJECT>
<ACTION>
Archived Client:
Archived Client to Manual_Archive and took a full backup of it
</ACTION>
<TEXT>
ticket: 123456
Decommission of client.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
<ENTRY>
<MID>
3
</MID>
<DATE>
2014-02-20 20:15
</DATE>
<OBJECT>
Added client:
</OBJECT>
<ACTION>
Added client:
Added client to VMware policy
</ACTION>
<TEXT>
Ticket 1919191
New DHCP server needed to be backed up.
</TEXT>
<AUTHOR>
bob
</AUTHOR>
</ENTRY>
</ELOG_LIST>
|
|
67668
|
Fri Feb 21 13:43:03 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9.2 | Re: Google Places API AutoComplete |
| 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
|
|
67667
|
Fri Feb 21 13:25:55 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | All | 2.9.2-2481 | Re: Export entries to XLS or CSV? |
| Andreas Luedeke wrote: |
|
| Jim Tinlin wrote: |
|
| Stefan Ritt wrote: |
|
| Andreas Luedeke wrote: |
|
Yes, you're right: the text field is only exported in XML and Raw mode.
It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.
But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.
I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.
(This string has not yet been added to the localization.)
As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.
Of course the spreadsheet programs just display the HTML source.
Stefan, do you think this should be added to the official branch?
 ⇄
Detect language » English
⇄
Detect language » English
|
Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution.
|
Has this been added yet?
I don't have the means to create an executable for Windows, if someone does I can give it a try...it sounds/looks like it will work.
Thanks!
|
Hi Jim, I've incorporated the patch to our production server about a week ago.
I've agreed with Stefan that he'll add it, when it proved to run stable for a while.
Until now it appears to work fine. I think Stefan will add it to the distribution soon.
But I won't touch any Windows systems, you'll need to wait for someone else to compile it for you.
Maybe some skilled Windows user want to give it a try: i've attached the changes in the elogd.c file from v2.9.2-2481,
the modified file can be currently downloaded from http://people.web.psi.ch/luedeke/public/tmp/elogd.c
⇄
Detect language » English
Andreas
⇄
Detect language » English
⇄
Detect language » English
⇄
Detect language » English
|
This patch is now officially in the GIT repository. |
|
67666
|
Fri Feb 21 13:09:48 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.9.2 | Re: Unable to resize images in browser |
| 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 |
|
67665
|
Thu Feb 20 17:37:06 2014 |
 | Markus Grosse-Kock | M.Grosse-Kock@reken.de | Question | Windows | 2.9.2-2475 | Re: Adaptation of the language |
| 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 |
|
67664
|
Thu Feb 20 16:36:06 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.9.2-2475 | Re: Adaptation of the language |
| 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 |
|
67663
|
Thu Feb 20 12:27:42 2014 |
| Markus Grosse-Kock | M.Grosse-Kock@reken.de | Question | Windows | 2.9.2-2475 | Adaptation of the language |
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
|