hgetrost

Hi Angelo,

You would have found 46 instead of 45 because I set the new episode to show in RSS Feed after my testing. I have restricted it from the feed in case it was something to do the latest Ep.

We migrated to new servers last week and the nginx log files show the following error, looks like we might not have an xml parser in our new environment? Am waiting to hear back from our server guy but just thought to update you on what we’re looking at here.

2017/07/10 12:00:15 [error] 5425#5425: *5885749 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught Error: Call to undefined function xml_parser_create() in /DATA/public_html/upliftconnect.com/wp-content/plugins/powerpress/powerpressadmin-rss-import.php:1413
Stack trace:
#0 /DATA/public_html/upliftconnect.com/wp-content/plugins/powerpress/powerpressadmin-rss-import.php(722): PowerPress_RSS_Podcast_Import->_parse_enclosure(‘<enclosure typ…’, ‘\n <guid is…’, ”)
#1 /DATA/public_html/upliftconnect.com/wp-content/plugins/powerpress/powerpressadmin-rss-import.php(962): PowerPress_RSS_Podcast_Import->import_item(‘\n <guid is…’, Array, false, ”, ”, ”, ”, ”, false, ‘publish’)
#2 /DATA/public_html/upliftconnect.com/wp-content/plugins/powerpress/powerpressadmin-rss-import.php(1108): PowerPress_RSS_Podcast_Import->import_episodes(Array, false, 0, ”, ”, ”, ”, false, ‘publish’)
#3 /DATA/public_html/upliftconnect.com/wp-content/plugins/powerpress/powerpressadmin-rss-import.php(1201): PowerPress_RSS_Podcast_Import->import()
#4 /DATA/public_html/upliftco” while reading upstream, client: 192.88.134.18, server: upliftconnect.com, request: “POST /wp-admin/admin.php?import=powerpress-soundcloud-rss-podcast HTTP/1.1”, upstream: “fastcgi://unix:/run/php/php7.0-fpm.sock:”, host: “upliftconnect.com”, referrer: “http://upliftconnect.com/wp-admin/admin.php?import=powerpress-soundcloud-rss-podcast&#8221;

Hi Angelo,

Thanks for your response. Our iTunes feed is now Active again. I’ll run through what we’ve been doing here for your reference:

I also submitted a support request to apple at the same time I wrote to you and their response was: “As I can confirm the feed is valid as well, we are currently reviewing this error appearing in Podcasts Connect and will get back to you as soon as we can.”

Meanwhile I took on board your feedback and checked our firewall and server caching.

Also using this tool: http://web-sniffer.net/ I can see the HTTP response header content-type is text/html. This is still the case and our feed is now Active … so perhaps this was not the cause? The changes I made to our episodes yesterday are showing in iTunes so have been accepted and propagated successfully.

To test I re-submitted the same podcast feed to Podcasts Connect to check their validation and was getting the two errors: “feed already been submitted” and also the “”Podcast cover art must be at least 600 X 600 pixel JPG or PNG, in RGB color space, and hosted on a server that allows HTTP head requests”. The second was worth investigating. Checked that our artwork is within the required standards. After a while I clicked Validate again and this second error was cleared. Then checked our submitted approved feed and it was Active.

So perhaps something was cleared at the iTunes end? It does not seem to be the content-type being text/html as things appear to be working ok again.

Just thought to update you and let you know the details.

Cheers,

Heide

I’ve installed and we are using the new top level categories for our recent launch which was super important to get into the right category for our podcast so thanks so much for providing this feature!

Hi Angelo, we are close to releasing podcasting. Is it at all possible to get a version with the sub-option to select the post status on import? The iTunes category fix is much appreciated and will be very useful for our release.

Kind regards,

Maybe I should have posed that as a question – I can use category podcasting to give us a new unique address … from what I understand that should be accepted as a new feed?

Great thanks for your response and advice Shawn, thats how I thought it works but had some concerns after researching online and reading that resubmission might require a new URL and Name, we’ll have a back up plan if thats the case. I’ll let you know if it is for your own knowledge and reference.

Thanks for the update, its good to know this is possible. Do you have an estimated time frame for when this enhancement will be available in the PowerPress plugin? I am sure there are many additional features being requested of the development team, is it possible to raise the priority of this request?

Many thanks and kind regards.