title: "Error calling method on NPObject" on first page load
body: <p>since a few days there seems to be a problem with a audio player script (flash + javascript) on one of our pages that NEVER occured before and I changed absolutely nothing in the code (it has worked for a few years now) that could cause this issue.
  We bought the audio player script a few years ago, and again, until a few days ago, it worked perfectly.</p>
  
  <p>The error also behaves very strange. Let me explain...:</p>
  
  <p>The page is <a href="http://www.imatunes.de" rel="nofollow">www.imatunes.de</a> . You can see these small audio players on each article there.
  Feel free to check out the code, got nothing to hide there.</p>
  
  <p>My coworkers told me, that suddenly nothing happened if they clicked on the "Play" buttons. Normally, the script should start the flash player, which plays an audio file.</p>
  
  <p>Now comes the "somehow" strange part:
  My coworkers are all using Google Chrome. When they open the page in Chrome and click on a "Play" button, the JavaScript console throws the following error:
  <strong>"Error on calling method on NPObject".</strong>
  Googling that error says it has to do something with actionscript, cross-domain policies and such. But the error will get stranger...:</p>
  
  <p>I'm using Firefox, and there it works FLAWLESS. But it also works on MY Google Chrome flawless, so it's very hard to debug (that's why I'm here to ask).</p>
  
  <p>My coworkers also tried it on their home PCs, also running Google Chrome and such, and it also doesn't work there.</p>
  
  <p>Now comes the "very" strange part:
  When they get this error and reload the page via the browser controls (F5 or the reload button), it still won't work.
  <strong>But</strong> if they browse around the page or just click on the logo in the header (which basically takes them to the home page again), the script magically works.
  And on every other page except for the home page, it will work on first try.</p>
  
  <p>As I said before, this started a few days ago - before that, everything worked just fine. And I really didn't change anything in the code.</p>
  
  <p>So regarding the fact that it works after they browse around the page and return to the home page, it somehow seems like some sort of caching error. 
  I really don't know how I could debug this, or what to do.</p>
  
  <p>Thank your for every possible help in advance!</p>