Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I did everything indicated, and there's no options for Audio Player in the admin settings.
Comment | File | Size | Author |
---|---|---|---|
#4 | audio.module.txt | 48.07 KB | johnflower |
#11 | 1.jpg | 51.29 KB | Anonymous (not verified) |
#11 | 2.jpg | 52.82 KB | Anonymous (not verified) |
#11 | 3.jpg | 54.67 KB | Anonymous (not verified) |
Comments
Comment #1
Jorge Campo CreditAttribution: Jorge Campo commentedSame issue.
Comment #2
savinsur CreditAttribution: savinsur commentedditto, no player option.
Comment #3
johnflower CreditAttribution: johnflower commentedTry http://your.website/admin/settings/audiofield
You will also need to change lines 56, 57, & 58 in audiofield.module from
to
Comment #4
johnflower CreditAttribution: johnflower commentedI've changed this from support request to a bug report with a priority of critical. I did this because the purpose of the module is to play sound and it cannot without a change in the code.
I've attached a patched audio.module file. I also corrected some spelling and grammatical errors, and improved descriptions on the admin screen. This should fix the problems in version 6.x-1.0-beta1. You'll need to remove the '.txt' extension from the file and then drop it in your audiofield module folder
Comment #5
CinemaSaville CreditAttribution: CinemaSaville commentedIs this a patch for audio.module or for audio_field.module?
Comment #6
savinsur CreditAttribution: savinsur commentedto
$player1=realpath("sites") . "/all/libraries/player/audio-player/player.swf";
$player2=realpath("sites") . "/all/libraries/player/xspf_player_slim.swf";
$player3=realpath("sites") . "/all/libraries/player/playerSinglePackage/playerSingle.swf";
making the above changes results in a blank white page.
Comment #7
marclauren007 CreditAttribution: marclauren007 commentedThanx alot. worked for me.
Comment #8
Jorge Campo CreditAttribution: Jorge Campo commentedChanging to forward slashes also worked for me perfectly well.
Thanks a lot Johnflower!
Comment #9
Anonymous (not verified) CreditAttribution: Anonymous commentedhello guys,
this Othman Adarbeh I am the maintainer of the Audio Field module.
I am sorry for being late to answer your questions,
to get this module works fine you have to enable CCK, filefield module and also Audio field, second step is to get the audio players from the links I just wrote in README file
create folder in libraries folder under \sites\all\libraries and name it player, extract the players on that folder.
once you done with the prevois steps go to site Configration you'll see Audio Field option from there you have the ability to change your default audio player.
Im sure you dont have to change backword slash to forward slash to get it work on windows but I didnt check yet if you have to replace the back slash with forward slash on other opearating system.
please feel free to ask me anytime.
Comment #10
savinsur CreditAttribution: savinsur commentedThat's better! I think I had a stray character in my copy and paste of your code.
All is working now, except one of the players has no screen / player example, just a radio button.
Need to investigate more.
Comment #11
Anonymous (not verified) CreditAttribution: Anonymous commentedsound good it is work with.to be sure thats you extract all the players in correct way I'll attach 3 snapshots it show the files you have to have it in the player directory .
make sure you have all files and folders in the photo on your player directory
Comment #12
johnflower CreditAttribution: johnflower commentedRe #5
Thank you for pointing out my error. I've fixed the offending post.
Re #9
The direction of the slashes is important for *nix based servers. If you change the sloshes to slashes it will still work on windows.
Three things that would simplify the install process:-
+ Include a small sound file with the module for testing the players.
+ Create a folder called players inside the module folder, eg sites/all/modules/audiofield/players.
+ Include at least one free player, like audio module does. 1pixelout perhaps? It's released under GPL2
The big selling point about this module is that it is lean. People can add functionality. As opposed to the audio module which for some people needs to be taken apart and rebuilt to suit their needs. Or the SWF tools modules which has a bewildering array of options.
Comment #13
Anonymous (not verified) CreditAttribution: Anonymous commentedthanks johnflower,
I'm going to relaese another version of audio field after make the changes of the module file.
the folder player should be in libraries folder, sites/all/libraries/player.
Comment #14
johnflower CreditAttribution: johnflower commentedJust to clarify, I'm proposing that, in the next release, the code be changed so that the players are contained within the module directory. I am not suggesting that users take my statement as an instruction on how to do things with the current module.
This would change the install process from:-
1) Download and unpack the audiofield module
2) Make a directory called libraries
3) Make a directory called players
4) Download and unpack the players
...
to:-
1) Download and unpack the audiofield module
2) Download and unpack the players
...
even better would be to include a player as the audio module does and the process is even shorter:-
1) Download and unpack the audiofield module
...
Comment #15
CinemaSaville CreditAttribution: CinemaSaville commentedI agree with John. The easier you can make it for end users/developers the better. We need to focus on making Drupal less tech intensive. There are so many modules with little quirks, that it's easy to get confused and frustrated. The technology should serve the creativity not impede it. Thanks again for this much needed module, and play counts would be a great addition as well.
Comment #16
Anonymous (not verified) CreditAttribution: Anonymous commentedI agree with guys, I did think to make the audio players included in the module file, but I didn't because the license issues and when you got the audio players from their providers it will be the newer versions. I really appreciate that care about audio field module.
Comment #17
CinemaSaville CreditAttribution: CinemaSaville commentedThanks, Othman for the valuable contribution to the community. This was a necessary module, and you stepped up. So keep on going. I'm sure you will figure this out.
Comment #18
q0rban CreditAttribution: q0rban commentedSubscribe.
Comment #19
jensimmons CreditAttribution: jensimmons commentedIt looks like the change from \sites\all\libraries\players to /sites/all/libraries/players has been made — is this correct? If so, you can set the status of this issue to fixed, Othman.
Meanwhile, I am trying to get this module to work on a complex multisite install, and having /sites/all/* hardcoded into the module means it will only work in the /all/ directory.
This is a slightly different issue, however, so I am going to open a new issue. #766104: Support multisite installs
Comment #20
jensimmons CreditAttribution: jensimmons commentedYou should update the documentation on the module page:
Extract the players in "\sites\all\libraries\player" folder.
to:
Extract the players in "/sites/all/libraries/player" folder.
Comment #21
tamerzg CreditAttribution: tamerzg commentedYes issue with forward slashes was fixed in last release. Actually we are preparing new version which will have players inside audiofield module instead of libraries folder. This should also solve issue with multisite installs.