Digital Workshop

Hi there

Like many I encountered a failing of my opus created swf's after the release of Flash 10.

I have followed the instructions and replaced the file in my flash publish folder with the one in the zip as instructed, but now instead of hanging on the loading screen it hangs on a totally blank screen.

The version I have is Opus Pro V2.81 with Opus Flex installed. I have run the most recent update from your download site. I have restarted the system to make sure this was not the problem


The publication is a revision file for my pupils who have their mock exams coming soon so I'm keen to get it going. The publication does still publish to a working exe.

Any fixes or advice (other than buy a newer version ) would be appreciated.

this is an example of the hanging swf
http://www.bishopbriggs.e-dunbarton.sch.uk/_files/esskills.swf

I would suggest upgrading Opus to v6.
There have been many changes to the flash player and browser plugins since Opus v2.81 was released.
Apple dropped Flash support from Quicktime as well, so DW had to rewrite Opus to use the flash player instead of Quicktime for playback.

Flash is being changed so it will fit better with RIA developers using AIR; even developing swf's using an earlier version of Flash itself gives problems with either the Flash 10 player or browser plugin.
I would suggest that Opus v2.81 is becoming old technology, like many applications 5 or 6 years old.

That said, someone more familiar with using Opus Flex might suggest a workaround for your problem.

Paul

Hi

The flash file is there on the site (I downloaded it in FireFox) - just doesn't load .

I agree, in the long-term you will have to upgrade Opus if you want to continue creating Flex files. However, in the short term your only option, I think, would be to have your original imp file published using a later Opus edition. I presume that this would work. I know preparations for SQA exams are happening this term and understand why you are keen to get it working. I have seen your publication before, at SETT a couple of years ago or a MasterClass meeting somewhere? Update your profile on Glow with an email address and I will contact you.

David

Hi David,

Blimey wasn't expecting a Masterclasser to answer.

We're not fully immersed in Glow yet. But will see if I can update my profile.

Thanks to you both for replying.

TJL

If you cannot update your Glow profile, you can contact me through my website at www.ictstuff.info

Hi, is there any reason why you are not embedding the swf in a html file? because you are pointing directly to the swf and also, if you right click and click on play it will play the swf file.
Do you need help to embed the swf into a html file I can help.
Cheers

Hi Koala,

No reason, just a URL given as an example, even when embedded in html it hangs. The changes to Flash 10 seem to be the problem.

cheers

"Content-Disposition header may prevent SWF files from playingSome HTTP servers sometimes send a response header that looks like this:

Content-Disposition: attachmentThe purpose of this response header is to indicate to client software (browsers, Flash Player, e-mail clients, etc.) that the file being returned should not be rendered inline as active content. For example, imagine you're reading e-mail messages on a web-based service and you click a link that represents a file attached to a message. The server may well respond with "Content-Disposition: attachment"—meaning, "Hey, browser, don't open this file. Save it to disk instead." This header can sometimes serve a security purpose: If a server provides files that were uploaded by untrusted users, the "Content-Disposition: attachment" header can help prevent those files from being executed in the server's domain.

Starting with version 10,0,2, if Flash Player sees a "Content-Disposition: attachment" header while downloading a SWF file, it will ignore the SWF file rather than play it. Note that this restriction applies only to SWF files and not to other types of content, such as images, sounds, text, or XML files, policy files, etc.

What is impacted?
This change will affect any SWF file whose HTTP server specifies "Content-Disposition: attachment" while serving the SWF file. This change affects SWF files of all versions played in Flash Player 10,0,2 and later. This change affects all non-app content in Adobe AIR (however, AIR application content itself is unaffected).

What do I need to do?
If you control the HTTP server on which the SWF file resides, determine whether you trust the SWF file to execute in the server's domain. If so, remove the "Content-Disposition: attachment" header by changing your HTTP server's configuration.

If you do not control the HTTP server on which the SWF file resides, you have two options:

Contact the server administrator, inquiring whether the "Content-Disposition: attachment" header can be removed.
Download the SWF file from another SWF file that uses ActionScript 3.0. In the loading SWF, use the URLLoader or URLStream class to download the loadee SWF, rather than the Loader class as usual. After the loadee SWF has finished downloading, call Loader.loadBytes to transform the SWF data into a running SWF file. Note that this technique may not work because the loadee SWF may refer to relative URLs or rely on security sandbox privileges that are not available from the loading SWF's context".

I did what they suggest and my problems are over!
Cheers

Thanks to all for the advice, but especially to David for his time in getting things back up and running.

A true gent.

If you share some of your new found knowledge it could help someone else.

Paul

I simply took Tim's original imp file and republished it in 6.4 and with the exception of a few changes to text boxes and buttons everything is back to what it was before Flash 10.

I have been using 6.4 for a few weeks now and have no issues with Flex publications. I have republished two or three Flex pubs using 6.4 and they have all published and run without a hitch.

However, one issue I do have is that since installing 6.4 all of my publication icons (my .imp files) have reverted to the Windows "unknown" icon. Despite manually changing this setting in the File types window it would appear that there are no icon files in the 6.4 Opus.exe file. I have emailed DW about this.