Hi,

Followed your installation video to the letter, player shows up on node, but the mp3 file is not found. Using Firebug I can see that the embed code is fine (I copied the URL in the player's embed code and pasted into a browser tab - file played using browser default player fine).

Any reason for this? Is it a problem with clean URLs or Pathauto etc?

Thanks

Comments

jaybee1001’s picture

Title: Player reports "File Not Found" » SOLVED - Player reports "File Not Found"

Turned-off encoded URLs.

jdelaune’s picture

Status: Active » Closed (works as designed)
BD3’s picture

Title: SOLVED - Player reports "File Not Found" » Player reports "File Not Found"

Also gets a 'file not found error' if there is a slash (/) in the clean url.

It would be nice to have organized urls such as www.mysite.com/audiofiles/category/audiofilename

I can change it to www.mysite.com/audiofiles_category-audiofilename with no problems, must be the slash?

BD3’s picture

Does anyone know if this is by design as well, or something with the URL alias that it doesn't like? Any help would be greatly appreciated!

BD3’s picture

Status: Closed (works as designed) » Active
B-Dot’s picture

I can confirm that with clean URLs turned on, the path to the MP3 does not resolve.

Turning off clean URLs solves the issue, but it is hardly a solution.

This is a great module - it would be wonderful to see this fixed.

bohz’s picture

I think this is critical.
the module should work with clean URLs.
It's a pity...

my bad: I did enable "Encode: YES" but did not save config.

With encoding enabled everything works, for me.

thanks

vas01’s picture

Hey, this has been bugging me for a while now. I have the module in a block on the front page, if i have Encoding Enabled it displays File Not Found errors on every node. If i have Encoding Disabled, then on about 1/4 nodes it displays "File Not Found" errors, its always the same songs. I tried other modules to play the same files and everything works fine, but this module matches my site the most, hope to see it work. By the way i tried both the newest Dev and the Stable, same thing on both.

pacasum.repocusin’s picture

i got to fix the issue by removing spaces in the filename. ex. "Artist - title.mp3" yields to that error. Changing it to "Artist-title" fixes the problem. Hope this helps. :)

boreg’s picture

Assigned: Unassigned » boreg

The problem with clean urls still appears. It's irrelevant to encoding file URL etc. The problem appears only with the slash (/) in the node URL as Birdeye Design mentioned.

michaelcchastain’s picture

I believe the problem that some people are seeing is the type of relative url they are using. take for example the following hrefs

<a href="link1"></a>
<a href="/link2"></a>

imagine these links are being called from this current url: drupal.org/node/600248.

link1 will resolve to drupal.org/node/link1.
link2 will resolve to drupal.org/link2.

I believe the example in the docs does not include the leading forward slash on the url which is necessary. This would explain why some of you are able to get mp3 player to work when only one step away from your root domain(i.e. rootdomain.com/onestep) but not when 2 or more steps away(i.e. rootdomain.com/twosteps/away) which will not resolve correctly to the root domain. And thus sites/mysite/files will not be correctly resolved.

Wrapping it up:
When calling the mp3player theme function do it like so:

<?php print theme('mp3player', 'Default', "/" . $node->field_mp3['0']['filepath'], $node->field_title['0']['value'], $node->field_artist['0']['view'], NULL); ?>

note the quoted forward slash for the file path.

Michael