The jPlayer download (zip) by default extracts to a folder named jQuery.jPlayer.[version].

So I ended up with the folder:
sites/all/libraries/player/jQuery.jPlayer.2.0.0

However, Audio Field only found the library after I renamed the folder to:
sites/all/libraries/player/jplayer

The behaviour is fine but could it please be documented?

Also, while I was working this out, the status message "You must install and select at least one player to be able to play the audio" appeared persistently on every page, which probably isn't the intention.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Tebb’s picture

I had the same problem with the module not finding the player files and tried the same rename of the downloaded folder to jplayer making it:

www.domain.co.uk/es/sites/all/libraries/player/jplayer/Jplayer.swf
www.domain.co.uk/es/sites/all/libraries/player/jplayer/jquery.jplayer.mi...

I also tried renaming the latter to:

www.domain.co.uk/es/sites/all/libraries/player/jplayer/jplayer.min.js

None of these worked for me and I'm still getting the message:

"You must install and select at least one player to be able to play the audio."

The only thing I can think of is that it's a multilingual site with path a prefix.

Tebb’s picture

Ooops, my ftp client was caching the filenames, so they were not what I thought.

The library is being correctly detected now using:

www.domain.co.uk/es/sites/all/libraries/players/jplayer/jquery.jplayer.m...

(Anyone copying this should note that I changed the 'player' directory to 'players' in the configuration too as it seems more natural language.)

The flash file is Jplayer.swf. I have not checked that this works yet, just that the module detects the javascript.

pardalman’s picture

Thanks God of this post !! I could not find the way to install jPlayer !!!
I agree with the issue

kingfisher64’s picture

I keep getting a green message on every page.

"You must install and select at least one player to be able to play the audio."

I have tried installing jplayer and the standalone wordpress player. No matter what path I give to the players I receive that message.

sites/all/libraries/players/jQuery.jPlayer.1.2.0/Jplayer.swf
sites/all/libraries/players/audio-player/player.swf

I've read the documentation on: http://drupal.org/node/973194 however it keeps popping up.

Since it's a green message as opposed to one of those nasty red one's does this mean everything is working ok? Obviously I don't want this message on every screen however I'll put up with that if I know everything is good.

Thanks for any help

pjcdawkins’s picture

Priority: Minor » Normal
Status: Needs work » Active

kingfisher64: rename the folder sites/all/libraries/players/jQuery.jPlayer.1.2.0 to sites/all/libraries/player/jplayer

kingfisher64’s picture

I've done what you suggested, however it's still coming up with a green message on every page.

Ideally I would like to use the wordpress standalone player.

I've installed 2 players and both come up with that green "error?" message. The following file paths that have been referenced to no sucess are:

sites/all/libraries/player/audio-player
sites/all/libraries/player/jplayer
/sites/all/libraries/player/audio-player/
/sites/all/libraries/player/jplayer/

I'm running drupal 7.7 and audiofield-7.x-1.0-beta3.tar.

It's an unusual message popping up. On one side there's a green tick suggesting that everything is ok and on the other the wording suggests that I haven't set the correct path for a player.

Does this message go away one properly configured? Or is it correctly configured, since it's a green message not a red error one.

Thanks for any help again.

pjcdawkins’s picture

kingfisher64: does the file sites/all/libraries/player/jplayer/jplayer.swf exist?

The 'green error message' is what I got too (until I corrected the filename as per the OP) but it's not your fault, it's a design & coding error in the module. Beyond that I'm sorry I can't really help.

The purpose of this thread is to highlight and track this bug in AudioField, and hopefully get it fixed.

kingfisher64’s picture

Hi pjcdawkins,

The following does definitely exist. I've done quite a few combos before posting on the site. It does the same when referencing the standalone wordpress player.

sites/all/libraries/player/jplayer/Jplayer.swf

I've just finished testing the mod. The file uploads fine, but when the mp3 is clicked the default browser player, plays the file not either the jplayer of wordpress player. So it's not referencing the players correctly.

All your work is very much appreciated - as I don't want you to think I was complaining that I couldn't get it to work, I just want to help you get rid of this message, by giving you as much info as possible. I love this mod so hopefully you can pinpoint the problem. :)

VM’s picture

Wordpress player seems to work fine on this end. I used the 7.x -dev version for testing.

My suggestion is to check the permissions on the following folders

/libraries < unnecessary check if you are using other modules which store their files in libraries
/player
/audio-player

Of note, my players are simply put in sites/all/libraries

sites/all/libraries/audio-player for example.

After the player is found it must be selected on config screen using the radio select for the player in use.

I'd much prefer that this module used instances for players so that more than one player could be used in different parts of the site, similar to how the mp3player.module does. Would also be of benefit to be able to style the wp player from the config. Though these are feature requests and I'll consider filing them if I choose to use this module beyond testing.

kingfisher64’s picture

I still can't get this green message to disappear and get the module to recognise the player libraries. I'm using the 7.x -dev version, trying to replicate what you've done to success. This is the only module I can't get to work properly that i've installed and configured. I've got a libraries folder present as quite a few other modules are using this. I'm the administrator on the website and administrator permissions are checked (as well as authenticated user) just to make sure. To do with permissions I assume your'e referencing the modules > audiofield > permissions options.

I've done everything mentioned in this thread, the readme file to no success. When the module is installed and enabled the performance of the site goes down drastically. I'm not if it's requesting something over and over again as this green message has popped up 4 times in one go before now.

Thanks for trying to help me, but i think I'm going to have to give up. It's a real shame as I would of loved to use the mod, but I just can't think of anything else to do to try and get it working properly.

VM’s picture

To do with permissions I assume your'e referencing the modules > audiofield > permissions options.

incorrect. The folder permissions on the server itself. ie: CHMOD

kingfisher64’s picture

If you would be so kind as to tell me how to get this done, i'll give it a try. I did google drupal 7 chmod but there was no tuts on how this is done.

Thanks

VM’s picture

It's not drupal specific. It's environment specific. Your hosts documentation or OS docs will aid here.
Not knowing the environment you are running there is no way for me to give a step by step.

http://www.google.com/#sclient=psy&hl=en&source=hp&q=file+folder+permiss...

I'd suggest setting this module up on a fresh install with no other modules. Perhaps it will aid in getting to the bottom of your issue. There may be a module conflict going on. I've tried to reproduce the issue twice today and cannot. Each time I've walked through it. The wordpress player shows up and works as expected. However, I've chosen another route (module) altogether.

good luck.

kingfisher64’s picture

My environment is windows 7 64bit, testing the mods on localhost using wampserver 2.1. From the research I just did it looks a case of just right clicking on the folder > properties > security tab, and changing the permissions to Allow for all. This was done to no success.

Thanks again.

VM’s picture

@ Kingfisher64 on the config screen what is in the text box as the path to the player folder?

kingfisher64’s picture

I've tried quite a few paths. According to the readme the top one is the correct path for the wordpress player.

/sites/all/libraries/player/audio-player/player.swf
/sites/all/libraries/player/audio-player/
/sites/all/libraries/player/audio-player

sites/all/libraries/player/audio-player/player.swf
sites/all/libraries/player/audio-player
sites/all/libraries/audio-player
sites/all/libraries/audio-player/

I've had a go at anything I could think of. Tried creating folders sites/all/libraries/players/, also tried just copying the contents of the players into the root libraries dir and referencing it direct. I've cleared drupal's cache several times for every directory change as well, just to make sure.

I've never had so much trouble trying to install a mod.
Out of interest what are you using for an audio player?

Thanks

tamerzg’s picture

The path in config page should be : sites/all/libraries/player
then if you use wordpress player it should be located at sites/all/libraries/player/audio-player/player.swf

Can you try dev version of module? Also can you post screenshot of your config page?

kingfisher64’s picture

FileSize
15.45 KB

Issue 1 - Clean install

Right i've just setup a new clean test site installing only the libraries folder, libraries mod and audiofield (dev version). The player shows up on the config page as a radio button option. So that's great, however having created the audiofield content type, created the content itself - there is no sign of the player when the audio file is clicked. It's just the browser default (firefox 5) playing. I've tried clearing the drupal cache and have tried both jplayer and the wpaudioplayer. I've added mp3 to the "Allowed file extensions".

Issue 2 - Original Install (Previous issue mentioned in this thread)

So now the logical thing is to go through installing each module or libraries I had in the non-working site with audiofield installed, until something breaks? since in the clean version the player shows up on the config screen.

Could anybody give me a list of modules/libraries they have installed that works with audiofield, so I can exclude them for the elimination process.

I've attached the screenshot of the original problem.

In summary the clean install shows the players in the configuration > audiofield page. The older installation with lots of modules installed still won't find the player.

VM’s picture

the audiofield that you created = you have to set the display of the field under manage display to the player IIRC

as far as the older install goes, the only way to figure out where a module conflict is , is to replicate the install in a dev environment and start disabling modules.

kingfisher64’s picture

Right so I have to set in the audiofield content type > manage display to the player? I've attached a snapshot of the options I have for the audiofield. Should it be showing the player within this drop down list? The audio option has a config cog graphic to the right, however when audio is selected this disappears and the display goes wrong.

I'll do your suggestion for the older install.

Many thanks again.

VM’s picture

yes. Audio.

Display goes wrong? What does that mean? and does that happen on the vanilla install?

if on the install with a bunch of modules: you're still at having to work backwards to try and figure out where the conflict is coming from. The more contrib modules installed the more likely that a module conflict is occurring. Without knowing which modules that is so that it too can be looked at it's difficult to try and narrow down.

kingfisher64’s picture

On the clean install when the audio option is selected from the drop down list the output goes very wrong (pics attached). I've tried bartek and garland themes, both display the same.

I'm going to have a look at the other install with lots of mods today so see what's going on.

VM’s picture

looks to me like you are either using the wrong version of the library which is 2.0.0 for D7 or there is something wrong with the calling of the jplayer css file.

please confirm that ONLY the 2.0.0 version of jplayer is in the libraries folder.

kingfisher64’s picture

I've checked it's the 2.0 library downloaded from http://www.jplayer.org/

VM’s picture

Then I'm totally at a loss for why it isn't working on your end. Not sure what else to have you look at , at this point.

kingfisher64’s picture

I'm giving up on this mod for now. I just can't get it to work, and don't have the time to try and fix these issues. Thank you for all the help given though, it was much appreciated. :)

VM’s picture

Category: feature » support
Status: Active » Closed (cannot reproduce)

Based on comment #26 and the fact that I can't reproduce this issue. I'm marking as such.

pjcdawkins’s picture

Category: support » feature

@VM: while we don't seem to be able to help kingfisher64, please consider my OP which was a request for better documentation of the library location.

VM’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

patches welcome that you think would better aid others. If you aren't up to speed with creating a patch. attaching a rewritten readme.txt to this issue would be welcome.

When I read through it and installed it for the first time to aid here, I had no issues in following the directions. (Which isn't to say others aren't having issues). That said, I don't know how to better word the readme.txt for users who are having difficultly understanding the current readme.txt. There is little the module can do about how the js library maintainers package their scripts or the way any specific program may extract them into folders.

Perhaps adding that spaces and periods non alpha characters shouldn't be used in folder naming schemes regardless of how it's packaged or extracted?

Keep in mind that at any time the folder naming scheme from the jplayer js library can change at any time. Especially since the folders naming scheme based on your extraction is based on version of the js library downloaded at that time. So not being too wordy/specific seems the best way forward here.

The current readme.txt states to extract the compatible players and put them in to the /player/ folder for all players.

unzip the audio players directly into the "player" folder.

Thus they don't need to be in separate folders. Every player could be sitting in the /player/ folder which is how I had set it up. I didn't need the /jplayer/ folder at all.

It seems that what is happening here is users aren't extracting/or uploading the player, but they are also uploading the folder the player is included in?

Suggestions toward a solution here are more than welcome. Just stating to make the readme.txt better doesn't help any one better understand how to word something so that those users are better aided by the readme.txt.

Based on your experience and the difficulty you ran into, what specific wording would have aided you? or made it "better" since that's an awfully subjective term.

Otherwise, this thread lives on for other users to find who may have difficultly?

VM’s picture

Status: Closed (cannot reproduce) » Postponed (maintainer needs more info)

remarking as postponed until such time as someone who's having difficulty offers up some suggestion that makes sense in a general manner for the readme.txt

mvc’s picture

Status: Closed (cannot reproduce) » Postponed (maintainer needs more info)
mvc’s picture

Version: 7.x-1.0-beta3 » 7.x-1.x-dev

ideally this would explain to users where to find the required libraries and where to put them much like wysiwyg does.

another thing to clean up in the documentation: despite the screenshot on the module page, adding a file Sample_Track.mp3 doesn't do anything (there's no reference in the code). it would be a nice feature to have, though.

Daniel.Moberly’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Fixed

The README has been updated in dev to provide much clearer installation instructions.

Status: Fixed » Closed (fixed)

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