• Resolved Bob

    (@bobk88)


    From Chrome’s error console:

    Uncaught Error: cannot call methods on slider prior to initialization; attempted to call method ‘option’ query.js:2

    Safari’s error console says the same (except it omits the word ‘uncaught’).

    This started after I updated from WordPress 3.4.2 to 3.5 yesterday.

    Safari 6.0.2, Chrome 23.0.1271.97, running in Mac OS 10.8.2 on a Mac Pro 8-core.

    mp3-jplayer 1.7.3 with customized GUI (customization was not done by the plug-in’s author, and AFAIK it did not involve altering Javascript – just css)

    This error doesn’t seem to occur in Firefox 17.01. It correlates with several problems – files not playing back, multiple songs being selected at once upon successive clicks, page jumping up to the top after clicking on a song, problems with time display, etc.

    I tried the following, and the problems remained:

    1. switched to the Twenty Twelve theme

    2. disabled all other plugins

    3. tried SCRIPT_DEBUG per these instructions in the Codex

    Clearing the browser cache and then re-loading the page seems to resolve the issues in Safari, and then the player works as expected; but this doesn’t seem to help in Chrome.

    Test page is here.

    http://ww.wp.xz.cn/extend/plugins/mp3-jplayer/

Viewing 10 replies - 16 through 25 (of 25 total)
  • same problem… hope the developer can find a solution for these great plugin.

    well for me it seems that the problem come from the plugin Tubepress… If you deactivate it, everything is working fine.

    The developer send an email today that the fix is ready and should be out in a few days. I’m hoping a few days is quick, so I send a 20 GBP donation his way. If you want a fix soon, I suggest others do the same.

    This is the best way I know to motivate and reward developers for their effort. After all, I’m sure this guy has put in a ton of work on this. And, that’s all work I didn’t have to do myself πŸ™‚

    Thread Starter Bob

    (@bobk88)

    Anyone new to this thread: I encourage you to read my previous couple of posts.

    Bottom line: if you need a reliable music player, I would recommend not using this, for the following reasons:

    1. It’s been broken in Safari and Chrome since the release of WP 3.5 nearly two months ago (see original posts for details).

    2. For at least the past year (when I started using it), the current version has not correctly displayed playlists in recent versions of Opera in recent versions of Mac OS X (and PC too, if I recall correctly). I thought it was a CSS problem, but a developer recently suggested that it’s a jQuery problem.

    3. Developer has not answered any forum posts for over 9 months.

    4. Plugin hasn’t been updated in nearly 17 months.

    5. Two weeks ago the dev told me the update would be released over the weekend, and that didn’t happen.

    As I said in my review, Simon seems to have put a lot of work into this plugin, and it has useful features and flexibility that I haven’t seen in other music player plugins, free or premium.

    If the reasons I mentioned above don’t matter to you, then go for it.

    When I wrote the dev he supplied this info a week or so ago:
    ME- how long till update?

    DEV- Three weeks (we haven’t started yet) but it will be similar to http://ww.wp.xz.cn/extend/plugins/wp-miniaudioplayer/stats/ Will be about a month before releasing.

    ME- Cool…thanks for reaching out. When the new version is released will it be in WP repo again or a premium offering?

    DEV- It will be a premium offering at around $20. We’re busy creating jPlayer.it which aims to be a store where you can download free and paid-for skins and plugins.

    Thread Starter Bob

    (@bobk88)

    Scott: was that correspondence with Simon? Or with one of the Happyworm guys?

    I’m asking because one of the Happyworm guys is in Italy (according to their site), and the .it domain is Italy. Also, the developer of the plugin linked in your message is Italian, so I’m wondering if they might be collaborating. And that plugin is completely different from mp3-jplayer. ( And if the new plugin is similar to the one in the link, why not just use that?)

    Just to be clear: All the correspondence I’ve mentioned in this thread has all been with Simon, the dev of mp3-jPlayer.

    Whoever it is, their communication skills are lacking. First they say three weeks, then a month. Oh, yeah, and: they haven’t started yet.

    That was with Mark from Happyworm. I am a bit confused also as to whether they are upgrading or creating an entirely new plugin!

    Thread Starter Bob

    (@bobk88)

    Thanks for the clarification.

    Though based on jPlayer, mp3-jPlayer is completely separate – Simon made significant mods and additions when coding his plugin. So please, let’s keep clear on what we’re talking about in this thread! πŸ˜‰

    One final thing about jPlayer: as I mentioned above, if you need something right away, I recommend using it directly, and since you’re a dev, you’d probably find re-skinning easy. I started with Happyworm’s Blue Monday skin and, knowing just a little CSS, made a very different GUI (though I couldn’t do the volume slider mod myself).

    I’ll be interested in what Happyworm comes up with.

    Good luck!

    I just updated with the new release that came out yesterday.

    Everything works beautifully again!

    And, I like some of the new features too πŸ™‚

    Thread Starter Bob

    (@bobk88)

    Great!

    I had to move on, but hopefully I can use 1.8 as a backup. That will involve some editing of php, javascript, and css files, since I’m using a modded version of 1.73. Or I might end up writing my own plugin…

Viewing 10 replies - 16 through 25 (of 25 total)

The topic ‘Javascript error in Safari & Chrome, WordPress 3.5’ is closed to new replies.