[Plugin: podPress] Conflict with custom-headers-and-footer

This is no bug of podPress.

If you add code or simply text via the “Header:”-box of the custom-headers-and-footers plugin then this plugin adds this code or content to all pages including all Feeds of the blog. The same happens if you add something in the “Footer:”-box.
That is a problem for the Feeds because the code becomes inserted between the <item> (or the <entry> tag) of the Feeds.That is not allowed and makes the Feed invalid.

The fix for that is simple. Add && !is_feed() at two places in the custom-headers-and-footers.php file:

line 73 and 81
old:

if ( ( $wp_query === $wp_the_query ) && !is_admin() ) {

new:

if ( ( $wp_query === $wp_the_query ) && !is_admin() && !is_feed() ) {

This modification will prevent the custom-headers-and-footers plugin from adding code at the wrong place in the feeds.

Regards,
Tim

BTW: If you add the tags of more than one plugin to a forum thread, that thread will appear in the Forum Feeds of all these plugins.

Thank you so much – that did the trick!

Because of the invalidation, iTunes removed my podcast from the store, and now when I ping, it seems to come up with https://adventuresintimespaceandmusic.phillipwserna.com/feed/ instead of https://adventuresintimespaceandmusic.phillipwserna.com/feed/podcast I had wiped my podpress database so I could fully reinstall. Is there something I am missing in my setup?

Apple’s support is not very helpful – am I missing something important with podpress?

Both Feeds are valid and it is not very important which Feed you have submitted to the iTunes Store. The iTunes Store and the iTunes client software will show only the posts with attached media files.

Which Feed have you submitted to the iTunes Store?

Because of the invalidation, iTunes removed my podcast from the store.

How do you know that? Did you get an email or an other message which contained this explanation?
Are you sure that it was not beacause of the title of your Feed (Doctor Who: Adventures in Time, Space and Music ? Podcast Feed). “Doctor Who” is maybe a term which is protected by some kind of trademark or seen as misleading because your podcast is as your description says it not The Doctor Who podcast.

and now when I ping, it seems to come up with

I don’t understand. What is comming up? The iTunes client software with the iTunes Store page of your podcast? How is that possible if you are sure that your podcast was kicked out of the store?

A different thing is the iTunes button of the podPress Feed Buttons widget. If I click on this button the iTunes client software starts and subscribes immediately to your podcast. The Feed behind this button is https://adventuresintimespaceandmusic.phillipwserna.com/feed/podcast . You are using the iptc:// option of the widget which makes iTunes start. But this works without submitting the Feed to the store.

You probably know how it works but here are the instructions on how-to submit a podcast to the iTunes Store https://www.apple.com/itunes/podcasts/specs.html#submitting

Regards,
Tim

A lot of Doctor Who Podcasts have the ‘Doctor Who’ at the begninng, so I doubt it was that. I didn’t receive any email from Apple that was removed, but it isn’t in the US store, I resubmitted and tried again. I keep getting an error of “Page not available in the US store” error when I try to go to the link to the podcast. Could I be a ping spammer? I tried emailing support, but they are useless – what’s the best support method for iTunes regarding podcasts?

I have searched with google for the itunes page of your podcast and google has found at least this page https://itunes.apple.com/lv/podcast/doctor-who-adventures-in-time/id392534466
Episode 10 is the last podcast in the list there. But it is maybe not a page of the US iTunes Store.
But https://itunes.apple.com/us/podcast/doctor-who-adventures-in-time/id392534466 works now too. I have also checked in my iTunes Client and I would says that you Podcast is available again.

Regards,
Tim

Tim – thank you…not THANK YOU for all your help!I got some definitive answers earlier today when I was finally able to get an email to ‘[email protected]’ – the best help to know what the final deal was after your great code-fix for the plugin. Thank you so much!

All the best!

Phillip

Sorry for late response. I have fixed this bug in version 1.2.