Skip navigation
Currently Being Moderated

Flash site works locally but not online (uploaded to server)

May 5, 2012 7:01 AM

Tags: #not #flash #template #loading #online

We have bought a flash portfolio template and have customized it with our pictures, video, etc.


When we test it locally on our computer (using different web browsers) it all works perfectly well. We have uploaded the finished website to our server and when you go to the address online, it doesn't work (a loader progress shows but it is stopped and nothing happens).


We have however uploaded the original template we bought and it works perfectly online.


The template consists of and index.html, various .swf, and various .xml that we have modified according to the template instructions (it also contains a java script folder we haven't touched).


What is it wrong with our modified template - it works locally without problem…!


Thanks for your help

  • Currently Being Moderated
    May 5, 2012 7:16 AM   in reply to albertomoreno1982

    If a loader progress is showing but nothing is loading, it sounds like there is a file missing that needs to be loaded to the server or the path to something is not correct.


    If you can get your hands on the debug version of the player you might be able to see what error is kicking up that is stalling the loading.

    Mark as:
  • Currently Being Moderated
    May 5, 2012 7:56 AM   in reply to albertomoreno1982

    When a Flash file works locally but not on-line, it's almost always a pathing issue (provided you did upload ALL files and do not have something missing... as suggested by Ned).

    A "pathing issue" results when the main .swf cannot find one or more of the associated Flash an xml file or images.

    It can be something as simple as using switching file names to all lower case. Local machine is not case sensative... most servers are. So "My Photo.JPG" is not the same as "my_photo.jpg". When naming files, best to use all lower case, no spaces in any file or folder names... use_underscore_instead.

    But the most common cause is that those associated files (xml, images, etc.) are not pathed relative to the Web page where the main .swf is embedded. Pathing to the .xml and image files should be as though the .swf was located in the same folder as the Web page... NOT the actual location of the .swf file.

    And that includes paths to the xml file and paths to image files coded into those xml files. Everything need to be coded relative to the Web page.

    This topic has been covered a number of times here:

    Best wishes,


    Mark as:
  • Currently Being Moderated
    May 5, 2012 9:49 AM   in reply to albertomoreno1982

    When you say "Flash site works locally but not on-line", how are you testing that? by clicking directly on the .swf? or by testing the .html web page which has the main .swf file on it?...all on your local machine of course.

    You could also be having problems with the Flash player itself. Some suggestions to fix a #1009 error include uninstall and reinstalling the Flash player.

    My two cents on updating the Flash player.... DON'T! Also don't target the latest version when you publish your Flash... target an older more stable version, 10 + or so. Let others work the bugs out first. Just my opinion but I never use the latest version of player, software, etc. Latest versions are often buggy and take awhile to settle out.

    So what you do with your player is up to you...

    But if pathing IS an issue, I'd suggest you re-read:

    My post near the bottom explain in detail how to path the .xml and related image or video files. It's not as straight forward as you might think, but does follow a very simple principle. Once you grasp the concept, pathing the related Flash files becomes much clearer and easier.

    Best wishes,


    Mark as:
  • Currently Being Moderated
    May 5, 2012 10:15 AM   in reply to albertomoreno1982

    You should be testing the site as you would normally visit, which I assume will be thru an html page.  You should have downloaded the debugger version that is created for the browser you intend to test with. 


    1009 errors indicate that object your code is trying to target does not exist as far as your code sees things.  I do not know if it works the same in the debugger version, but normally when you test in Flash if you set the Permit Debugging option in the Flash Publish Settings to be active, the error will include specific line references pointing to the problem.


    I don't have much experience with the debugger version mainly because of how it behaves for normal browsing. I take it out as soon as I don't need it so that I don't have to endure what it does.

    Mark as:
  • Currently Being Moderated
    May 6, 2012 8:02 AM   in reply to albertomoreno1982

    Yep. It's entirely believeable, that's all it takes to trip a file from working.

    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points