Zugg Software :: View topic

Beginner Joined: 17 Apr 2007 Posts: 20

Exported all my settings yesterday to XML via the export command (in windows XP). Opened the file to see that everything was ok. Saved the file and proceeded to install Windows Vista (yesh...) and installing CMUD 2.35.

My problem:

When I try and import the XML file, only 2 of the classes imports correctly. I see no trace of the other classes (they still exists in the XML file correctly).
The XML file contains 10-12(?) or more classes with all kinds of triggers and aliases, but only the two first gets imported correctly. I cannot find them in any of the class-folders either. They are missing.
Using Vista Ultimate 64-bits.

Any ideas?

P.s. I havent tried CMUD since v1.2x somewhere, so I have no idea how its supposed to work/not to work.

//Best regards

Wizard Joined: 14 Aug 2004 Posts: 1269

What version of CMUD were they exported with?

Beginner Joined: 17 Apr 2007 Posts: 20

2.34 (Could'a been 2.35 but not sure)

Wizard Joined: 14 Aug 2004 Posts: 1269

Sounds like a bug. Did you keep your package (pkg file) from XP? Maybe you can just use that for now. You'll probably need to e-mail the XML file (and pkg if you have it) to Zugg.

Beginner Joined: 17 Apr 2007 Posts: 20

Nah, I didnt keep the most recent pkg file, but I can try load a month old pkg file or so just to test.
I'll wait for Zugg to respond before I send him the file (or if he have any other ideas)

Beginner Joined: 17 Apr 2007 Posts: 20

Everything looks ok in the XML file.. is there any issues when reading this file in CMUD?

------------

This Page Is well-formed XML!
Result: Passed validation, 2 warning(s)
File:
Use the file selection box above if you wish to re-validate the uploaded file XXXXXXXXXXX\triggers.xml

Encoding: us-ascii (detect automatically) utf-8 (Unicode, worldwide) utf-16 (Unicode, worldwide) iso-8859-1 (Western Europe) iso-8859-2 (Central Europe) iso-8859-3 (Southern Europe) iso-8859-4 (North European) iso-8859-5 (Cyrillic) iso-8859-6-i (Arabic) iso-8859-7 (Greek) iso-8859-8 (Hebrew, visual) iso-8859-8-i (Hebrew, logical) iso-8859-9 (Turkish) iso-8859-10 (Latin 6) iso-8859-11 (Latin/Thai) iso-8859-13 (Latin 7, Baltic Rim) iso-8859-14 (Latin 8, Celtic) iso-8859-15 (Latin 9) iso-8859-16 (Latin 10) us-ascii (basic English) euc-jp (Japanese, Unix) shift_jis (Japanese, Win/Mac) iso-2022-jp (Japanese, email) euc-kr (Korean) gb2312 (Chinese, simplified) gb18030 (Chinese, simplified) big5 (Chinese, traditional) Big5-HKSCS (Chinese, Hong Kong) tis-620 (Thai) koi8-r (Russian) koi8-u (Ukrainian) iso-ir-111 (Cyrillic KOI-8) macintosh (MacRoman) windows-1250 (Central Europe) windows-1251 (Cyrillic) windows-1252 (Western Europe) windows-1253 (Greek) windows-1254 (Turkish) windows-1255 (Hebrew) windows-1256 (Arabic) windows-1257 (Baltic Rim)
Doctype: XML (detect automatically) XHTML 1.0 Strict XHTML 1.0 Transitional XHTML 1.0 Frameset HTML 4.01 Strict HTML 4.01 Transitional HTML 4.01 Frameset HTML 3.2 HTML 2.0 ISO/IEC 15445:2000 ("ISO HTML") XHTML 1.1 XHTML Basic 1.0 XHTML-Print 1.0 XHTML 1.1 plus MathML 2.0 XHTML 1.1 plus MathML 2.0 plus SVG 1.1 MathML 2.0 SVG 1.0 SVG 1.1 SVG 1.1 Tiny SVG 1.1 Basic SMIL 1.0 SMIL 2.0
Root Element: cmud

Potential Issues
The following missing or conflicting information caused the validator to perform guesswork prior to validation. If the guess or fallback is incorrect, it may make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

Missing "charset" attribute for "text/xml" document.

The HTTP Content-Type header (text/xml) sent by your web browser (Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506; Media Center PC 5.0; InfoPath.2)) did not contain a "charset" parameter, but the Content-Type was one of the XML text/* sub-types.

The relevant specification (RFC 3023) specifies a strong default of "us-ascii" for such documents so we will use this value regardless of any encoding you may have indicated elsewhere.

If you would like to use a different encoding, you should arrange to have your browser send this new encoding information.

No DOCTYPE found! Checking XML syntax only.

The DOCTYPE Declaration was not recognized or is missing. This probably means that the Formal Public Identifier contains a spelling error, or that the Declaration is not using correct syntax, or that your XML document is not using a DOCTYPE Declaration.

Validation of the document has been skipped, and a simple check of the well-formedness of the XML syntax has been performed instead.

Learn how to add a doctype to your document from our FAQ, or use the validator's option to validate your XML document against a specific Document Type

Congratulations
The uploaded document "XXXXXXXXX\triggers.xml" was checked and found to be well-formed XML. This means that we were not able to determine the exact document type, but that the document passed the XML well-formedness syntax check. If you wish to wish to perform formal validation of the document, you can use the "Document Type:" option of the validator.

Validating CSS Style Sheets
If you use CSS in your document, you can check it for validity using the W3C CSS Validation Service.

Posted: Sun Aug 03, 2008 8:11 pm

Same thing happened to me actually, exporting from 2.33, importing to 2.35. The export seemed fine, but the import is incomplete. I've yet to check it out closely though.

Enchanter Joined: 09 Sep 2007 Posts: 605

Hmm, how did I miss this thread?.. Confused

I can confirm broken XML import in 2.35. This is my post from another thread http://forums.zuggsoft.com/forums/viewtopic.php?t=31452 :

Wizard Joined: 14 Aug 2004 Posts: 1269

Well there were some XML export changes made in 2.31 and 2.32 so maybe one (or more) of them wasn't carried over to the import routine...

Beginner Joined: 17 Apr 2007 Posts: 20

Any words Zugg?

//best regards

Adept Joined: 27 May 2008 Posts: 299

Zugg is out for the week at WorldCon or something. Don't expect him till next week.

Posted: Mon Aug 04, 2008 7:14 pm

Just doing a quick check-in, but I'll certainly need the XML file to test this, so send it to sales@zuggsoft.com. Also send me the correct *.pkg package file so that I can compare the correct package with what I get with the XML import.

Posted: Tue Aug 12, 2008 4:28 pm

Just wanted to let you know that I did receive your files, thanks. I'll take a look at them later this week.

Posted: Tue Aug 12, 2008 9:54 pm

Well, I found some of the problems with this. There was a problem with both Export and Import in the recent versions.

The problem with XML Export is with buttons. None of the properties of the button are being exported in v2.35. This shouldn't prevent a file from being imported, but it will mess up your buttons and especially mess up gauges.

The problem with XML Import is with multistate triggers. A multistate trigger actually causes the Import routine to completely abort and not load anything in the XML after it. So you get a partial import.

Both of these problems are fixed for the next version which I'll release later this week.

Enchanter Joined: 09 Sep 2007 Posts: 605

Zugg, please wait for my files, because at time they were created, I had no multistate triggers, but had troubles with importing an XML file.

Posted: Tue Aug 12, 2008 10:28 pm

Yes, they are separate issues on my bug list, so don't worry.