Flash Player and .SWF

Question

I am a new upcoming Web Designer. I created two web pages for
my web site, in Adobe Flash Pro CS3, and I published it for HTML
view. I upload it to the server the page would play but when I'd go
to click on the buttons that would link to the other pages of my
website, it would not go in. So at first my first thought that
there might have been some actionscript issue going on with the
flash buttons. But when I went to the original .FLA file on the
buttons it worked fine for the folder that it was in, so I figured
let me re-route these buttons to the actual website using the
website and its directory for the buttons to link. Still did not
work, as a matter of fact when I re-checked it again using the
browser this message box open up with this error message:"Adobe
Flash Player has stopped a potentially unsafe operations the
following local application on your computer or network:
C:\AD%20Creative%20Media%20&%20Designs\index.swf is trying to
communicate with this Internet-enabled location:
www.andersondominique.com To let this application communicate with
the Internet, Click Settings. You must restart the application
after changing your settings." So I did clicked on the settings
button, which lead me to the this website but on a different page.
I changed the security settings like it asked me to for at least
100 times today, and I am not getting a different result. Can
somebody please help me! I really need to get this website up and
running properly its for me to get a job. Im desperate! If anyone
out there is familiar with this problem please answer me or better
yet email me at: [email protected] THANK YOU!

Answer 1

We've recently made a number of security-related changes to how UNC paths are handled in Flash Player, and in addition, have restricted some network requests from being made for locally-executed SWFs running with local-with-filesystem permissions.  These changes were necessary, as we found ourselves on the wrong side of a confluence of both old and emerging standards and conventions, and a very forgiving approaches to incorrectly constructed URLs in most major browsers.
Where we could, we added good debugging messages, so installing a an ActionScript debugger version of Flash and running the application might provide you with some useful clues; however, as complexity increases, I'm not convinced that using Flash Player to execute SWFs locally in the browser is going to be smooth sailing, and I anticipate that we'll see additional churn as we evaluate and align with the expectations of the modern web in this regard.
The good news is that we have Adobe AIR, which is designed to make it really easy to port your Flash Content, and it's specifically designed to build desktop applications, free from the complexity of browser plug-ins.  As a least-cost, long-term strategy, I'd strongly encourage you to evaluate porting your SWF over to AIR.  It may be as easy as just changing the publishing target in a current version of Flash Professional and distributing your application as an AIR payload instead.
Alternatively, you could stand up a local webserver and host both the content and the SWF.  The really hairy edge-cases stem from the fact that we're trying to support HTTP and UNC paths simultaneously.  If you're using HTTP, things are much, much more straightforward.
If you can narrow it down to the failing ActionScript call, I might be able to give you a more specific suggestion for a workaround.