Adobe's Active Content Fix

This post is more than 2 years old.

So, I don't know about you, but since I don't use the devils' browser, I really haven't been too concerned about the upcoming (now here) EOLAS update which impacts Flash. When the update was rolled out and my project manager noticed the change on a client site, it was time to correct it.

So I took a look at Adobe's Active Content Developer Center and was surprised at how simple their fix was. Luckily my company's CMS system has a custom tag to spit out the code for Flash SWFs. All I had to do was modify that. The code change in question could not be simpler, I mean, look at this:

<script> AC_FL_RunContent( 'movie', 'filenameWithOutSWF', 'width','48', 'height','1516', 'id','myidiscoolerthanyourid'); </script>

Shoot, even if this IE change had not happened, this would have been a useful little script to get Flash onto a page.

I just wanted to make sure people knew about this fix. I was actually surprised by how fast I was able to fix the client's code with this.

One little note. I wasn't sure how to handle FlashVars. I thought they were special and the JavaScript code that Adobe provided didn't have a way to handle them. Duh. FlashVars are just one more property. Here is a modified version of the code above.

<script> AC_FL_RunContent( 'movie', 'filenameWithOutSWF', 'width','48', 'height','1516', 'id','myidiscoolerthanyourid', 'FlashVars','msg=DharmaWasHere&station=Swan' ); </script>

Truly simple and elegant solution. Thanks Adobe!

Raymond Camden's Picture

About Raymond Camden

Raymond is a senior developer evangelist for Adobe. He focuses on document services, JavaScript, and enterprise cat demos. If you like this article, please consider visiting my Amazon Wishlist or donating via PayPal to show your support. You can even buy me a coffee!

Lafayette, LA

Archived Comments

Comment 1 by Brian Rinaldi posted on 4/25/2006 at 5:40 PM

We moved everything to swfobject which worked great as well.

Comment 2 by Raymond Camden posted on 4/25/2006 at 5:43 PM

I've heard good things about it as well. I'm not using it, but I think a coworker is.

Comment 3 by Ryan Guill posted on 4/25/2006 at 6:00 PM

Hey ray, does this work for flash forms as well? If so, Im not sure how you would implement it...

Comment 4 by Chris Charlton posted on 4/25/2006 at 6:05 PM

Yes, pretty simple. :) The free extension from Adobe adds a Publishing (HTML) template and a Command (to ask where to save the JS include file). So, yes, pretty simple.

I see FlashObject, er now, SWFobject (SWFo) has an update as well. I really, really like how SWFo handles FlashParams. Adobe's solution isn't bad, but I like to parse in params with server-side code and Adobe's solution for FlashParams seems arcane for now. For now.

Comment 5 by Raymond Camden posted on 4/25/2006 at 6:12 PM

Ryan, no, it is not for Flash Forms or CFCHART. Adobe is working on that though.

Comment 6 by Kyle Hayes posted on 4/25/2006 at 7:09 PM

Apple implemented javascript code and functions for embedding quicktime as well.

Comment 7 by Rob Gonda posted on 4/26/2006 at 3:30 AM

I'll second FlashObject / SWFObject ... I started using it recently and it's working like a charm.

Comment 8 by Bjorn Jensen posted on 4/26/2006 at 11:09 AM

But does it work with javascript disabled ?
NoScript is the 2nd most popular extension for firefox at the moment, and as a NoSCript user I have to say it's bliss. I'm already blocking flash, but I can enable it with a click, however if javascript is used to generate the flash, I'll probably never see it and just move on to another site.

Comment 9 by Raymond Camden posted on 4/26/2006 at 2:40 PM

It does not work with JS disabled. I believe the Adobe site mentions that in the noscript you can use the 'old' object/embed stuff so that at least they _get_ the flash, but just have to click first.

Comment 10 by PaulC posted on 4/26/2006 at 11:05 PM

As infuriating as this situation is because of Eolas, I have to call shenanigans in part on Adobe.

MS announced this change months ago, patches for CF should have been ready to go, and I didn't even hear about the revised Flash publish templates until I saw it on John Dowdell's blog days after the IE patch was released.

Not to nitpick too hard, but I didn't see any kind of statement from Adobe on the lawsuit either. I know companies like to avoid getting sued, but I think developers would feel better if mama bear flashed her teeth at Mike Doyle.

Especially after <a href="" target="_blank>these comments from Eolas COO Mark Swords.

Comment 11 by J posted on 6/30/2006 at 5:14 AM

I can't get FlashVars to work in IE6 or Firefox 1.5.0 and when I searched adobe flash forum for 'active AND content AND FlashVars' I found posts mentioning that FlashVars doesn't work. What browser are you using?

Comment 12 by Greg H posted on 7/27/2006 at 8:15 PM


In a comment above 3 months ago, responding to Ryan's question about an Active Content fix for "Flash Forms or CFCHART" you wrote "Adobe is working on that".

Have you heard if Adobe has released a fix? I checked the CF 7.0.2 updater and do not see it called out specifically.



Comment 13 by Raymond Camden posted on 7/27/2006 at 8:19 PM

It is there.

Comment 14 by Z posted on 8/28/2008 at 6:27 PM

This article saved my sanity.

Comment 15 by DJ posted on 10/24/2008 at 10:24 PM

I know this is an old article so I apologize for reopening.

The AC_FL_Runcontent works great for FF 3 but IE will load my swf but not play it (background shows but nothing else) as soon as i put in 'FlashVars','xmlfile=#imageXML#&xmlfiletype=Default',

Anyone have any ideas as to why or how to fix?


Comment 16 by Raymond Camden posted on 10/25/2008 at 12:35 AM

What is #imagexml#? It doesn't have a space in it, does it?