Skip to main content
whitneya74264677
Participating Frequently
August 10, 2015
Question

publishing over a network

  • August 10, 2015
  • 2 replies
  • 398 views

Has anyone had issues of working on a cptx file (network location) and publishing on the network? The publish file (swf or html)is not functioning as designed.

We have been doing this and are noticing that may of the small functionality items programmed do not work.  We tested by working from the C:drive with no issues.

Our IT guy is very interested to find out if this is a Captivate 8 issue, or do we need to investigate our network.

Thank you all!

Send word!

Whitney

This topic has been closed for replies.

2 replies

RodWard
Community Expert
Community Expert
August 11, 2015

The reason your SWF files published to the network are not working properly is likely due to that network folder location NOT being set up on end user's PCs as a trusted location in Flash Global Security.

See here for details: Setting up Flash Global Security for Captivate | Infosemantics Pty Ltd

The reason your HTML5 content is not playing properly from a network server location is that HTML5 will also suffer browser security issues unless it is played from a WEB server over HTTP (not LAN server over TCP/IP).

whitneya74264677
Participating Frequently
August 11, 2015

Here is our situation based on the previous commentary:

Developer A has created a cptx file that includes rollover slidelets.  When the original developer publishes the swf from the network or local machine everything works including slidelets.

When someone else publishes from the same cptx file from the server or bringing a copy of the original file to their local machine, everything works except the slidelets.

When troubleshooting, we have tried duplication of the cache files across the network, copying to the local machine and all iterations, yet the slidelets do not work.

We have not deleted the cache files for fear of losing something from the original developer.

Everything works (including SLIDELETS) only if the original developer publishes the file.

Keep in mind we are not using html5 as a published version.

Thoughts, comments, suggestions?

Thank you all.

W

Lilybiri
Legend
August 10, 2015

You should never work on a Captivate file that is on a network, that is the recommendation.k

Sent from my iPad

whitneya74264677
Participating Frequently
August 10, 2015

Are the captivate cached files located in the users Adobe Captivate Cached projects folder required when to publish files?

The folder gets quite large quickly and we try to optimize our folders as much as we can. 

If you can provide any details on how the captivate files work with the cache folder we would be most happy!

Thank you sir!

Erik Lord
Inspiring
August 10, 2015

The files in Captivate's cache folder are not required. In the Captivate Preferences, you can empty that cache at any time.

I believe, but don't know for sure, the advantages of the cache are slightly quicker load time for projects and as a location for auto-backups.

While I agree with the overall guideline to NOT work on CPTX files over the network, nor publish to a network location, I *have* done that a fair bit in the past and *usually* with no ill effects. However, if you do have to work over a network, just note that you are inviting troubles (however rare or frequent they may be). Best practice: probably copy the source file to your machine, work on it, publish it, etc...then copy everything back up to the network (backup?!) location at the end of the day.