It might not matter to Flash whether or not your XML documents are correctly formed (and they almost certainly don’t need an XSL style sheet). You may want to add an encoding declaration in the xml tag to make sure that any accented or special characters display properly, but then again Flash may not even care about that and just grab the data it wants and do its thing with it. But if you want to view your XML docs in a web browser then you may want to consult a guide like
this one to make sure that the syntax is correct, etc.
-
MODX Staff
- 10,725 Posts
It does matter about the content type; it needs to be text/xml as ganeshXL indicated. I’ve done a lot of this kind of thing and can confirm it works a charm.
Quote from: OpenGeek at Mar 19, 2008, 09:12 PM
It does matter about the content type; it needs to be text/xml as ganeshXL indicated. I’ve done a lot of this kind of thing and can confirm it works a charm.
Yep. I may have been confusing about that, but it definitely matters. First I typed "text/html" above without thinking (error de dedo) and then my last post might have seemed to be saying that what ganeshXL said might not be necessary. Not so. The correct content type in MODx is essential.
it works also with text/html
I used the snippet call on the blank template
another thing,
I have utf-8 enconding on the config of modx but when I type an acute "é" for example it transforms it to "é"
so because of this I have to replace all the "é" "à" ’s in flash
Is there a way around this?
Did I forget something?
That’s probably the Rich Text Editor changing those characters when you enter them in each document. I don’t know if you can turn that off, so try a forum search and if you don’t find an answer post a new thread
here. If there’s no way to stop the RTE from translating those characters, you’ll either need to not use the RTE for those documents or replace the characters in your snippet.
-
☆ A M B ☆
- 24,524 Posts
You can change the configuration of the RTE entity encoding to "raw" in the plugin.
