For zip creation to work properly, the full directory path of the publish location needs to be less than 256 characters in length, including the name of the zip file itself. Also, please be aware that working on a network drive or publishing to a network drive can cause erratic behavior. You should edit and publish your content on your local hard drive (typically, your C: drive).
If you're still experiencing issues creating the zip file, we'd be happy to take closer look at what's going on. First, create an Articulate Presenter Package of your presentation as described here. Then upload the resulting zip file from your computer on the second page of this form, and we''ll attempt to diagnose what's happening when we receive your upload. Thanks!
Please send me an example "full directory path of publish location including name of zip file".
The behaviour *has* occurred when publishing to a local hard drive.
Once I hear from you about the directory path bizzo, then I'll take a look at the form. It seems from what I read on this forum that Articulate has numerous technical issues that end up going to your tech team for troubleshooting. Why would it matter which drive on a computer system a published product is saved to? And why would Articulate be content with "erratic behaviour" when users are trying to use the software?
Thanks for asking. An example of a workable directory path would be something like: C:\Users\Administrator\Documents\My Articulate Projects\working sample.
As far as technical issues being forwarded to our support team, keep in mind this is a technical support forum, so the natural flow of anything that fellow community members and moderators like myself aren't able to assist with, we're happy to take a closer look at a customer's files, which is really the best way to troubleshoot an issue.
Publishing and saving files to a local drive rather than a network drive or USB drive, isn't something unique to Articulate software, and unexpected or erratic behavior is certainly not something we're content with. It's typically a byproduct of not following best practices when developing, saving, or transferring projects.
If you're going to be working in a collaborative environment with other developers and moving projects from one drive to another, here is a reliable and recommended worflow to follow to avoid file corruption and loss of resources.
4 Replies
Hi Smarten Up,
For zip creation to work properly, the full directory path of the publish location needs to be less than 256 characters in length, including the name of the zip file itself. Also, please be aware that working on a network drive or publishing to a network drive can cause erratic behavior. You should edit and publish your content on your local hard drive (typically, your C: drive).
If you're still experiencing issues creating the zip file, we'd be happy to take closer look at what's going on. First, create an Articulate Presenter Package of your presentation as described here. Then upload the resulting zip file from your computer on the second page of this form, and we''ll attempt to diagnose what's happening when we receive your upload. Thanks!
Peter,
Please send me an example "full directory path of publish location including name of zip file".
The behaviour *has* occurred when publishing to a local hard drive.
Once I hear from you about the directory path bizzo, then I'll take a look at the form. It seems from what I read on this forum that Articulate has numerous technical issues that end up going to your tech team for troubleshooting. Why would it matter which drive on a computer system a published product is saved to? And why would Articulate be content with "erratic behaviour" when users are trying to use the software?
Hi,
Thanks for asking. An example of a workable directory path would be something like: C:\Users\Administrator\Documents\My Articulate Projects\working sample.
As far as technical issues being forwarded to our support team, keep in mind this is a technical support forum, so the natural flow of anything that fellow community members and moderators like myself aren't able to assist with, we're happy to take a closer look at a customer's files, which is really the best way to troubleshoot an issue.
Publishing and saving files to a local drive rather than a network drive or USB drive, isn't something unique to Articulate software, and unexpected or erratic behavior is certainly not something we're content with. It's typically a byproduct of not following best practices when developing, saving, or transferring projects.
If you're going to be working in a collaborative environment with other developers and moving projects from one drive to another, here is a reliable and recommended worflow to follow to avoid file corruption and loss of resources.
And Tom Kuhlmann has written an excellent article on managing project files for this exact reason.
Hope that information is helpful, and please let us know if you have any further questions. Thanks!
Thank you Peter and Allen.
This discussion is closed. You can start a new discussion or contact Articulate Support.