WordPress.org

Forums

MP3-jPlayer
script error in firefox (5 posts)

  1. Christer2011
    Member
    Posted 2 years ago #

    Thanks for your plug-in, now after the update to 1.8.3, I get script error in firefox but not in chrome.

    Regards
    Christer

    http://wordpress.org/extend/plugins/mp3-jplayer/

  2. simon.ward
    Member
    Plugin Author

    Posted 2 years ago #

    Could you post the error up please?

  3. SaulOGrady
    Member
    Posted 2 years ago #

    I've noticed the same problem:

    "Warning: Unresponsive script

    A script on this page may be busy, or it may have stopped responding. You can stop the script now,, or can continue to see if the script will complete.

    Script: http://whatever the url is/:22

    Don't ask me..."

  4. Christer2011
    Member
    Posted 2 years ago #

    Same as SaulOGrady
    /Christer

  5. simon.ward
    Member
    Plugin Author

    Posted 2 years ago #

    Had a look into this, and just fixed a similar error for somebody. Here's what I found:

    1) Common cause for this error seems to be facebook scripts/plugins, so make sure you remove/deactivate them before doing any testing with the player.

    If you still have problems, read on:

    2) If you update plugins manually, make sure you are overwriting the old Jplayer.swf file with the new one, it's vital. The plugin will not work with the old swf.

    3) The install I just debugged still had the player's old .swf file on the server, despite the user having updated the plugin via admin (where plugin gets deleted and the new one uploaded). They had to go into their hosting account (godaddy) and use file manager to delete it from the server, and then re-upload it. Very strange, but there you go.

    To test if this may be the problem for you (unlikely as it may sound) just go to the following url in your browser, replacing yoursite.com with your domain name:

    http://yoursite.com/wp-content/plugins/mp3-jplayer/js/Jplayer.swf

    You should see 'jplayer 2.2.0' on the page.

    If you don't then this is why you get the error (I'm assuming you're using 1.8.3, and plugin is in the regular location).

    Simon

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.