Printable View
http://blog.deconcept.com/swfobject/
That is floating around the Boardroom so I figured I'd post it. I haven't had any time myself to try any of the fixes because of work but , like Wilbert says, waiting may be a good thing because this is sure to get squared away fast by some solution. Being a mac user also, boxing out Macs is not an option so let me know if this boardroom solution posted by Flashlorax works.
can someone on a Mac using IE please test this page?
www.xylofun.com/index2
This page http://xylofun.com/index.htm should crash IE?
Thanks guys :-)
P.S. The first link checks for a Mac and if yes, then the script will not execute and the flash content should display the "frame" with the popup "click ...."
Actually the CLick to Activate will not happen on IE for Mac as its no longer updated.
It has been several days since the simple solution was announced here and problems with it were uncovered. Has anymore progress been made on finding a simple solution?
here's what I've decided on.
http://activecontent.blogspot.com/
thanks for posting that Bret :-)
I just updated all the xylofun pages with that fix too.
Ciao
Blanius
where do I put the javascript file "ieupdate.js" that I made? In the webroot folder where the .swf files are? I haven't uploaded it to the server yet either, I should be able to see the results when I test it just on my computer, right?
Put where you can find it eh? Webroot is fine just make sure any pages in sub folders you point to the source correctly using proper path.
I'm still missing something...
I'm trying to follow the fix on http://activecontent.blogspot.com/ but can't seem to do it right.
Here is the site's index page I'm trying to fix: http://www.danceuponnothing.com Could someone view the source and see if anything is wrong? I pasted the line in between the <HEAD> tags and where I thought was before and after my only <object> tag...
I also included the ieupdate.js I made in notepad pasting from the activecontent site. It pasted into notebook as one long line of text, but I figured that was ok?
The ieupdate.js is in the same root folder as all the other files on the server. I didn't see anything about directly linking to it beyond what I followed in the activecontent info...
Thanks for any and all help, this is a pain
your source looks right. Must be the ieUpdate.js try fixing the formatting. I agree one line shouldn't make a difference. But who knows.
Running in IE I get several script errors Looks like most are releated to not ending a line with ;
here's the file zipped try uploading this copy
It must have been the ieupdate.js I made. Definitely wanted the returns and breaks I didn't get just pasting the code I guess.
It makes me smile to not see "the rectangle"...Thanks so much for your help Bret!
-Dan
Is there any chance that KM will encorporate this fix into the KM program, so when you click 'Export Movie As SWF and HTML page...' it will automatically do it?
I am working it now but still am undecided which fix to use; they all have pros and cons.
The only fix that seems to work consistently is the one recommended by Adobe but it has the disadvantage of having the movie properties stated 3 times (in the script, object and embed).
The fix that Blanius recommended did not work for some undetermined reason on the koolmoves web pages so I used the Adobe fix.
Just the fact you will attempt to export the html correctly (when you decide the routine) is cool by me. Adobe is content to leave their users manually editing the html and we at least have an active developer that can export new Koolmoves versions at will compared to the long process before Adobe does the same for flash users.
Whatever you decide...even if we have to apply minor tweaks after the fact...is a massive help to users.
I believe that Adobe does have an update via the Exchange that changes the way Flash 8 exports to handle it.
I wasn't having much luck with the Adobe fix so I was wondering about the feasibility of the simple solution used here as all the script seemed to be doing was to piece together the original code so i cut out the middle man.
http://hand.po.gs/flashfix.htm
flashfix.js consists of
function Generateobj(str)
{
document.write(str);
}
The example uses the flash satay method discussed elswhere but the full coding should still be fine.
Did you let KoolMoves generate the html with the Adobe fix for you given a specific swf using File > Export Movie > Add to existing movie? Maybe you have a error in the code you created?
Well I have been using the shortened code so there were probably errors when converting back.
But the point here is that I was examining the javascript from adobe and found it a little on the convoluted side so in search for the simple life have been trying the 'send the original object script to be used 'as-is' to create the object' approach more comprehensible/less prone to mistakes when hand coding.....no problems with getting the format right for the javascript as it is the same as the original(without the hidden line breaks).
You've written the additional software to try and automate a rather head crunching process which is a helpful move but there are other variations....most of my flash is now on php generated pages so I needed to deal with that.
The more I play with it the sillier it seems but c'est la vie.
Has anyone tried the link I posted....I don't have access to IE as it causes a skin allergy :)
regards
mike
works ok