Hi there,

The audio player uses HTML5, not flash, so the tracks must be loaded in order for the audio player to actually play the audio.

Best,

Chris

Cool, but the way the tracks keeps appearing in the source code ... Ideally hide the tracks in the source code ...

NVM. Got it.

Cheers,

Kade

Do you know where the "scripts" folder and "custom.js" is usually installed. I am haveing a hard time finding it.

Thanks,

Kade

Hey, I am only using the Word Press version, so that's all I can speak to. Perhaps the author or an HTML version user can let you know. But in terms of the strategy (covering links with span elements), it should be universally applicable.

Hi Vukmaster!

Thanks for the info above.

Quick question, will this work for the standard html version or only on Word Press?

Thanks again!

glad it's coming in handy :D

Thanks a million!

Great Addition! Thank you for the share!

Excellent, this was one of my biggest concerns with Nocturnal. Definitely implementing this in, thanks!

Thanks for sharing.

The theme allows you to attach audio to posts, but this also leaves it vulnerable to download via right-click > save as. You can use low quality, shortened, sound-marked samples to deter downloads, but this may also deter users from playing the audio. You can disable right-clicks with javascript, but this is annoying, only works if users don't take anti-javascript measures, and goes against standards. I have a couple small modifications that can protect your audio from download without disabling the right-click. No tech abilities required, other than copy/paste. Basically we add a span element that sits on top of each song link element as a blocker. We transfer it's mouse events to the audio file's events while preventing the right click from accessing the song link or revealing the file name in the status bar.

For an example, see my post at http://vuklazar.com/?p=118

Note, savvy users can still find ways around it, but the effort required probably outweighs the cost of buying music.

Here we go.

1) css: add this into your custom css area (option tree plugin) or into the theme's style.css (appearance > editor)to make sure the new span elements sit right on top of the song links

.songs li {
	position: relative !important;
	display: block;
	float: left;
	overlfow: hidden;
}
.dlblock {
	position: absolute !important;
	height:100%; width:100%;
	z-index:2;
	background:none !important;
}

2) php: go to appearance > editor and add the span element to archive.php, index.php, page.php, search.php, single.php, and category.php. They all contain the same foreach loop with 3 'echo' lines. Add the span right before each song link is retrieved so the loops look like this

foreach ($attachments as $attachment) {
	echo "<li>";
	echo "<span class='dlblock'></span>";
	echo wp_get_attachment_link($attachment->ID);
	echo "</li>";
}

3) javascript: tie the new span's mouse events to the original link's events by adding this into custom.js (in the scripts folder under the theme installation, not accessible through WP as far as I know). It's recommended you add this under the "//SONG STUFF" section. Note click events work differently and don't need to be tied.

var songBlock = jQuery("ol.songs li span");
songBlock.live('mouseover', function(){
	jQuery(this).next('a').trigger('mouseover');
});
songBlock.live('mouseout', function(){
	jQuery(this).next('a').trigger('mouseout');
});

And that's it. I tested in Google Chrome and IE on a PC and found no issues.