Edge Suite not working after Edge Animate upgrade

Why did you have to uncomment a line in the plugin? Can you make sure that you follow the instructions in
https://www.ads-software.com/support/topic/not-working-after-latest-adobe-cc-update?replies=22#post-6138079 to publish animations created in EA5. Otherwise I’m not sure what might happen.

@timm – it was an experiment. ??

I was thinking:
if Adobe removed the preloader.js file;
and the plugin will not import an OAM without the preloader.js file;
then remove the restriction in the plugin code and see what happens.

I have switched the plugin code back and am testing it as is.

I tried importing one of my simple animations again, and got it to work (imported via the plugin, runs on the page). You can see it at: https://es-test.sfwebfoundry.com/

The following was part of the confirmation message after the import:
“Auto detection of stage dimensions failed: Unable to spot stage variable.”

But there are 2 quirks / problems:
1) After the first run through of the animation, it doesn’t show the first half any more.

2) When I originally created the animation, it did not have a preloader or a downlevel stage. Even with the es5 version of the plugin, an import failed with a missing preloader.js error. I updated my animation, adding in a preloader, and now it imports correctly. I have realized that this is what prompted me to try commenting out the preloader.js check in one of the plugin files.

I am not sure what problem #2 means for the plugin. But it is interesting that previous versions of Edge Animate created a preloader.js file, whether you needed one or not.

If anyone wants to play around with my original animation (without the preloader) you can grab a copy of it at:
https://www.dropbox.com/s/26dayncu7jxsyt7/logo-1.zip?dl=0

~ PacWeb

The preloader.js used to be the main file which triggered all other file downloads. It contains some info which is still needed by the new version of edge suite if you use a preloader or not doesn’t matter. If you don’t use the preloader option then EA shifts some stuff into the .html. I can’t include the .html as it is, so I would need to do some heavy parsing which will most likely introduce bugs. Therefore, to get there faster, I still rely on the preloader.js. That as background info.

You can ignore “Auto detection of stage dimensions failed: Unable to spot stage variable.” this stopped working in EA4, but I parse the info out of the .xml file within the oam. I need to clean up the messages.

I checked your uploaded file. If I just open the standalone animation, meaning the logo-1.html, I get the same behavior. So that the animation doesn’t repeat correctly doesn’t seem to be ES related.

I’m glad to hear that the overall uploading worked for you.

I just opened the logo-1.html and watched it long enough to see the same problem. ??

Have you also seen the other problem?
Where the animation (OAM file) won’t import via the plugin because it is an animation that does not use a preloader.

Thanks for the background info. It is great to know. As you might guess, I scanned through the plugin file code yesterday. It looks complicated but thorough, and well documented (comments).

Oh, so the animation doesn’t upload at all when a preloader isn’t set? We have to distinguish between the preloader within the animation and the preloader file, which aren’t directly related. Can you create an animation without a preloader, set the separate preloader file option in the publish settings and see if that OAM really doesn’t upload. If so it would be great if you could put it in your dropbox.

It’s actually not that complicated, it was all just a bit hacky before, therefore I tried to comment a lot that I still know why I needed certain parts of the code. The codebase will be a lot smaller once support for older EA version is dropped, but that will happen only in ES2

That exactly it. The preloader (animation setting) was not set and the published OAM file would not upload (import). The animation you downloaded from dropbox should be the first version that does not have a preloader set (animation setting). So it should replicate the upload error.

When I get a chance I will throw together another simple animation that does not have a preloader set (animation setting).

I wonder how many other people are running into the import error, because their animation does not have a preloader set (animation setting).

It has been tricky, when writing these posts, to distinguish between the preloader setting in Animate and the js file.

Yeah, would be great if you could try that. I think most animations I saw up until now didn’t have a preloader set, but EA still created a preloader file with an empty preloader, dowblevel stage and the other settings.

Hi Timm,

Ok I tested 7 animations, of varying complexity, and some were created by other people. None of them have preloaders or down level stages. I carefully checked the publish settings: all of them are set to use the Adobe CDN and all have the option for “Publish preload DOM as separate file” greyed out.

The result = all had the “missing preloader.js file” error on import into WordPress.

So at least it is consistent.

What would you like to do next?

Thanks,
~ PacWeb

‘all have the option for “Publish preload DOM as separate file” greyed out.’ Do you mean you can’t enable it or just didn’t enable it? Edge Suite will fail without this option for the described reason, so that is not a bug itself. It would just be really bad if for some reason you couldn’t enable this option.

Can’t enable it.

But if I add a preloader (spinning wait cursor, etc) to my animation then I can check the box. I should note that this is under the Web Publish Settings. That option is not available under Animate Deployment Package.

I will email you a screen shot.

Thanks for the screenshot! You can ignore the web settings, what about the “Animate Deployment Package”, that’s what is relevant for the OAM.

I am sending you two screen shots:
1) Of the Animate Deployment Package settings – there is not an option related to the preload DOM.

2) The Web publish settings – I did an experiment:
– I added a preloader (wait cursor) to an animation.
– Then I published the animation, BUT I did not check the “Publish preload DOM” setting under Web Publish Settings (see screen shot).
– Then I tried to import the OAM into my WP site. The result was the “preload.js file missing” error.
– Then I went back to Edge Animate, checked the preload DOM setting under Web publish settings, and published again.
– When I went to my WP site, the newest OAM imported.

I suspect that not only did Adobe get rid of the preload.js as a default, but the setting that controls its creation is ONLY found under Web Publish Settings. Which is a little misleading.

If this is getting too convoluted, email me and we can setup a screen sharing call and I can take you through what I have done.

Thanks!

Wow, thanks for the detailed testing, I didn’t know that. Just to make sure I get this right, the setting under “Web” for “Publish preload DOM as separate file” decides if there is a separate preloader file in the OAM or not???

This then means we need to tell people to publish their files with theses options, this isn’t intuitive at all. I’ll check again how much work it is to parse the needed information from the .html