W3C Validator/XHTML/DOCTYPE/PODPRESS

Hi dael3,

in general it is a better idea to leave the code of the plugin as it is.

Since 8.8.5, podPress has e.g. the Filter Hook podpress_downloadlinks which gives you a possibility to filter the content of the line below the player preview or player.

You should use this hook to filter all the target="new" attributes which are not allowed in XHTML Strict (but e.g. in Transitional).

Create a PHP file and name it for instance podpress_filters.php.
The filter plugin (content of this file) could be look like this:

<?php
/*
Plugin Name: podPress filters
Plugin URI:
Description: some filters for podPress
Author: ntm
Version: 1.0
Author URI:
*/

add_filter('podpress_downloadlinks', 'filter_some_podpress_code_elements');
function filter_some_podpress_code_elements($podpressdownloadlinks) {
	$podpressdownloadlinks = str_replace('target="new" ', '', $podpressdownloadlinks);
	return $podpressdownloadlinks;
}
?>

Put the file into the /wp-content/plugins/ folder or a sub folder of that folder and activate the new plugin.

This filter removes all target="new" from these links.

All other podPress Hooks are listed in the podPress / Other Notes section.

Regards,
Tim

I will put out a new podPress version (probably) tomorrow and I’m going to include the filter plugin (or maybe some other solution).

BTW: you can add CSS for the podPress elements in the posts e.g. with

/* CSS for the podPress box */
.podPress_content {
...
}

/* CSS only for <div> box which contains the player or player preview */
podpress_playerspace {
...
}

/* CSS only for line with links below the player or player preview */
.podPress_downloadlinks {
...
}

podPress v8.8.8.1 has a new option at its General Settings page with name “do not use the target="new" attribute in links of podPress” which will help with the validity of the HTML output of podPress.