Player appears paused and in uncontrollable [#1359716]

I have this weird 'bug' with the jplayer. This is what I use:

- Jplayer module 6.x 1.0-beta3
- Jplayer 2.1
- Audiofield 6.x 1.0

I got everything installed good: the module tells me he found the jplayer library succesfully and I set up a random content type with only one custom field: audiofield. When I upload a track (mp3) and save the node, the player shows up like it should, but is completely uncontrollable and is paused already. This happens on both single player and multifile player displays and it appears in all browsers.

Seems to be an annoying bug and I don't know how to resolve this.

Anyone else having this problem?

Comment	File	Size	Author
#6	jplayer-1359716-fix-js-syntax-error.patch.patch	423 bytes	smoothify

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

damiandab CreditAttribution: damiandab commented 5 December 2011 at 15:26

I have the same problem :(

Comment #2

damiandab CreditAttribution: damiandab commented 5 December 2011 at 15:45

Priority:

Major

» Critical

tested also with dev version.

I get below message in firebug:

missing ) after argument list
[Break On This Error] $(player).jPlayer({

Comment #3

apoc1 CreditAttribution: apoc1 commented 7 December 2011 at 10:12

Anyone who has an idea how to resolve this?

Comment #4

BTMash CreditAttribution: BTMash commented 12 December 2011 at 22:49

The way to resolve this as far as I see is to add ); to line 82 of jplayer.js (inside theme) so that

becomes

});

However, I run into another issue after this with the error b.test is not a function. And I get this with both 6.x-1.0-beta3 and with 6.x-1.x-dev.

Comment #5

BTMash CreditAttribution: BTMash commented 12 December 2011 at 22:53

Ok, one resolution I see for the 6.x branch is that jplayer-2.x is actually not compatible with jplayer 6.x. So you need to download jplayer 1.2.0 for it to all work correctly (along with the above patch).

Comment #6

smoothify CreditAttribution: smoothify commented 5 February 2012 at 00:02

Version:	6.x-1.0-beta3	» 6.x-1.x-dev
Status:	Active	» Needs review

File	Size
jplayer-1359716-fix-js-syntax-error.patch.patch	423 bytes

I came across the same issue, and confirm that BTMash's solution works (thanks)

And I can also confirm, you do need jPlayer 1.2 to be installed.

Here is a patch that makes the change.

Comment #7

guldi CreditAttribution: guldi commented 7 February 2012 at 10:55

I chose jplayer 1.2.0, played the patch.

Now the js-error is ok, but the player still not responding.

Comment #8

smoothify CreditAttribution: smoothify commented 7 February 2012 at 13:29

@guldi: have you cleared your cache and done a forced browser refresh? (Ctrl + F5, or Command + R)

Comment #9

guldi CreditAttribution: guldi commented 9 February 2012 at 11:21

Yeah. Sure.
Sorry I can't help with this issue anymore. Had to choose another tool.
Happy with swf-tools.

Good luck!

Comment #10

deviantintegral CreditAttribution: deviantintegral commented 16 February 2012 at 15:55

Status:

Needs review

» Fixed

Thanks for the patch. I found one other missing semicolon with jshint and fixed that as well.

Comment #11

1 March 2012 at 16:00

Status:

Fixed

» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Comment #12

ricksta CreditAttribution: ricksta commented 13 April 2012 at 00:11

Status:

Closed (fixed)

» Active

I have the same problem as described above. I changed to the 1.2 version. I also get no error now.

I tried the fix for line 82, but I already had "})" instead of his "}" and when I added the semicolon after what I had, it broke it again and there was no play button.

I now have a play button but nothing happens when I click it. I've tried your patch but I don't think I'm applying it correctly. Can you tell me how to use the patch you attached?

thank you.

Rick

Comment #13

deviantintegral CreditAttribution: deviantintegral commented 25 May 2012 at 20:42

Priority:

Critical

» Normal

At this point, you'd be better off just running the 6.x-1.x-dev release. I'll be rolling a stable release soon, and we're using that code in production ourselves.