davethenerd

Confirming that, at least with some initial (but thorough) tests, both of these bugs appear to be solved with 10.0.8. Y’all rock! Thanks!

I thought maybe this was related to the trailer logic errors that still exist (and are plaguing me), so I went to pull your feed and look (I’m just a user like you, not a wordpress support engineer).

I am presuming your feed to be https://www.nba-live.com/feed/podcast/ and, when I pull that, I get a 500 error from your website, which is different from what I’m seeing with my trailer logic errors, but is definitely the reason that no one can update your show.

I’ll include the results of trying to pull your feed with curl below in case it’s helpful to you or the Blubrry folks.

curl https://www.nba-live.com/feed/podcast/                                      
<error>
    <code>internal_server_error</code>
    <title><![CDATA[WordPress &amp;rsaquo; Error]]></title>
    <message><![CDATA[&lt;p&gt;There has been a critical error on this website.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;https://www.ads-software.com/documentation/article/faq-troubleshooting/&quot;&gt;Learn more about troubleshooting WordPress.&lt;/a&gt;&lt;/p&>></message>
    <data>
        <status>500</status>
    </data>
</error>

I have (now) confirmed that this is happening on multiple WordPress/PowerPress installs.

Amazing. Thank you! Looking forward to hearing what they find.

Ok, I *think* I found it. When publishing next week’s episode, I found the “Type” option at the bottom of “Apple Podcasts (optional)” > “See More Settings”. It was set to “Full (default)”. I went to a previous episode and changed it to “Full episode” (which should be the same, right?) and… voilà, itunes:episodeType now shows up in the feed for that one episode. (I’ll still need to wait to see if this solves Apple’s matching problem, but at least I can test it and tell them I’ve got it in the feed now :).

Is there a reason PowerPress isn’t putting itunes:episodeType in the feed when “Full (default)” is selected, or is that an oversight in the code?

Thanks, Mike! I should’ve been more clear.

You’re right that Apple manages the subscription portion of things, and Powerpress manages the public feed.

Apple slurps in that public feed and then integrates their Subscription episodes plus the feed into what’s shown to users of Apple Podcasts. I know you know all this, of course, I’m just walking us down the path.

The issue is in that integration. We publish an “early access” episode to Apple Podcasts, which means we’re going in and publishing in Apple Podcasts *before* it appears in the public feed that PowerPress creates. Apple podcasts *tries* to match episodes in the two places so that duplicates don’t appear, and *that* is the crux of my issue.

It needs to match on two things: itunes:episode and iTunes:typeitunes:episodetype. Powerpress happily puts iTunes:episode out there, but it doesn’t have a way of populating iTunes:typeitunes:episodetype.

And without that second bit of criteria upon which to match, Apple Subscriptions thinks these are two separate episodes and lists them twice in people’s feeds.

So what I need is a way to add iTunes:typeitunes:episodetype to my feed, and I was hoping there might be a way to do that within Powerpress. ??

https://podcasters.apple.com/support/899-set-up-your-show-for-a-subscription has the details and… now I’m realizing that my communications from Apple are also confused. The email I got from Apple Podcast Support today said “itunes:type” was needed, but that support doc says “itunes:episodetype” is the feed it’s looking for. I’m assuming the support doc is correct and itunes:episodetype is what’s necessary.

Have you folks encountered this before? Any thoughts?

Perhaps some insight here. I tried to have it create a new bucket, and I get this error at the top of the screen:

Error executing "CreateBucket" on "https://mgg-wp.[myserverurl.com]:9001/"; AWS HTTP error: cURL error 6: Could not resolve host: mgg-wp.[myserverurl.com]; Unknown error (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

Seems it’s taking my endpoint of https://[myserverurl.com]:9001/ and trying to do a DNS lookup for [new-bucket-name].[myserverurl.com] which obviously doesn’t exist. This leads me to think I need to use “Pathstyle-only bucket” option, but that also doesn’t seem to stay checked.

Maybe this is the issue?