Dreamweaver has a “nice” feature that will automatically update the links in all affected files in a site when you restructure(moving files and folders around) your files and folders using it’s file browser panel. In most cases, I find this feature to be extremely useful and saves a great deal of time.

But today I found that this feature also caused a problem that took me a couple of hours to debug and trace to this particular cause. Dreamweaver actually erroneously modified a javascript file by adding in an extra relative path segment.

And this change in the flowplayer script caused the player not to be instantiated in Firefox and other browsers, but did not affect IE browsers (ie6 to ie8). I guess the generated code for embedding Flash for IE is different from that for the other browsers. And the path change only affects the branch of code that is supposed to render embed code for the other browsers.

I simply reverted the flowplayer code changed by Dreamweaver back to what it was. And the problem of FlowPlayer not showing up (not being created because the path to the player .swf file was wrong) went away.

  • Digg
  • del.icio.us
  • StumbleUpon
  • Sphinn
  • Facebook
  • Mixx
  • Google Bookmarks
  • Haohao
  • LinkedIn
  • Live
  • MyShare
  • MySpace
  • Reddit
  • Technorati
  • TwitThis

Related posts:

  1. SWFObject Conflicts Galore
  2. Video Formats for the Web – F4V, MOV, or MP4?
  3. Javascript Functions Appear to Be Undefined to IE
  4. Google Bar Causing Flash Video Page Script Error
  5. Error When Updating the FlowPlayer Plugin

Tags: , , , , , , ,

Leave a Reply

You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">