For the benefit of others who might be searching for a solution to the same problem, which part fixed it, moving the SWFObject code into the head, adding cache busting, or specifying an absolute path?
On Fri, Jan 29, 2010 at 2:12 PM, Alejandro Alves <[email protected]>wrote: > That solved the problem....thank you very much guys... > > -- You received this message because you are subscribed to the Google Groups "SWFObject" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/swfobject?hl=en.
