I installed the AudioField module 7x-1.0-beta 6 (http://ftp.drupal.org/files/projects/audiofield-7.x-1.0-beta6.zip) on a clear drupal7.14 install on localhost (XAMPP) on a Windows PC. I kept the default Google media player. After creating a new content type with a field type File and Audio Upload widget, I created a new node with an mp3 file. On saving the node, I got the error message: Notice: Undefined index: in audiofield_get_player() (line 122 of C:\xampp\htdocs\drupal713\sites\all\modules\audiofield\audiofield.module). and a strange looking media player. I was using the Chrome browser. Here is the screen shot:
Then I displayed the same node on Firefox, and got the error message though a little better looking media player but nothing happens on clicking the play button. Here is the screen shot on Firefox.
And I got the same error message on Internet Explorer. The media player appears to be the Windows media player.
Has anyone used the AudioField player on Drupal 7.14? Can someone try it on a clean install on a Windows localhost and post the results?
Comment | File | Size | Author |
---|---|---|---|
audiofield3.PNG | 77.77 KB | tax14 | |
audiofield2.PNG | 60.85 KB | tax14 | |
audiofield1.PNG | 54.65 KB | tax14 |
Comments
Comment #1
berenddeboer CreditAttribution: berenddeboer commentedI had a look at this module, and it's current state is fairly shocking. No clue what works and will work, but probably only the exact setup of the developer will work.
This module needs some love, it's not even in alpha state.
Comment #2
tamerzg CreditAttribution: tamerzg commentedYou forgot to choose default mp3 player from audiofield settings (admin/config/media/audiofield), therefore it will default to browser embedded player, which is rendered differently based on your OS or browser. However now I commited some changes to dev which will preset default player to google reader, which should always be available since it doesn't require installation on your server.
Comment #3
rileyv CreditAttribution: rileyv commentedInstalled AudioField on a 7.12 deployment.. Only the wordpress player shows up once installed in /sites/all/player, but even then, when creating a new content type, there is no option for an audio field of any kind.
If it's any help, I also have MediaFront installed, dunno if there are conflicts there.
Comment #4
tamerzg CreditAttribution: tamerzg commentedWhen installing the players have you followed instructions here: http://drupal.org/node/973194
See "Where to extract the players?" section.
Problem with 3rd party players is that they keep changing folder structure from version to version, and we can't keep changing it in our module or it would break users using the older versions of players. So the best way is to follow the instructions.
If you install dev version you should also see Google reader player, which doesn't require any installation on your server. Also if you enable Flowplayer module (http://drupal.org/project/flowplayer) you should get Flowplayer without any additional installation.
As for the audio field in content type, its located under File => Audio upload.
Comment #5
Taxoman CreditAttribution: Taxoman commented(After browsing several issues in the queue, it...)
Sounds like this is an indication of the need for clearer/more documentation.
I am about to evaluate the latest beta7, and will report back here with some suggestions for improved docs, or confirming that the docs are sufficient if so.
Comment #6
hyperidler CreditAttribution: hyperidler commentedI am using beta8 and selected the default to be jplayer, Google reader mp3 player, and then XSPF slim player, and the player still utilizes the default web browser player in Firefox and in IE. In addition, only a link shows for the file (no pause, play, and stop buttons) and the player opens a new tab to play the mp3.
I am using Drupal 7.16 and have all modules up to date.
For some reason the default display for the audio field was set to "file." Once I changed it to Audio with file download it works fine.
Comment #7
YesCT CreditAttribution: YesCT commentedNeeds work status usually means there is a patch on the issue and there is something about the patch that needs fixing in order to fix an issue. Active status usually means no patch yet/under discussion. Just setting the status to be more clear for this issue that there is no patch (that needs work).
Comment #8
Daniel.Moberly CreditAttribution: Daniel.Moberly commentedI don't believe any of these issues remain as of the latest release of the module. Installation is fairly straightforward and all players work cross-browser.