Publishing/Detection Issue

programming flash
1

Hey friends, I was wondering if anyone has experience working with the publishing process built-in to Adobe Flash CS3. I’m having a tricky problem that needs some expert diagnosis.

My site structure looks like this:

Root[INDENT]index.html
/images[INDENT]myimage1.jpg
myimage2.jpg
myimage3.jpg
…
[/INDENT]/swf[INDENT]myFile.fla
myData.xml

[/INDENT][/INDENT]If I open myFile.fla the project works great. The .fla reads that .xml file in the same directory, traverses the folders and gets the images. If I embed the same file in index.html it can’t find the images.

The XML

The xml contains the path to the images. Right now,

 imgsrc="../images/myImage1.jpg"

is the value that works correctly with my .fla when I open it. It does not work when I embed that .fla in an HTML file located in the root directory. Neither does making the path relative to the site root

 imgsrc="images/myImage1.jpg"

which I had expected to be my problem.

I believe this to be a problem with AC_RunActiveContent.js and the way the flash detection uses JavaScript, but I could be wrong.

2

Try making it an absolute url by starting with a slash:
imgsrc="/images/myImage1.jpg"

3

Thanks for the advice, but that didn’t solve it. What’s really strange is how the swf can find the files just fine when opened from the folder its in.

Again, I’m speculating that there is a problem with the AC_RunActiveContent.js and the way one of the JavaScript variables gets passed in.

4

File names are case sensitive - that’s another thing you could check.

5

Thanks again for your help. I’m able to launch this app from it’s location and get the images to display ok. The problem happens when it is embedded into the index.html page in the parent directory. Changing the path to reflect the images locations based on the index.html page also does not work.

The situation makes me want to headbutt something.

6

At this point is makes sense to just sacrifice my organization and place it in the root directory.

It doesn’t solve the issue but I’ve contacted Adobe about it and maybe they can provide a correct solution for later on down the road.

Thanks for your help.