WP Audio Player WordPress

Nirav Sheth comments:

Sorry - here's the link:

http://www.djmosoul.com/

And here's a link to the track itself:

http://www.djmosoul.com/wp-content/music/hey-bhagwan.mp3

This track plays fine for me since I'm logged in. But if you go visit it, it returns an error page from something I don't know how to find.

Dan | gteh comments:

For some reason it is redirecting you to a page with the id of 245 . Check what page that is in your WordPress pages list and then go through the wp-audio player settings to see if there's any permissions set for listening to files.

Im installing a copy now to check it out for myself.

Dan | gteh comments:

also, from what I can see, that plugin is only compatible up to Wordpress 2.9.2 and you are on 3.01 so there may be compatibility issues.

Nirav Sheth comments:

What do you click on that redirects you to ID 245? Are you referring to the audio player link itself? I'm happy to provide you the ID of any page if you think it will help. Just let me know.

The player has been working fine for me for several months with 3.01. It was working fine for several months until one day I changed the setting for Encoding on the plugin itself. Now my .mp3 files don't ever play and instead show an endless buffering tag. The files do play for me when I'm logged into Wordpress. But when I'm not logged in, it doesn't work.

Dan | gteh comments:

I found page id 245 by looking at the source code and finding the ID of the post div.


<div class="post" id="post-245">
<h2>Not Allowed</h2>


I installed it myself and it seems to be working with encoding turned on.


I'm trying to replicate the problem. If you disable encoding does it start working again?

Nirav Sheth comments:

I've disabled the encoding for a few days now. Still same issue. It seems that after I disabled encoding, it didn't actually disable. It says it's disabled, but still same functionality is showing. And it's redirecting people to that post ID you mentioned.

Dan | gteh comments:

My money is on W3 Total Cache.

Try clearing the w3 cache after disabling encrpytion to see if everything starts working again, possibly turn off that plugin and see what happens.

Dan | gteh comments:

w3 total cache shows static HTML pages to your visitors, but not you since you are logged in you see current pages. If you disable encryption, then clear the w3 total cache and temp files, I'll probably be able to view the site.

Nirav Sheth comments:

I've disabled w3 total cache. But I don't know how to clear the cache itself after I disabled the plugin. Or if I have to.

Dan | gteh comments:

If you disable the plugin, then it clears the cache. There's also a setting in teh w3 total cache settings to just empty the cache.

Problem still exists though so I am not sure what else it could be. If you don't figure it out and you don't mind, I can pop in to your admin section and check it out.

Nirav Sheth comments:

That totally works for me. I sent admin access to you via "message".

Dan | gteh comments:

thanks got it.

On February 08, 2011 you created the 'Not Allowed' page. Do you remember why you needed to create that page? I want to see what is causing the .mp3 files to redirect to that page when not logged in.

Nirav Sheth comments:

Any luck?

Dan | gteh comments:

no luck yet sorry.

Do you remember why or what plugin created the 'Not Allowed' page in your wordpress pages? All requests for .mp3 get redirected to that page so Im trying to trace where that came from

Nirav Sheth comments:

It's this plugin itself that created that page. I'm also searching for the same. What I'm actually doing is viewing the source code between working edition and non-working edition. I'm logged into the backend using Chrome and I'm not logged in using Safari. It's the only way I can trace the code difference.

Dan | gteh comments:

that is similar to what Im doing

The fact that it works when logged in means there is an instance of if (current_user_can()..... and I found a few instances inside the plugin itself but all related to the admin section.

Dan | gteh comments:

odd thing is when I installed the plugin on my own site, it never created that 'not allowed' page so Im stumped as to why the plugin created it for you automatically on your site

Nirav Sheth comments:

Did you enable encryption on the plugin settings?