WordPress.org

Plugin Directory

Changeset 594343


Ignore:
Timestamp:
09/04/12 09:24:49 (20 months ago)
Author:
ntm
Message:

8.8.10.14 beta 24

Location:
podpress/trunk
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • podpress/trunk/podpress.php

    r586206 r594343  
    11<?php 
    2 define('PODPRESS_VERSION', '8.8.10.14 beta 23'); 
     2define('PODPRESS_VERSION', '8.8.10.14 beta 24'); 
    33/* 
    44Info for WordPress: 
    55============================================================================== 
    66Plugin Name: podPress 
    7 Version: 8.8.10.14 beta 23 
     7Version: 8.8.10.14 beta 24 
    88Plugin URI: http://www.mightyseek.com/podpress/ 
    99Description: The podPress plugin gives you everything you need in one easy plugin to use WordPress for Podcasting. Set it up in <a href="admin.php?page=podpress/podpress_feed.php">'podPress'->Feed/iTunes Settings</a>. If this plugin works for you, send us a comment. 
     
    273273            } 
    274274            $podPress = new podPressAdmin_class(); 
    275             if($podPress->settings['enablePodangoIntegration']) { 
     275            if ( TRUE === isset($podPress->settings['enablePodangoIntegration']) AND TRUE == $podPress->settings['enablePodangoIntegration'] ) { 
    276276                podPress_checkmem('PodangoAPI code loaded', true); 
    277277                require_once(PODPRESS_DIR.'/podango-api.php'); 
    278278                $podPress->podangoapi = new PodangoAPI ($podPress->settings['podangoUserKey'], $podPress->settings['podangoPassKey']); 
    279                 if(!empty($podPress->settings['podangoDefaultPodcast'])) { 
     279                if ( TRUE === isset($podPress->settings['podangoDefaultPodcast']) AND !empty($podPress->settings['podangoDefaultPodcast']) ) { 
    280280                    $podPress->podangoapi->defaultPodcast = $podPress->settings['podangoDefaultPodcast']; 
    281281                } 
    282                 if(!empty($podPress->settings['podangoDefaultTranscribe'])) { 
     282                if ( TRUE === isset($podPress->settings['podangoDefaultTranscribe']) AND !empty($podPress->settings['podangoDefaultTranscribe']) ) { 
    283283                    $podPress->podangoapi->defaultTranscribe = (int)$podPress->settings['podangoDefaultTranscribe']; 
    284284                } 
     
    355355    /* misc stuff */ 
    356356    // the dashboard widget: 
    357     if ( TRUE === $podPress->settings['enableStats'] ) { 
     357    if ( TRUE === isset($podPress->settings['enableStats']) AND TRUE === $podPress->settings['enableStats'] ) { 
    358358        if ( (TRUE == isset($podPress->settings['disabledashboardwidget']) AND FALSE === $podPress->settings['disabledashboardwidget']) OR FALSE == isset($podPress->settings['disabledashboardwidget']) ) { 
    359359            if ( TRUE == version_compare($wp_version, '2.7', '>=') ) { // for WP >= 2.7 add the stats overview as a dashboard widget 
     
    375375 
    376376    /* stuff for premium podcasts */ 
    377     if ( isset($podPress->settings['enablePremiumContent']) AND TRUE === $podPress->settings['enablePremiumContent'] ) { 
     377    if ( TRUE === isset($podPress->settings['enablePremiumContent']) AND TRUE === $podPress->settings['enablePremiumContent'] ) { 
    378378        require_once(PODPRESS_DIR.'/podpress_premium_functions.php'); 
    379379        podPress_checkmem('premium functions included'); 
     
    552552function podPress_activity_box() { 
    553553    GLOBAL $podPress, $wpdb, $wp_version; 
    554     if ( TRUE === $podPress->settings['enableStats'] ) { 
     554    if ( TRUE === ($podPress->settings['enableStats']) AND TRUE === $podPress->settings['enableStats'] ) { 
    555555        if ( TRUE == version_compare($wp_version, '2.8', '>=') ) { 
    556556            // get the plugins version information via the WP plugins version check 
  • podpress/trunk/readme.txt

    r586206 r594343  
    9999 
    100100= v8.8.10.8 = 
    101 <strong>Notice:</strong> Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
     101**Notice:** Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
    102102 
    103103* bug fix: an upgrade to this version will remove an old deprecated option which could lead to the situation that podPress would add "Download Standard Podcast" somewhere in the iTunes:summary or iTunes:subtitle of post.  (Thank you [IAmediaworks](http://wordpress.org/support/profile/iamediaworks) for [reporting the problem](http://wordpress.org/support/topic/upgrade-added-download-standard-podcast-to-itunes-episode-description).) 
     
    112112 
    113113= v8.8.10.7 = 
    114 <strong>Notice:</strong> Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
     114**Notice:** Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
    115115 
    116116* bug fix: the function which limits the number of characters for several feed elements is multibyte-character-safe and it does not cut through htmlentities anymore (Thank you [franky1029](http://wordpress.org/support/profile/franky1029), [welshes99](http://wordpress.org/support/profile/welshes99) and [drezac](http://wordpress.org/support/profile/drezac) for [reporting the problem](http://wordpress.org/support/topic/podpress-player-doesnt-show-in-post).) 
     
    121121 
    122122= v8.8.10.6 = 
    123 <strong>Notice:</strong> Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
     123**Notice:** Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
    124124 
    125125* bug fix: a further bug fix for the feed modifying functions. podPress is using now the WP-own list of HTML entities and their numeric equivalents (ent2ncr();) to transform non-ASCII characters in the additional feed elements into RSS-feed-save text. (Thank you [Aaron Frankel](http://wordpress.org/support/profile/aaronfrankel) for [reporting the problem](http://wordpress.org/support/topic/88105-xml-feed-still-down).) 
    126126 
    127127= v8.8.10.5 = 
    128 <strong>Notice:</strong> Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
     128**Notice:** Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
    129129 
    130130* bug fix: a further bug fix for the feed modifying functions 
     
    132132 
    133133= v8.8.10.4 = 
    134 <strong>Notice:</strong> Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
     134**Notice:** Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
    135135 
    136136* bug fix: for a problem with not escaped ampersands in iTunes:category names which appeared in 8.8.10.3 (Thank you [BibleStudyRadio](http://wordpress.org/support/profile/biblestudyradio), [UULosAlamos Webmaster](http://wordpress.org/support/profile/uulosalamos-webmaster),  [AJRitz](http://wordpress.org/support/profile/ajritz) and [raymer](http://wordpress.org/support/profile/raymer) for [reporting the problem](http://wordpress.org/support/topic/plugin-podpress-itune-feed-incorrect).) 
     
    138138 
    139139= v8.8.10.3 = 
    140 <strong>Notice:</strong> Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
     140**Notice:** Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
    141141 
    142142* The 3rd party statistic options are available again by default. If you have used them before then please control the related settings after the upgrade. 
     
    151151 
    152152= v8.8.10.2 = 
    153 <strong>Notice:</strong> Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
     153**Notice:** Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
    154154 
    155155* bug fix: podPress displays the download number for files with white spaces in their names in the "Downloads Per Media File" table and in the line below the player (Thank you [SmartPeoplePod](http://wordpress.org/support/profile/smartpeoplepod) for [reporting the problem](http://wordpress.org/support/topic/plugin-podpress-podpress-stats-per-post-are-gone-help).) 
     
    157157 
    158158= v8.8.10.1 = 
    159 <strong>Notice:</strong> Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
     159**Notice:** Upgrading to this version from version 8.8.9.2 or older will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
    160160 
    161161* bug fix: the jQuery and jQueryUI libraries are getting loaded correctly, regardless whether the file system on the server is case sensitive or not 
    162162 
    163163= v8.8.10 = 
    164 <strong>Notice:</strong> Upgrading to this version will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
     164**Notice:** Upgrading to this version will rename the podPress `meta_key`s in the postmeta data base table of your blog (see bug fixes). Downgrading to a previous version is only possible if you reverse these changes. 
    165165 
    166166* a new option at the General Settings page of podPress to display the file size of the media files along with the duration in the line below the player (or player preview) 
     
    232232= v8.8.8.2 = 
    233233* now, podPress is going to take over the meta information of the Feed with the slug name "podcast" during a direct upgrade from podPress v8.8.6.3 or an older version to v8.8.8.2. But you should also control all the Feed Settings after the upgrade. 
    234 * bug fix: a further fix for the <em>Always before the <!- More -> tag</em> option 
     234* bug fix: a further fix for the *Always before the <!- More -> tag* option 
    235235* bug fix: now, the filter filters not only the posts with certain podPress attachments, it filters also the enclosures in the feed. (If you choose .m4a files the for instance a post with a m4a file and a mp3 file will appear in the Feed but only the m4a file will be visible as an enclosure of this post.) 
    236236 
     
    252252* all image files which are 80x15 buttons for Feeds have a new name scheme: feed_button-{name of the feed}.png 
    253253* redesign of the Feed/iTunes Settings page 
    254 * a new filter hook <em>podpress_post_content</em> for the complete podPress section of posts with podPress attachment (for the sections `<!-- Begin: podPress --> ... <!-- End: podPress -->`) 
     254* a new filter hook *podpress_post_content* for the complete podPress section of posts with podPress attachment (for the sections `<!-- Begin: podPress --> ... <!-- End: podPress -->`) 
    255255* upgrade to [getID3](http://www.getid3.org) v1.8.1 (1.8.1-20101125) 
    256256* bug fix: for a JS problem with the new input field ids of the category form in WP 3.x 
     
    459459Upgrading from 8.8.6.3 (or older version) to 8.8.8.x (or newer versions): 
    460460If you have used the widgets of podPress then it will be necessary to reactivate these widgets manually after an upgrade. The reason for these cirumstances are the massive modifications on both podPress widgets. The widgets will try to take over the old settings as far as possible. 
    461 podPress adds feeds to your blog. These Feeds have the names <em>podcast</em>, <em>premium</em>, <em>enhancedpodcast</em> (since 8.8.5) and <em>torrent</em> (since 8.8.5). In the past versions, you could not control these Feeds and their meta information via a settings page. That is why v8.8.8.x has a new section at the Feed/iTunes Settings page (which has also a new design). With this new podPress Feeds section in place, the purpose of the Feed Settings section has changed. Now, the Feed Settings section is for controlling the iTunes tags and other settings only of all the main Feeds of the blog (like the default Entries RSS2 Feed) and the podPress Feeds section is for controlling the additional Feeds which podPress adds to your blog (like <em>podcast</em>). In the past all the Feeds have shared the same information from the Feed Settings section. If you are using at least one of these Feeds to publish your podcast episodes or to route them to Feedburner or iTunes or a comparable service then you need to fill in the information about this Feed like the content description or the URL of Feed icon into the new podPress Feeds section. You may copy and paste the information from the Feed Settings section or you could use the chance to customize these information. If you are using a non-default Permalink scheme then you should save the Permalink settings after the podPress upgrade. You should also re-save the Permalink setting after you have changed, activated, deactivated or renamed a Feed or if you are using the podPress the first time in your blog).  
     461podPress adds feeds to your blog. These Feeds have the names *podcast*, *premium*, *enhancedpodcast* (since 8.8.5) and *torrent* (since 8.8.5). In the past versions, you could not control these Feeds and their meta information via a settings page. That is why v8.8.8.x has a new section at the Feed/iTunes Settings page (which has also a new design). With this new podPress Feeds section in place, the purpose of the Feed Settings section has changed.  
     462Now, the Feed Settings section is for controlling the iTunes tags and other settings only of all the main Feeds of the blog (like the default Entries RSS2 Feed) and the podPress Feeds section is for controlling the additional Feeds which podPress adds to your blog (like *podcast*). In the past all the Feeds have shared the same information from the Feed Settings section.  
     463If you are using at least one of these Feeds to publish your podcast episodes or to route them to Feedburner or iTunes or a comparable service then you need to fill in the information about this Feed like the content description or the URL of Feed icon into the new podPress Feeds section. 
     464You may copy and paste the information from the Feed Settings section or you could use the chance to customize these information. If you are using a non-default Permalink scheme then you should save the Permalink settings after the podPress upgrade. You should also re-save the Permalink setting after you have changed, activated, deactivated or renamed a Feed or if you are using the podPress the first time in your blog).  
    462465podPress v8.8.5 and newer versions require at least WP 2.1 but it is recommended to use at least WP 2.3. To be able to use the full feature set (e.g. for multiple widget support) of podPress, you should use at least WP 2.9.x. 
    463466Upgrading to v8.8.10 is going to rename the podPress `meta_key`s in the postmeta data base table of your blog (`podPressMedia` becomes `_podPressMedia` and `podPressPostSpecific` becomes `_podPressPostSpecific`). Downgrading to a previous version is only possible if you reverse these changes. 
     
    465468 
    466469== Upgrade, Configuration and Other Notes == 
     470 
    467471= Upgrade = 
     472 
    468473Upgrading from 8.8.6.3 (or older version) to 8.8.8.x (or newer versions): 
    469474If you have used the widgets of podPress then it will be necessary to reactivate these widgets manually after an upgrade. The reason for these cirumstances are the massive modifications on both podPress widgets. The widgets will try to take over the old settings as far as possible. 
    470 podPress adds feeds to your blog. These Feeds have the names <em>podcast</em>, <em>premium</em>, <em>enhancedpodcast</em> (since 8.8.5) and <em>torrent</em> (since 8.8.5). In the past versions, you could not control these Feeds and their meta information via a settings page. That is why v8.8.8.x has a new section at the Feed/iTunes Settings page (which has also a new design). With this new podPress Feeds section in place, the purpose of the Feed Settings section has changed. Now, the Feed Settings section is for controlling the iTunes tags and other settings only of all the main Feeds of the blog (like the default Entries RSS2 Feed) and the podPress Feeds section is for controlling the additional Feeds which podPress adds to your blog (like <em>podcast</em>). In the past all the Feeds have shared the same information from the Feed Settings section. If you are using at least one of these Feeds to publish your podcast episodes or to route them to Feedburner or iTunes or a comparable service then you need to fill in the information about this Feed like the content description or the URL of Feed icon into the new podPress Feeds section. You may copy and paste the information from the Feed Settings section or you could use the chance to customize these information. If you are using a non-default Permalink scheme then you should save the Permalink settings after the podPress upgrade. You should also re-save the Permalink setting after you have changed, activated, deactivated or renamed a Feed or if you are using the podPress the first time in your blog).  
     475podPress adds feeds to your blog. These Feeds have the names *podcast*, *premium*, *enhancedpodcast* (since 8.8.5) and *torrent* (since 8.8.5). In the past versions, you could not control these Feeds and their meta information via a settings page. 
     476That is why v8.8.8.x has a new section at the Feed/iTunes Settings page (which has also a new design). With this new podPress Feeds section in place, the purpose of the Feed Settings section has changed. Now, the Feed Settings section is for controlling the iTunes tags and other settings only of all the main Feeds of the blog (like the default Entries RSS2 Feed) and the podPress Feeds section is for controlling the additional Feeds which podPress adds to your blog (like *podcast*).  
     477In the past all the Feeds have shared the same information from the Feed Settings section. If you are using at least one of these Feeds to publish your podcast episodes or to route them to Feedburner or iTunes or a comparable service then you need to fill in the information about this Feed like the content description or the URL of Feed icon into the new podPress Feeds section. You may copy and paste the information from the Feed Settings section or you could use the chance to customize these information. 
     478If you are using a non-default Permalink scheme then you should save the Permalink settings after the podPress upgrade. You should also re-save the Permalink setting after you have changed, activated, deactivated or renamed a Feed or if you are using the podPress the first time in your blog).  
    471479Upgrading to v8.8.10 is going to rename the podPress `meta_key`s in the postmeta data base table of your blog (`podPressMedia` becomes `_podPressMedia` and `podPressPostSpecific` becomes `_podPressPostSpecific`). Downgrading to a previous version is only possible if you reverse these changes. 
    472480 
     
    487495 
    488496= Feeds of podPress = 
     497 
    489498podPress adds not only iTunes-tags and <enclosure>-tags to your usual RSS feed. It adds e.g. a feed called "podcast" (http://example.com/?feed=podcast), a feed called "playlist.xspf" (http://example.com/?feed=playlist.xspf) and a feed called "premium" (http://example.com/?feed=premium). 
    490499The podcast feed contains all the posts which have at least one media file added with podPress despite the categories the post is in. It is not necessary to put all the post with podcast episodes in a category called podcast. (There is one constellation you should avaoid: If you name a sub category podcast and you are using e.g. the Permalink structure "Date and name" then the URL http://example.com/category/parentcategoryname/podcast/ leads to the feed called podcast and not to the category view.) 
     
    501510 
    502511= Filter Hooks of podPress = 
     512 
    503513Since v8.8.5 you can filter some parts of the output of podPress 
    504514 
     
    535545 
    536546= How-To use custom variables for the XSPF player: = 
    537 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). 
     547Create 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). 
     548The 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.  
     549The 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). 
    538550 
    539551 
     
    594606= How can I set a post specific license and license URL? = 
    595607 
    596 Define two custom field per post. One with the name <strong>podcast_episode_license_name</strong> and the name of the license as the value and one custom field with then name <strong>podcast_episode_license_url</strong> and the URL to the full license text. It is necessary to define at least the URL. If the name is not defined then the name will be the URL. 
     608Define two custom field per post. One with the name **podcast_episode_license_name** and the name of the license as the value and one custom field with then name **podcast_episode_license_url** and the URL to the full license text. It is necessary to define at least the URL. If the name is not defined then the name will be the URL. 
    597609 
    598610= I have a post and have added two (or more) media files via podPress. Why is it not possible to mark them all for the usage in a RSS Feed? = 
Note: See TracChangeset for help on using the changeset viewer.