Edge Suite not working after Edge Animate upgrade

I think this might be solvable in a different way. Can you do me a favor and sent me an OAM with a set preloader and downlevel stage, but WITHOUT the separate preloader file option enabled.

No problem. It was a team effort. I would not have found all of this on my own. Our trading messages is what uncovered all of this.

You are correct, the only setting for “Publish preload DOM as separate file” is found under the Web settings.

From what I found, to get an OAM to import correctly you need to do two things:
1) Add a preloader (wait cursor) to your Edge Animate animation.
2) Check the box for “Publish preload DOM as separate file” under Web Publish settings.

You are right, this is not intuitive at all.

I have a theory about why the “Publish preload DOM as separate file” setting is only under Web Publish settings and I just did a test that seems to confirm it.

Adobe got rid of the preloader.js as part of their lightening of Edge Animate. But it is still something that might be needed in customized web projects. So they kept a setting to publish that file under the Web Publish settings.

I am thinking that they were thinking that the setting was not needed under the Animation Deployment Package setting, because an OAM file is usually used by another Adobe product. So if the setting was under Animation Deployment it was unnecessary and potentially confusing to people using Animate.

In Dreamweaver I tried inserting an OAM file from an animation that does not have a preloader set (wait cursor) into a new HTML doc. A file that causes an import error in WP. It inserted (imported) perfectly.

I am thinking that Adobe built the ability to parse the OAM without a preloader (js file or wait cursor) into their programs. But didn’t realize that it threw off your plugin and only put a setting to create a preloader.js under Web Publish settings because that is the spot for ‘customized’ web output in Edge Animate.

Basically, they were trying to lighten the Edge Animate program and keep its UI straight forward. But ended up causing this subtle confusion.

Does this make sense?

Yes, makes total sense when looking at it this way. The user would be pretty confused when having an option for a separate preloader file on OAMs.

I’ll check if we can make it work without the preloader file when not having a preloader. Will take until end of next week though as I’ll be away next week.

When we will get the fix for this issue.. I can’t update my site and my clients are waiting for this issue to be solved so they will also complete their sites.

Is there any possible solution to get the OAM file work in WordPress site.

I’ve been following this thread and have just tried to upload a new animation. As suggested I have:

1) Add a preloader (wait cursor) to your Edge Animate animation.
2) Check the box for “Publish preload DOM as separate file” under Web Publish settings.

I can see the oam file in the tmp directory but am getting an error message:

‘Unable to parse stage name from main edge file’

Is this related to the EA upgrade or a separate issue?

Thanks.

Just to add to the above. I’ve tried this with an upgraded animation as well as a new animation. I’ve tried uploading to two different installs of WordPress (one of them a new install with no plugins other than Edge Suite) on two different hosting services and I always get the ‘Unable to parse stage name’ error. I’ve tried changing the Edge Suite folder permissions but still no joy.

Hi PacWeb,

Thanks very much for the above. The new version fixed it. I am now able to upload both new and upgraded animations. I really appreciate the the time you and Timm have been putting in to solve this problem. Thanks again.

Philnicholl

I successfully got everything uploaded to divadeluxedesign.com/test using the steps above and in the other thread. The two issues I have now:
1. The animation doesn’t always load, and sometimes gets stuck on the preloader.
2. Choosing individual animations for different pages (using the code snippet inserted into the header.php file) doesn’t seem to work either. I can specify a default, as well as an animation specific to the blog page, but choosing from the drop down on an individual page or post doesn’t seem to work at all.

Hello. I have tested the above method and the animation is uploaded and working on my production environment but my friend is working on Sandbox environment wordpress when I upload the same file it give me just 1 error

” Unable to parse stage name from main edge file “

The file is not uploading at all. What is the issue.

Hi Sam53,

If you read pacweb’s post above you’ll see that there are two stages to a successful upload.

First thing, as part of your animation (within Edge Animate) you need to do the two steps that @philnicholl quoted above. 1) Setting a preloader and 2) Publishing the preload DOM.

The second thing, is that you need to be using the newest version of the plugin, ES5. And to reiterate Timm’s note, “DON’T EVEN TRY TO USE THIS IN PRODUCTION! ” so use with caution. You can get ES5 here:
https://github.com/ti2m/edge-suite-wp/tree/ea5

Installing the latest version of Edge Suite, available via the link, is necessary as well as setting the preloaded and publishing the preload DOM.

Hope this helps.

Philnicholl

Hi Philnicholl – thanks!

Hi Sam53 – is your friend still having problems?
Even after using the ES5 plugin and setting up the preloader.

Thanks,
~ PacWeb

Hi cydsmith,

I looked at your demo site, The animation loaded and ran for me. When I went to the other pages (How, What, Who, Why) I saw a different animation, just a rotating compass. Let me respond to your questions:

1) What browser are you using?
I am using Chrome. I have seen (with my own animations) and have heard that the animations can have problems in non-webkit browsers (Firefox and IE).

Also, is Edge Animate flagging any warnings?
They would show as a little yellow, caution triangle in the lower righthand corner of the stage.

2) I have found hardcoding an animation difficult as well. If you are talking about the “Edge Suite” dropdown in a Edit Post/Page page, I think Timm once told me that that dropdown doesn’t do anything (other than give you animation IDs to reference). A few of questions:
Are you trying to have the specific animations only in the header?
If not, have you tried using the shortcodes for the specific animations that you want on specific pages?
If you do want them only in the header, do you have a widgetized area in your header that you can leverage?

Thanks,
~ PacWeb

Hi,
I just commited two changes to the ea5 branch. I made the preloader file optional and multiple compositions should now work within one page.

@pacweb Could you maybe give it another try with your compositions? That would be great. If you don’t have a preloader within the animation, then you don’t need to do anything. If you want to use a prealoder though, then one needs to enable the “separate file” preloader option. Would be great if you could test both and also check if multiple comps within one page work for you.

If anyone else is up for testing, please do so, we need to check if that works better now.

Hi Timm,

I will use the newer version and test both scenarios: with a preloader and without. When I am done I will post my results here.

Stay tuned …
~ PacWeb