Looks like that may be an issue with the Engage file. Can you send us your zipped project files so we can take a closer look and help resolve this? You can do that here:
Interesting idea you pose. I generally use the "Save and return" option, but not always. Just depends on the kind of edits I'm doing. I have no idea how the last file was saved. If my client sees the problem again, I'll try this new approach AND send the Engage file to Support. (I just gave him a new build of the course for testing.)
FYI, it's only the one file doing this and there are other interactions in the course.
3 Replies
Hey Kevin,
Looks like that may be an issue with the Engage file. Can you send us your zipped project files so we can take a closer look and help resolve this? You can do that here:
http://upload.articulate.com/
Thanks!
Does this happen if you use the "Save and return to publisher" option? Have you tried publishing the engage file for Web then importing that?
I had that happen once and that worked for some reason.
Also, is it all engage files or just that one in your course?
Hi Dwayne,
Interesting idea you pose. I generally use the "Save and return" option, but not always. Just depends on the kind of edits I'm doing. I have no idea how the last file was saved. If my client sees the problem again, I'll try this new approach AND send the Engage file to Support. (I just gave him a new build of the course for testing.)
FYI, it's only the one file doing this and there are other interactions in the course.
Thanks for your help.
Kevin
This discussion is closed. You can start a new discussion or contact Articulate Support.