When embedding a compiled .swf, any potential syntax for linking an XML file ( "file.xml", "/file.xml", "./file.xml", ... "http://example.com/files/sitename/file.xml") seems to fail.

Not entirely sure about that because we've only tried it once, but am about to try again to verify.

Comments

1kenthomas’s picture

Priority: Normal » Minor

Repriortizing 'minor.'

Passing allowscriptaccess=sameserver (or such) in the embed code works (with some odditities), & this is an issue w/SWFObject.js, to boot.

wmostrey’s picture

Category: support » feature

I'm not in favor of putting in that line by default, but I don't want people to alter the module just to put in that line either. Perhaps I will add a configuration option for this. Thanks for pointing this out.

1kenthomas’s picture

It is possible to pass as a parameter via asset, eg, [asset|aid=##|...|bgcolor=#FFFFFF|allowscriptaccess=sameserver]; SWFObject seems in fact to parse any variables you include in this manner.

The problem I see (almost posted last night, but it is a SWFObject problem) is that any asset user can enable script access to an external server-- I'd want that severely restricted myself.

My ideal (for some point in the future) thus would be enforcing same-folder-only script access, with upload of the .swf and .xml at the same time.

wmostrey’s picture

Status: Active » Closed (won't fix)