That's because https is a pain the @ss.
Mixed Content: The page at 'https://storefront.aaaconstructionschool.com/cgi-bin/commerce.cgi?display=a…mptyoverride=y es&template=PDGCommTemplates/Header_Footer_XHTML/mold-2.html' was loaded over HTTPS, but requested an insecure script 'http://animate.adobe.com/runtime/6.0.0/edge.6.0.0.min.js'. This request has been blocked; the content must be served over HTTPS.
so when exporting don't use the option that allows edge.6.0.0.min.js to be hosted on the adobe servers
you didn't upload the edge js file to your new location
https://storefront.aaaconstructionschool.com/cgi-bin/edge_includes/edge.6.0.0.min.js Failed to load resource: the server responded with a status of 404 (Not Found)
Thanks again Joe;
That is the problem. The file "is" there but it is acting like it isn't. That's why in my first post I suggested it might be a path issue. In the help files for the earlier versions of Edge there were issues regarding relative vs absolute paths that had to be corrected and I think this still might be the case? However the newer .js files are not as friendly as the older ones.
so why can I see this js file in the browser
but not this one???
Hey guys, I'm having the exact same problem as TheJokker.
Edge animation runs fine on my root directory, but once uploaded to my server it doesn't show.
I went down the rabbit whole of attempting to use the "Animation" .oam file type export from Edge, and then created a single page site to house it in, but the same problem occurred. The animation played in Muse, and on the root directory export created by muse, but not when loaded in the server.
Example of Edge "Web" exported page" http://www.rhizomeconsulting.com/clients/simran/sandbox2/RevelAnimatedDraft1.html
Example of Edge "Animation" export embedded in Muse site: www.rhizomeconsulting.com/clients/simran/sandbox/index.html
On both sites, I'm getting an error (seen in Safari's developer error console) that the "....edge.6.0.0.min.map" failed to load due to a 404 not found.
That file is there in the directory, but it has the name "edge.6.0.0.min.js"
From my research this points to a http vs https issue that pittsburgh_joe pointed to.
Anyone else have a solve for this? Or other work arounds? I'm dead in the water!