Bob

I forgot to mention that I want to keep the limit at 20 MB, so I’m glad the plugin setting is being overridden.

Thanks for the reply – it’s good to know this should be OK.

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…

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!

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.

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.

Direct code is working fine so far.

Jplayer’s site has a ‘Quick Start‘ that walks you through the installation on a regular web site. You have to figure out how to adapt that to your WordPress theme.

I’m using a paid WP theme called Catalyst. It provides areas where you can insert scripts easily into pages, the header, or both. I’m using these, and they seem to be working fine.

If you don’t have that kind of feature, maybe you could write a simple plugin just to add the jplayer script(s) via ‘enqueue_script.’ (Or maybe there are plugins that make it easy to add your own scripts – try searching the repository.)

Note that WordPress uses jQuery in ‘no-conflict’ mode (see the above link, about half way down the page). The bottom line is that you have to write ‘jQuery’ instead of using the dollar-sign shortcut ($) in the script where you add the links to your audio files. There were only 3 or 4 instances of this, so it’s not a big deal.

Unfortunately, this is NOT mentioned on the jPlayer site, since their tutorial is aimed at regular (non-Wordpress) sites. Since I’m not a developer, I didn’t know the details about using non-included scripts with WordPress, and spent a lot of time wondering why jPlayer wasn’t working until I stumbled on the above page.

jPlayer requires the core jQuery library. In my site, other plugins are already calling in jQuery, so I didn’t need to include a script for that.

Note that in the Quick Start they link to an external jQuery library hosted by Google; if you weren’t already aware, you should either use WordPress’ included library, or disable it if you want to use an external one. Calling in two instances of a script can apparently cause problems and is not recommended.

Hope this helps.

Yes – the developer email me last week saying he fixed the plugin and it would be available over the weekend. That didn’t happen.

I recommend not using this plugin. I ended up using jplayer directly in my site (not via a plugin).

Last week, the developer said that a fixed update would be released over the weekend. Obviously that didn’t happen.

Unfortunately, I’ve had to move on and find another solution. I’m now using jPlayer directly in my site (not a plugin).

Though I don’t think I mentioned the ‘#’, that’s one of the results of the javascript/jQuery issue I reported in this thread.

There’s some conflict between the plugin and WP 3.5’s javascript/jQuery. The developer said there’s a new, fixed version coming soon, so let’s hope that’ll resolve the issue.

I’d been wondering about that.

But when I spoke with the developer yesterday, he said that mp3-jplayer first looks for WordPress’ included jQuery libraries (in the folder wp-includes); the versions in the plugin’s folders are only there in case they’re missing from WordPress for some reason.

Per his suggestion, I checked in Firebug and saw that indeed WordPress 3.5’s versions of jQuery (1.8.3) and jQuery UI (1.9.2) are being loaded.

I don’t know if this has any effect on the problem, but I told him that in WP 3.5, they changed the convention for suffixes for minified .js and .css files.

He said he’ll look into the issue, but didn’t say exactly when. Here’s hoping….!

More troubleshooting info to add to my above posts.

Here’s the simplest way to see the problem:

In Safari and Chrome (Mac), if the first thing you do after the page loads is click the ‘play’ button, the player seems to work ok. Subsequent clicks on another song will cause it to load and begin playback, as expected.

However, if the first thing you do after the page loads is click on a song title instead, that title loads into the ‘current track’ display at the top of the player, but playback does not start, and if you had to scroll down to see the player, the page jumps back up to the top.

If you then click on the play button, the selected song will play back, but with the following issues:

1. The ‘elapsed time’ readout remains at 0:00.

2, The ‘total time’ readout does not appear.

3. The playback progress bar does not appear, and clicking along the timeline does not have any effect (it should cause playback to jump to the location where you clicked)

More troubleshooting info to add to my above posts.

Here’s the simplest way to see the problem:

In Safari and Chrome (Mac), if the first thing you do after the page loads is click the ‘play’ button, the player seems to work ok. Subsequent clicks on another song will cause it to load and begin playback, as expected.

However, if the first thing you do after the page loads is click on a song title instead, that title loads into the ‘current track’ display at the top of the player, but playback does not start, and if you had to scroll down to see the player, the page jumps back up to the top.

If you then click on the play button, the selected song will play back, but with the following issues:

1. The ‘elapsed time’ readout remains at 0:00.

2, The ‘total time’ readout does not appear.

3. The playback progress bar does not appear, and clicking along the timeline does not have any effect (it should cause playback to jump to the location where you clicked).

Update: my test page has moved to here.

I’m a musician, so audio is crucial to my site.

I thought the usual recommendation is to stay with the latest version of WP since they fix security issues. So I’m basically afraid to go back! ??

I’m looking into using jplayer or soundmanager2 directly rather than via a plugin. I don’t yet know how to do that, but it might be worth it in the long run. I wouldn’t mind paying Soundcloud and using their players on my site, but I don’t like any of the GUIs (I don’t want to see waveforms except when I’m recording and editing!).

I deleted the plugin and did a fresh install. (Mine had a customized GUI with additional CSS and button images.)

The fresh install with default skin showed similar problems in Chrome and Safari (Mac).

The problem seems to involve the jQuery UI slider (ui.slider.js). Someone with more javascript experience echoed this finding, and suggested it might be a conflict between the older version of js included with the plugin and the newer version installed with the WordPress 3.5 update.

I emailed the developer about these issues, but so far haven’t heard anything. He appears to have abandoned this plugin, at least as of now. No posts from him in 9 months. Sad, because he seem seem to have put a lot of work into the plugin. And frustrating – I spent a lot of time customizing the GUI, and now I’m back to square one.