In the past, Blubrry has stated that this error:
WordPress database error MySQL server has gone away for query SELECT t.*, tt.* FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON tt.term_id = t.term_id INNER JOIN wp_term_relationships AS tr ON tr.term_taxonomy_id = tt.term_taxonomy_id WHERE tt.taxonomy IN ('post_tag') AND tr.object_id IN (5) ORDER BY t.name ASC made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), do_feed, do_action('do_feed_podcast'), call_user_func_array, powerpress_do_podcast_feed, do_feed_rss2, load_template, require_once('wp-includes/feed-rss2.php'), do_action('rss2_item'), call_user_func_array, powerpress_rss2_item, wp_get_post_tags, wp_get_post_terms, wp_get_object_terms
(or ones similar to it being generated by Powerpress) is only because of the mysql server at the webhost, which never made 100% sense to me, since one site will throw this error now and then, while another site on the same server won't throw this error once a year.
If it were the mysql server, wouldn't all those sites on the same server throw that same error more often, or at all?
I did some comparisons, and literally the only difference I've found so far is between using PHP 5.3 and PHP 5.4... is it possible that there's something with using PHP 5.3 that causes Powerpress to hang and generate this timeout where using PHP 5.4 does not?
I ask this because one site I have had to be moved to a new server recently. That new server doesn't have PHP 5.4; it had been running PHP 5.4 on the previous server and the site never generated this error, but now running only PHP 5.3, it throws this error almost all the time.
The webhost hasn't gotten back to me yet on whether there's something different enough between their PHP version installs that might explain this, but maybe the Blubrry guys can find something faster on their end?