Skip to main content
plummerdesign
Inspiring
May 19, 2018
Answered

Help publishing from Adobe Animate CC

  • May 19, 2018
  • 1 reply
  • 1363 views

Could use some help publishing from Adobe Animate CC V18.0.

I have a project, an HTML Canvas Document 300x250 PX that is destined for web advertising and click through.

It tests out wonderful.  Very pleased.

Problem is that I cannot figure out how to get it into a package for the end client.  Also to give them a web preview, whithout me being there.  I planned on uploading it to my MUSE website for them to preview.

But regardless of how I set up the 'publish', it never offers me the OAM.  Nothing MUSE can read is created.

Even in Dreamweaver I am lost as to how to place.

Guess I stepped away from this program too long as it was not a problem found in Flash or Edge Animate from days gone by.  What am I missing?

Thanks for the assist : )

This topic has been closed for replies.
Correct answer plummerdesign

In the screenshot you showed is an OAM checkbox. If you used that you could publish an OAM version, and Muse would be able to use that single file.

For the current approach you said you uploaded the HTML to the server, and that the images folder is in the same folder as the HTML. Did you mean on the server as well as on your local drive?

The things that would need to go onto the server, if you're not using OAM, would be the HTML (which you can rename to give the client an easier link), the .js file, and the images folder.

If it's not too sensitive could you post a link to your non working version? Or, if you use the browser's developer tools you could look at the Console to see if any errors are being reported.


Colin,

Thank you so much for the well written response.

Indeed the OAM places fine into the Muse page and works as it should.

...

My problem was with the browser-based version.

Digging deeper I discovered that while the 'IMAGES' folder truly uploaded to the server; the HTML/JS called for it to be found WITHIN the SAME folder as the script.  When Animate exports, it puts the IMAGES in a folder OUTSIDE of the HTML/JS folder.  So on upload the path stays as such. 

THE FIX was to create a second, redundant file with images and manually upload it to the same file folder on the server as the HTML/JS...it solved the query.  Now all works as it should.

...

I use the Muse FTP for that program, and Ipswitch FTP-PRO for manual uploads.  Nothing in the Animate docs say to do what I did.

PLEASE MARK THIS AS THE CORRECT ANSWER : ) 

1 reply

kglad
Community Expert
Community Expert
May 19, 2018

save your fla to a new directory.

publish your fla.

upload everything in the new directory (except the fla) to a website directory.

send a link to the uploaded html

plummerdesign
Inspiring
May 22, 2018

Hmm. That was not really the answer, as it was exactly what I was already doing.

(Preran please uncheck the 'correct' button)

.

The key in part seems to be using the ADVANCED Publish Settings, not Default.  I checked 'Overwrite HTML on Publish' to include JavaScript in HTML.

Then I uploaded the HTML file to the server.

It plays as it should BUT the 4 JPG images do not show up.

The JPG images are in the IMAGES folder and also in the same folder as the HTML and JS folder for redunancy.

Now to figure out how to either embed the images or Publish so that the player sees them.

THAT would be the correct answer : )

(see attached screenshot)

Colin Holgate
Inspiring
May 22, 2018

In the screenshot you showed is an OAM checkbox. If you used that you could publish an OAM version, and Muse would be able to use that single file.

For the current approach you said you uploaded the HTML to the server, and that the images folder is in the same folder as the HTML. Did you mean on the server as well as on your local drive?

The things that would need to go onto the server, if you're not using OAM, would be the HTML (which you can rename to give the client an easier link), the .js file, and the images folder.

If it's not too sensitive could you post a link to your non working version? Or, if you use the browser's developer tools you could look at the Console to see if any errors are being reported.