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
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. http://www.adobe.com/support/flashplayer/downloads.html
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 files...like 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:
Thanks so much for your help adninjastrator - having finished all the work on our website and having to deal with not seeing it working can be frustrating since we are no experts at Flash...
I have opened each and every .swf file from the website with the Flash Player Debugger but nothing happens... (no errors displayed on a dialog or anything) Is this what we are supposed to do?
I see we have some .jpg (in the pictures galleries) named with Upper case and one space (instead of _). We are going to rename all of them to lowercase and don't leave spaces.
Regarding the .swf - should we leave them alone (they are the originals) or do something else with them?
I have downloaded the "Macintosh Flash Player 11.2 Projector content debugger" and opened the main.swf with it - while navigating the site the following message was displayed (see picture):
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.
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.
Thanks both Ned and adninjastrator for your help.
@ adninjastrator: I am testing the site:
-first simply clicking the index.html that opens a web browser (I use different ones to see if it works in all of them) -> in this way all works fine.
-I have downloaded the "Flash Player Debugger" (Macintosh Flash Player 11.2 Projector content debugger) - and have opened the main.swf (that opens the main website --- since the other .swf open only what seem areas of the site in plain colors but no content) - I am going to download the 10.3 version as you tell me and uninstall the newer one for this one. When I open the site this way all works fine but the ActionScript error message I have posted above appears when I navigate the site.
I am going to re-read all the posts you have sent me and specially the last one and will report back after trying out the different options.
@ Ned: Ok I'll go through the debugger version of the browser to see how it goes - I guess it will be pointing where the problem lies...
We'll report back as I try it all out - CHEERS!
Can you guys believe it was just a .jpg (the main background picture the site loads as you enter it) that was accidentally renamed .JPG ?
Thanks to both for your suggestions we got in the right path to solve it
Lucky Strike: we were ready to redo the whole site from the ground up, but decided to prove a change starting with the backgrounds... and there the problem lied...
A thousand thanks for taking your time and for you information Ned and adninjastrator