Hey Regis,
I’m betting it has something to do with the URL that member has posted. It needs to be the URL for the album. The plugin then searches that page to get the album’s unique ID #, which is added to the player’s code to make it embed properly. If the member has posted the URL for their membership page (not the album page), it may not find the unique ID #.
That “E HTML PUBLIC” is actually part of the beginning of the source code for the page. I’m not sure why that particular section is being grabbed. If could post the URL for that member, I can take a look.
Hey. Thanks for you response. I have verified the member IS posting the correct URL. Here’s his bandcamp page: http://ourfaircity.bandcamp.com/album/a-most-clever-disaster
Also, here is the complete IFRAME tag that is being loaded. The whole thing seems to be garbled.
<iframe width="150" height="295" loose.dtd"="" html4="" tr="" www.w3.org="" "http:="" en"="" transitional="" 4.01="" html="" dtd="" w3c="" -="" src="http://bandcamp.com/EmbeddedPlayer/v=2/album=E HTML PUBLIC " style="position: relative; display: block; width: 150px; height: 295px;">
The other strange thing I’m having with this member is that his soundcloud set is not working. Specifying a single track seems to work fine, but not a set: https://soundcloud.com/ourfaircity/sets/a-most-clever-disaster
Thanks so much,
Regis
Hey Regis,
I just updated the plugin to 0.3.1 to reflect the new Bandcamp player. I thought I had that sorted out, but it appears the new player has the album ID is a different place than the version 1 player did in the page’s source code. It should work for everyone now.
As far as the SoundCloud set, I’m going to guess that has something to do with the permissions on the set. I just played around with one of my sets and was able to remove the embed code from other people’s view of my player. I believe when you do this, it also disables the oEmbed, which is how the SoundCloud player works within this plugin. They may need to change their permissions to allow people to embed that player.
Thanks so much for your super quick response to this issue slushman!
Now I will start a new thread for my next issue : )