Pages: [1]
  Print  
Author Topic: Can't get Gaia site working on a new server  (Read 339 times)
mosk
Gaia Expert
****
Posts: 207


« on: October 18, 2011, 12:10:35 PM »

Hi.  I recently switched to a new webhost with faster servers and got a dedicated IP because the Gaia site I'd built had lots of flv's and it was struggling on my shared hosting platform.  At one point things were working fine on the new host.  I then removed the svn folder (for subversion) from the webhost because I didn't think it was needed.  No idea if that's what triggered the problem or just a red herring, but now my site won't load past the first page.  Loads index, nav, and the start page very slowly, plays an flv that's on the first page very slowly, but doesn't move on to the next page at the end of the video (should be triggered by cuepoint).  Nor does double clicking on the enter gate take me directly to the second page as it used to.  And the right click menu changes things in the URL window, but nothing gets loaded (and MonsterDebugger doesn't show any further activity past that first page).

Everything still works perfectly well when I run it inside the Flash IDE or when I double click on the index.html and run in it a browser (with the files pulled from my local c-drive).

I tried pulling everything off the new server and re-uploading everything (meaning the entire bin directory), including the svn folder.  Still not working however.

Any ideas as to what could be going on?  (I'll contact my new webhosting service, but they specialize in Drupal, not Flash, so it would helpful if I had some idea how to fix things before getting in touch).

Thanks for any suggestions.  (Note - I'm running the latest version of Gaia from Flash CS4 IDE in AS3 with Tortoise SVN for versioning)
« Last Edit: October 18, 2011, 12:19:19 PM by mosk » Logged
mosk
Gaia Expert
****
Posts: 207


« Reply #1 on: October 18, 2011, 01:21:25 PM »

Just tried uploading a completely different Gaia site and ran into problem where only part of the first page gets loaded - the navigation buttons don't; and once again, the right click menu had pages listed, the URL address would change, but no change in content would occur.

I removed that old site and restored things to the new one, but it still can't get past the first page (http://www.yourgods.com/bin/index.html#/welcome-to-yourgods-com) and the video (which is an flv encoded at a low quality, very playable rate of 750kbps).

Double clicking on the welcome gate should bypass the video and go straight to the next page ((http://www.yourgods.com/bin/index.html#/fool-s-hold/the-hold) but that's not working either.

The www.YourGods.com site is supposed to be live, but right now it's about 9/10ths dead - so I'm hoping someone here might know how to troubleshoot such things and be willing to take a look at it.

Thanks for any assistance.
Logged
steven
Gaia Author
Administrator
Gaia Evangelist
*****
Posts: 3871


gaiaframework
WWW
« Reply #2 on: October 18, 2011, 01:32:47 PM »

Looks like it's working for me.

Are you using the debug player? Make sure you don't have any runtime errors.
Logged

Steven Sacks | Gaia Author
Please support Gaia by donating to the project!  Smiley
mosk
Gaia Expert
****
Posts: 207


« Reply #3 on: October 18, 2011, 02:38:39 PM »

Hey Steven -

Ok.  I uninstalled the Regular Flashplayer and installed the debugger, and this is what I found in my Log Files:

Code:
from Main:  view.scaleX = 0.9041666666666667 and view.scaleY = 1.0129032258064516
from Main:  view.x = 0 and view.y = 0
Error: Failed to load policy file from xmlsocket://127.0.0.1:5800
Error: Request for resource at xmlsocket://127.0.0.1:5800 by requestor from http://www.yourgods.com/bin/main.swf has failed because the server cannot be reached.
*** Security Sandbox Violation ***
Connection to 127.0.0.1:5800 halted - not permitted from http://www.yourgods.com/bin/main.swf
Error: Request for resource at xmlsocket://127.0.0.1:5800 by requestor from http://www.yourgods.com/bin/main.swf has failed because the server cannot be reached.

and also this:
Code:
Warning: AllowScriptAccess='never' found in HTML.  This setting is ineffective and deprecated.  See http://www.adobe.com/go/allowscriptaccess for details.
Warning: 'com' has no property 'onEnterFrame'

As for the allowscriptaccess - not sure why it's coming up with that.
I have a one line index.php file located inside of public_html/yourgods.com
Code:
<?php header("Location: http://www.yourgods.com/bin/index.html");?>
which simply redirects to the index.html inside of my bin folder generated by Gaia -  and that index.html has allowscriptaccess set to always as shown below.

Code:
<title>Gaia Framework Site</title>
<script type="text/javascript" src="js/swfobject.js"></script>
<script type="text/javascript" src="js/swfaddress.js"></script>
<script type="text/javascript">
var params = {
quality: "high",
scale: "noscale",
wmode: "window",
allowscriptaccess: "always",
bgcolor: "#333333",
allowfullscreen: "true"
};
var flashvars = {
siteXML: "xml/site.xml"
};
var attributes = {
id: "flashcontent",
name: "flashcontent"
};
swfobject.embedSWF("main.swf", "flashcontent", "100%", "100%", "10.0.0", "expressInstall.swf", flashvars, params, attributes);
</script>



As for the Security Sandbox violation, my old webhost was 1&1, and they are still the official Registrar of YourGods.com - but I now have YourGods.com pointed at the DomainNameServers for my new host, Holistic, which specializes in Drupal and has no experience with Flash - so I hope you'll bear with me and offer what guidance you can since they said I was basically on my own for troubleshooting any Flash related problems.

Is that likely to be the source of my problem (that I'm only 'pointing' to the nameservers and have only 'parked' my domain with the new host instead of transferring it completely?

And if so, do I just need to create a cross domain policy xml file like the one below and leave it on my Old Webhost?

 
Code:
   
<?xml version="1.0"?> 
    <cross-domain-policy> 
    <allow-access-from domain="MyNewDedicatedIPAddressHere" /> 
    </cross-domain-policy>
 

I'd been using MonsterDebugger but I'm not sure if that gives you anything about Runtime errors.  So thanks for the tip about the Flash Debugger and for any further guidance.
Logged
steven
Gaia Author
Administrator
Gaia Evangelist
*****
Posts: 3871


gaiaframework
WWW
« Reply #4 on: October 18, 2011, 03:14:51 PM »

It's probably the source of your problem, yes. It's def not Gaia. You might want to post to Flashcoders for more responses. I don't know the solution.
Logged

Steven Sacks | Gaia Author
Please support Gaia by donating to the project!  Smiley
mosk
Gaia Expert
****
Posts: 207


« Reply #5 on: October 18, 2011, 03:17:34 PM »

OK.  I'll give it a try there or on the Adobe forums.  Thanks.
Logged
mosk
Gaia Expert
****
Posts: 207


« Reply #6 on: October 20, 2011, 09:07:11 PM »

Tracked down the source of my problem last night with some help on the Adobe and ActionScript.org forums, and I'll post it here in case anyone stumbles across the same problem.

Steven - thanks for your suggestion about the Flashplayer Debugger - helped me get to the bottom of my problem.  I'll post about it below for anyone else who runs into similar issues.

First, the security sandbox error with the 127.0.0.1 calls being sent out was a result of my not deactivating MonsterDebugger before uploading my site to a live server - so the server was trying to contact the AIR application on my localhost/desktop.  Ironically, that had nothing to do with why my site couldn't get past the first page on its new servers, and if I hadn't installed the FlashDebugger I would never have known about the error.  Firefox's Firebug extension lets you monitor NET interactions as someone at actionscript.org pointed out, which is a very useful feature for any who've not used it before.  (And as a side not, the MonsterDebugger's documentation explicitly tells you to deactivate the Debugger before posting on production site and discusses socket calls - guess I should have RTFM a little bit more closely)

Second issue which was blocking my site's functionality was a capitalization discrepancy between a navigation button/swf file  from Turtlebite's global nav and my Navig.xml file.  Not sure why this didn't trigger problems in the Flash IDE when I ran things.  And curiously, when I tested the identical files on my old webhost, it didn't cause problems there either.

Thanks.  Making progress once more.

Logged
Pages: [1]
  Print  
 
Jump to:  

TinyPortal v1.0 beta 4 © Bloc