XML to CMS: Issues

Malformed XML

XML to CMS works with any valid xml files.
What does it mean?
Well, an xml is invalid when its structure doesn’t respect the xml specification, so, it is malformed.
A typical issue is the non-one-only root node.
The xml parser of Flash player VM1 (As2) is more permissive than VM2 one.
By Xml specifications, an xml must have one only node root. In VM1 also XMLList on root are accepted while VM2 , being strict, this cannot be happen.
Since XML2CMS is Flex based, only valid xml files will be handled.

A quick way to test the validness of an xml is to open it through Firefox and see what it prints out.

Best Practices when compiling an xml structure

….soon

Flash TextField ‘img src’ Issue

….soon

Upload Limit

….soon

WebRoot not readable

….soon

Mouse Wheel

The mouse wheel works by default to any User Interface element which have scrollbar visible.
Unfortunately there is known bug in the Flex SDK which break this functionality on some browser, for example on FireFox on Mac Os X.
This is something beyond our responsibility, so it will be fixed once Flex SDK will fix it.
Sorry for this inconvenience.
(XML to CMS 1.3 does contain a fix to this issue, thanks to this dude)