Zugg Software :: View topic

Wizard Joined: 17 Jun 2006 Posts: 1201

When I try to export something to XML, it ends up with errors in it.

</trigger>
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

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

Required white space was missing.

I can view it in the editor just fine though.

Novice Joined: 17 Aug 2007 Posts: 34

I just exported XML for another bug I had.

Perhaps you can get a bit more detailed. What specifically are you trying to export? Can you export one class but not another? Are you trying to export the entire thing?

Posted: Mon Aug 27, 2007 5:45 pm

Having the pkg file is really the only way to reproduce this bug. I'm guessing it's related to a specific setting or corruption in your package.

Posted: Mon Aug 27, 2007 7:21 pm

Where are you getting the error:

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

I didn't have a problem with exporting, but I did with importing. Clicked on Import XML, selected the file, and nothing. Even tried with a blank character.

Wizard Joined: 17 Jun 2006 Posts: 1201

Right. It will export fine, but you won't be able to import it due to the error.

Posted: Mon Aug 27, 2007 11:06 pm

Can you give us a copy of the XML so we can try to reproduce the bug?

Wizard Joined: 17 Jun 2006 Posts: 1201

Well I didn't want to display all my code for the world to see, since it specific to a certain mud and my character. Do you want me to e-mail it?

Wizard Joined: 17 Jun 2006 Posts: 1201

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

I have to get more info about certain things. When you select a module in the package editor, it gives you tabs for Options and XML. Is this XML supposed to be editable? If so, could this may be part the problem because I can add XML lines to it, but when I go to save it it reverts back to the original xml.

Just in case, here is a sample xml output I got.

Posted: Wed Aug 29, 2007 8:01 pm

Yes, this XML is editable. When I edit it and click Save changes, it works fine here. Perhaps you can show exactly what text you are adding or editing that isn't saving.

OldGuy2: I have no idea why IE doesn't display the XML properly. As far as I can tell, it is standard XML, so maybe it's an IE issue.

If you have an XML file that does not import, please email it to me so I can test it.

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

This may only be slightly related, but I'm wondering if it might be required (or just a good idea) to use CDATA tags on script code in the XML. I know it wouldn't look as clean, but it could make the XML output more compliant.

Posted: Thu Aug 30, 2007 5:46 pm

CDATA has nothing to do with "compliance". CMUD is already converting special characters like < into proper entities like < So CDATA isn't needed. Since I allow the XML to be edited, I decided that CDATA made the XML look "less readable". And remember that the entire purpose of all of this XML work was to come up with a more human-readable XML format.

Also, this encoding (where entities are used), is also the same encoding that is used in zApp, so when the zApp user-defined forms stuff is added later, there will be consistency on how it looks to the user.

Enchanter Joined: 11 Feb 2003 Posts: 511 Location: USA

Not to feel too rushed or anything, but have you had any success with reproducing the issue with XML not saving/being imported correctly?

Wizard Joined: 25 Mar 2003 Posts: 1113 Location: USA

Fair enough. If we know how to use CDATA tags and try them in the CMUD XML, would they work? Just curious now. Smile

Posted: Fri Aug 31, 2007 4:42 pm

Yes, if you use CDATA, then they should work fine.

Dumas: I still haven't gotten to this import/export bug on my bug list yet. Hopefully later today.

Posted: Fri Sep 07, 2007 7:10 pm

The problem with editing the XML above was that you were specifying an ID="999" value for your macro. Since there wasn't any existing record with an ID of 999, it ignored your addition. You need to use ID="-1" to add a new value.

I have improved this in v2.03 so that if the ID you specify doesn't exist, it will still create a new value. So that should work in 2.03.

Also, in 2.03, if the length of the "encoded" script is a lot longer than the original script (because of lots of < > & etc), then CMUD will use a CDATA section instead of doing the encoding.

And I should have the XML export/import issues working later today.