Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
icon5.gif   XML import Error, posted by Donald on Thu Feb 27 15:15:55 2014 new__2.xml
    icon2.gif   Re: XML import Error, posted by Andreas Luedeke on Mon Mar 3 15:42:29 2014 
       icon2.gif   Re: XML import Error, posted by Donald on Tue Mar 4 19:48:02 2014 new__2.xml
          icon2.gif   Re: XML import Error, posted by Donald on Tue Mar 11 15:17:36 2014 
Message ID: 67670     Entry time: Mon Mar 3 15:42:29 2014     In reply to: 67669     Reply to this: 67671
Icon: Reply  Author: Andreas Luedeke  Author Email: andreas.luedeke@psi.ch 
Category: Question  OS: Windows  ELOG Version: 2.9.2-2475 
Subject: 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.

ELOG V3.1.5-fe60aaf