` container). If you want to use this filter hook then make sure that the filtered result still contains the span element with an id like this: `''`. This span element is in the filter input. Do not replace all of the content. * podpress_post_content (since 8.8.8): a filter for the complete podPress section of posts with podPress attachment (for the sections ` ... `) * podpress_post_scriptblock (since 8.8.10.9): a filter for the Javascript block of the podPress section of posts with podPress attachment * podpress_legacy_support_feed_icon (only in combination with WP < v2.2): it is a possibility to add a feed icon in front of each line of the Feed Buttons widget in text mode * podpress_posts_distinct (since 8.8.10): a filter for the modifications which podPress adds to the DISTINCT part of the posts query of WP * podpress_posts_join (since 8.8.10): a filter for the modifications which podPress adds to the JOIN part of the posts query of WP * podpress_posts_where (since 8.8.10): a filter for the modifications which podPress adds to the WHERE part of the posts query of WP = How-To use a different skin for the XSPF player: = Since v8.8.5 podPress uses the [XSPF player created by Lacy Morrow](http://blog.lacymorrow.com/projects/xspf-jukebox/) which has the possibility to use customized player skins. podPress includes a default skin. But it is also possible to use different skin files. These skin files are XML files and need to be placed in sub folders of the wp-content/ folder e.g. /wp-content/plugins/podpress_options/xspf_options/custom/skin_1_{width}x{height}.xml. Since v8.8.8 the default folder for these files is outside of the folder of podPress and the naming scheme of the skin files is different. Furthermore it is necessary to copy the podpress_xspf_config-sample.php file into the /wp-content/plugins/podpress_options/ folder, to rename it to podpress_xspf_config.php and to edit it. If you place that configuration file into a separate folder as suggested then it will endure an automatic plugin upgrade. The name of the skin file and the custom variables file are skin_1_{width}x{height}.xml and variables_1.txt. The "_1" in the file names (and in the names of the constants) stands for the blog ID. In the single blog mode the blog ID is 1. If you have an multiple site blog installation (WP 3.+ or WPMU), the main blog ID is also 1. The skin file names need to contain also the width and height. You can find these values inside these the skin.xml files. It is also necessary to use these width and height values in the widgets settings. If you change with or height in the widgets settings then you need to rename the file again or you need a separate file which has the new values in the file name. For instance if you want to use the player in one sidebar of the main blog with the width 210 pixels and on an other page with the width 600 pixels then you need two files e.g. skin_1_210x210.xml and skin_1_600x210.xml. A skin file name for a widget of the first sub blog would be e.g. skin_2_170x210.xml. Note that the width needs to be at least 150px, the height at least 100px and the height of the slim player at least 30px. Please, look also into the podpress_xspf_config-sample.php file (new since v8.8.8) for further information about the usage of such skin files. The "[XSPF Jukebox skin.xml Specification](http://lacymorrow.com/projects/jukebox/skindoc.html)" are documents which explain how-to make such a file. But you can also use one of the [existing skins](http://blog.lacymorrow.com/projects/xspf-jukebox/). podPress uses a derivative of the SlimOriginal skin by default. (Since v8.8.8, podPress uses for the player skin no separate files.) = How-To change the XSPF playlist URL = If you have a custom XSPF playlist e.g. a .xspf file and you would like that the player uses this custom playlist then you can insert the new URL in the widgets settings (or define the constant PODPRESS_CUSTOM_XSPF_URL_x with the URL of this custom playlist (At the end of the file podpress_xspf_config-sample.php is a prepared line of code.). The `x` in the name of the constant stays for the ID of the blog.). The URL has to be an URL to a playlist which is on the same domain/server as your blog! But it is allowed that the tracks in the playlist can be situated on a different server. = How-To use custom variables for the XSPF player: = Create a sub folder in the plugins folder of your blog e.g. /wp-content/plugins/podpress_options/xspf_options/variables (create a different one for the slim player e.g. /wp-content/plugins/podpress_options/xspf_options/variables_slim/). Copy the podpress_xspf_config-sample.php file from the podpress folder to the podpress_options/ folder. Rename it to podpress_xspf_config.php and uncomment the line with constant PODPRESS_XSPF_USE_CUSTOM_VARIABLES_1 (or PODPRESS_XSPF_SLIM_USE_CUSTOM_VARIABLES_1 for custom variables for the slim player). The number 1 in the name of the name of the constant is stands for the ID of the blog (it is 1 for the main blog of a multi site installation or a single blog). If you want to define different variables for XSPF player in different (sub) blogs then you need to define constant and variables files with their IDs too. The last stept is to create the variables files and place them in the variables (or variables_slim) folder. They have the naming scheme variables_{blog ID}.txt. For more information about all possible variables see the [documentation of the XSPF Jukebox](http://lacymorrow.com/projects/jukebox/xspfdoc.html). == Frequently Asked Questions == Please, use the WP.org [Plugins and Hacks forum](http://wordpress.org/tags/podpress?forum_id=10) to ask your questions or for bug reports. When you post in this forum please add at least the tag "podpress" to your post. That makes it very much easier to get a notice of your post (There is a [RSS feed of forum posts which are tagged with "podpress"](http://wordpress.org/support/rss/tags/podpress).). (The domain name of the official [podPress FAQ](http://podcasterswiki.com/index.php?title=PodPress_FAQ "Official podPress FAQ") page is currently (03/2010) unavailable resp. parked. You can still find some [traces of this Wiki at Archive.org](http://web.archive.org/web/20080708140114/podcasterswiki.com/index.php?title=PodPress).) = What does podPress with the Feeds? = * podPress adds automatically additional elements (e.g. [iTunes RSS tags](http://www.apple.com/itunes/podcasts/specs.html#rss)) to the default RSS Feeds of your weblog. But it can be used to modify also diverse elements of the ATOM Feeds of a blog. You can find most of the related options at the Feed/iTunes settings page of podPress. Furthermore it is possible to configure these options for each category Feed separately. This feeature is called Category Casting and you can activate and configure it for existing post categories at the page where you can edit the settings of a category. * But podPress adds also completely new Feeds to your weblog. These Feeds might be RSS or ATOM Feeds and you can control the content of the Feed for instance with a category filter or a file fype filter. You can configure those Feeds also at the Feed/iTunes Settings page of podPress in the section podPress Feeds. = How can I create multiple Podcast Feeds? = There are basically two ways: * One way is to use the Category Casting feature to adjust all kinds of podcast related elements in the category feeds of the blog. WordPress produces these category Feeds and you can customize them with podPress. These Feeds containing posts of one category. You activate the Category Casting feature while you edit an existing category in which you edit an existing category. * The other possibility is to add one or more additional, new Feeds to the blog with the help of the settings of the podPress Feeds section at the Feed/iTunes Settings page of podPress. You can influence the content of these podPress Feeds with the help of a category filter and a file type filter. With the file type filter you can determine that a Feed contains for instance only posts with .mp3 or .m4a podcast episodes regardless of the categories of the posts. But it is also possible to create something like category Feed with the category filter. But with the differences that you can select more than category per Feed and that such podPress Feeds have maybe nicer URLs. (Notice: After creating a podPress Feed, after changing a slug name or after (de-)activating such a Feed, you need to re-save the Permalink settings of your blog.) = How can I add podcast episodes with podPress? = First you need to upload the podcast files with WordPress or probably with a FTP client software. (Often podcast files are to big to upload them with a web formular like the WordPress Media Uploader. in such case you will need to use a FTP client software or comparable program.) It is basically a good idea to store the podcast files in sub folders of the /wp-content/uploads/ folder of your blog. After you have uploaded a media file, you create or edit the post (or page) which should contain an episode. Below the editor box you will find a separate box with the title "podPress - postcasting settings for this post". There you insert the complete URL of the podcast file and enter or determine automatically some meta information about the current episode like the duration or the file type and size. While saving or publishing the post these podcast information are getting saved as well. (You can get probably a good impression how it works from [this WP.org forum thread](http://wordpress.org/support/topic/356947) although the original question is a little bit different. This [other WP.org forum thread](http://wordpress.org/support/topic/425141) might also be helpful.) = Does podPress has HTML5 support? = Yes. podPress (since 8.8.10) embeds .mp3, .ogg and .ogv media files with the HTML5 `