This is the fix as posted on the m.c.rich_forms forum.
Doug
[quoted text, click to view] > Use the Custom Tag EOLAS_FIX V.1.02B, it works fine!
That custom tag doesnt work perfectly....
I am surprised that Adobe doesnt just patch CF7 like they did with Flex 1.5.
Anyone know at Adobe if this is going to happen? We should not be relaying on
Custom Tags to fix the way CF outputs content based on its server code. If the
environment changes, so should CF7... the developer community that uses it can
only do some much that custom tag is basically a bandaid.
Note: Its not working on my setup and I am working with the custom tag author
to get it working. So far its been unsuccessful.
Ben Forta's blog says "The good news is that the ColdFusion team is working on
a workaround to address this issue specifically for ColdFusion generated Flash.
The bad news is that it's still a few weeks away. Stay tuned, we'll post
specifics as soon as we have them."
There is fix that will work now and it's fairly simple. It requires two steps:
1. You have to place the following code inside but at the end of the BODY tag
on any page that uses macromedia Flash in any fashion inclucing Cold Fusion.
Copy and paste the following.
<script type="text/javascript" src="ieupdate.js"></script>
2. The create a java script file called "ieupdate.js" and place the following
code in it and place the file in the root directory of your web site.
theObjects = document.getElementsByTagName("object");
for (var i = 0; i < theObjects.length; i++) {
theObjects.outerHTML = theObjects.outerHTML;
}
Everything should work fine! It did not creat this fix, but can't rember
where I found it either.
John
;)