Installation seemed to be a success, and ive uploaded an mp3 file but the following message appears instead of the player..

It look's like you don't have Adobe Flash Player installed. Get it now.

I can view the player on your demo site, so obviously have flash installed (v9).

Any suggestions?

Comments

jdelaune’s picture

You have copied the swf and js file from the standalone player into the correct directory?

jlg’s picture

Status: Active » Closed (fixed)

That was the problem, I had them in the modules/mp3player not modules/mp3player/mp3player.

Thanks for your help.

szermierz’s picture

I've got the latest Flash Player installed in both IE and FF. I get the above message in FF but in IE the player shows up and runs fine.

spython’s picture

Same here, does not work in FF but works in Safari.

fenfe1’s picture

Status: Closed (fixed) » Active

I get the same thing!

jdelaune’s picture

Assigned: Unassigned » jdelaune
Status: Active » Fixed

Re-open if the beta1 version suffers the same fate.

andrewsuth’s picture

Have you checked if javascript is turned on?

In fact, the error message is not correct as there are 2 possibilities for this error appearing.

It should say something like:
"It looks like you either have Javascript disabled or you need to install Adobe Flash Player."

jdelaune’s picture

Correct thanks I've fixed this.

markomahony’s picture

Hi there,

I can't play my podcasts on Drupal 6.13. I have tried all the suggestions above:
- copied the swf and js files into modules/mp3player/mp3player
- ensured that javascript is enabled
- granted the audio module permissions

The results when I try to play the mp3 are as follows:
IE7 - "File not found"
Safari - "It look's like you don't have Adobe Flash Player installed. Get it now."
Firefox - "It look's like you don't have Adobe Flash Player installed. Get it now."

This works on IE7 in my test environment and I have set it up the same on the live site. Do you have any ideas for me?

Thanks a lot,
Marko

ggevalt’s picture

Version: 6.x-1.x-dev » 6.x-1.0-beta1
Status: Fixed » Active

My apologies: I think I accidentally changed the status to active when I posted (tried to undo, but not successfully); please disregard.

We were having the same issue:

Using the beta1 version
Javascript is enabled
swf and js files copied into modules/mp3player/mp3player
granted module permissions

FF -- "It look's like you don't have Adobe Flash Player installed. Get it now."
Safari -- player appears and ran as it should.

After some searching I tried clearing cache and player appeared in FF as well.

andrewsuth’s picture

@Starnox: I like the option offered in the SWF module where you can set your own message if Javascript / Flash is not installed/enabled.

Do you think you could implement the same flexability for this module?

markomahony’s picture

Guys,

Turns out it was a proxy server issue - all my set up was in place correctly.

Thanks for your posts.
Marko

hitori’s picture

For those who have it working on one browser and not the other.. clear your cache..
I had the problem it worked in FF and not in Safari, I then cleared the cache in Safari and it worked.
Credits to ggevalt (for reminding me again of the obvious thing to do in such a case)

looplog’s picture

hmm, this doesn't work for me, though I suspect my problem may be slightly different.

I have a filefield within a gmap view formatted as a mp3player. This works fine in Firefox, with the mp3player appearing in the gmap bubbles. Unfortunately, it won't show in any other browser, instead displaying the error as above. I tried flushing the cache but no luck there I'm afraid.

Any other ideas?

ilw’s picture

Cleaning the cache, that the point for FF!

braindrift’s picture

Hallo Guys,

I have a problem that could be related to this. I use the player inside a view. This view is shown with the module Views Display Tabs. One tab(display) shows me some images, and the other the mp3-files. All works fine as long as I click only once on the MP3-Tab. But when I click a second time on the MP3-Tab there apears the message: 'It look's like you don't have Adobe Flash Player installed. Get it now.'. To get this away I have to change to the Images-Tab and then come back.

Is it possible that the MP3 Player has a problem with Ajax-Requests? Is there any solution?

Thanks
dendie

braindrift’s picture

Category: support » bug
solipsist’s picture

Reply to dendie's problems with MP3 Player and Views Display Tabs:

I strongly suspect the problem dendie's reporting is caused by MP3 Player not implementing a JS-behavior as described here:
http://drupal.org/node/114774#javascript-behaviors

Without a behavior to instantiate the Flash player the MP3 Player won't be loaded when displays are switched and all you see is the static text informing you to get Flash played for your browser.

jdelaune’s picture

The JS in question isn't written by MP3 Player but by the WordPress Audio Player so I may have to look into writing a custom JS file for the Drupal. See #574656: Improve WP Audio Player JS (Do Not Use Inline JS)

jdelaune’s picture

Status: Active » Closed (fixed)
Max K.’s picture

For those of you who still haven't been able to figure it out, it looks as if there's a slight error in the latest version of the standalone mp3 player. Editing the first line to begin with "var swfobject=" should fix it.

fnapo’s picture

I love you :D
Yes, this was the problem :)

Enno’s picture

+1

Changing the audio-player.js file as described by #21 solved the problem.

benmirkhah’s picture

Thanks Max K.

"var audioplayer_swfobject="

needs to be changed to

"var swfobject="

in file audio-player.js

coloryan’s picture

Thanks! Editing the first line fixed it for me as well.

maverick14’s picture

#21 fixes this problem indeed - thanks

Gabriel R.’s picture

Status: Closed (fixed) » Active

#21 This is not doing it for me.

- The .js and .swf files are in the right place
- Cleared the caches of the browsers as well as Drupal's
- Javascript is enabled
- There are no extra permissions to enable, right?

No luck, stuck on It look's like you don't have Adobe Flash Player installed. Get it now.

Gabriel R.’s picture

The problem on my end is that the bit of JS declaring the AudioPlayer object is at the end of the page.

<script type="text/javascript"> 
<!--//--><![CDATA[//><!--
AudioPlayer.setup("/sites/all/modules/mp3player/mp3player/player.swf", {width:290});
//--><!]]>
</script> 

So when the page loads, the script invokes the object before it is loaded. Need to find a way to move that to the top of the page. Actually, it would be best to set the load of the object onpageload instead of right away.

I'll let you know.

Gabriel R.’s picture

Status: Active » Fixed

OK, so I moved my scripts to the top of the page. All working fine now. No need to edit the variable name as described in #21.

Status: Fixed » Closed (fixed)

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

coloryan’s picture

Deleted - wrong module - Sorry.

gjones’s picture

Version: 6.x-1.0-beta1 » 6.x-1.x-dev

I'm getting this same problem on the Beta1 and Dev versions.

Player and js are in sites/all/modules/mp3player/mp3player
Javascript is loading near the top

The message used to say:
"It look's like you don't have Adobe Flash Player installed. Get it now."

but now with the dev version it says:
"You may need: Adobe Flash Player."

Firefox, Chrome, Safari ... haven't tested IE

I've tried the fix from #21 on both versions...still doesn't work.

pflork’s picture

Hi All,
Same here. I've tried all the workaround suggested above. However this is still not happening. Any other Idea please ?

Thanks for your help.

icekream’s picture

How does this affect views that have the lightbox mode? I get this same text when I try to link it to a lightbox. works fine without the lightbox implementation

pacome’s picture

Subscribing
I have the same problem ; it doesn't work on both versions..
-p-

truyenle’s picture

I also have the same problem as #32 and #21 doesn't fix it.

Any clue for this?

Thanks

Whackler’s picture

Moving $scripts to the top of my page worked for me

brulain’s picture

Version: 6.x-1.x-dev » 6.x-1.0

Same issue after updating in 1.0.
Works fine after coming back to beta1.

Update: 1.0 works if the 2 files (audio-player.js and player.swf) are placed in '.../mp3player/' instead of '.../mp3player/mp3player/'. Strange, because 'Path to mp3 library' is setting to 'sites/all/modules/mp3player/mp3player'.
Update#2: I have putted again the 2 files in '.../mp3player/mp3player/' and deleted the 2 others in '.../mp3player/', and it works...
NB: each time, I have cleared Drupal and browser caches.

jdelaune’s picture

So after all those updates what was the outcome? It works?

beefheartfan’s picture

I upgraded to version 6.x-1.0 tonight. After doing so all my players say "You may need: Adobe Flash Player."

I tried clearing my browser cache and Drupal cache. The problem remains.

I tried changing the audio-player.js file as described by #21. The problem remains.

I tried moving the scripts to the header as described by #28. The problem remains.

Please let me know what else I can try. I run an online music store, so without the streaming samples it really cripples the site.

brulain’s picture

Yes, finally it works with normal settings.
So I apply the well knowed rule: if it works, don't touch...
Bye.

brulain’s picture

@beefheartfan
I encountered the same issue.
If there are error messages in your Drupal logs indicating it doesn't find the 2 stand-alone player files, copy them in the mp3player main directory (with the .info file) and clear Drupal caches. Perhaps it will solve your problem...

psmx’s picture

Status: Closed (fixed) » Needs work

Same problem here. I fixed by going to admin/settings/mp3player/global-settings and saving the configuration again. It looks like after the update the default path is set back to mp3player/ instead of mp3player/mp3player (or any setting you might have set before the update)

jdelaune’s picture

Status: Needs work » Fixed

Yeah I fixed this issue yesterday and rolled it out to the dev branch. Just rolled out a new stable release.

Status: Fixed » Closed (fixed)

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