Wandering Eye Entertainment

Angelo ,

yes it is, I even got an update through my podcasts app on my iphone showing the new episode come through. Once I put that snippet in the right .htaccess file, things finally took effect.

I’ll be recording a new episode soon and uploading it to see if it continues to take effect, but I don’t forsee any issues at this point and I was able to avoid using the itunes tag option which I was hoping I would only have to do as a last resort.

Thanks for continuing to help monitor the situation and troubleshoot this issue. Going forward with this process in the future will be a lot easier.

I wanted to update you on this. So it appears that the .htaccess file that needs the 301 redirect is in fact the one used in the root folder of public_html. That is the one that is being used by wordpress. I tried placing the code you gave me into the correct place under RewriteBase / in that one just to see. It updated the subscriber date instantly as it is supposed to.

It hasn’t updated the index in the store yet and I don’t think it will for a few days. So I think it is finally solved. The block is below. The only question I have now is, the old episodes I had. In order to have those available, I would need to then, upload them into the new feed?

Located in the root public_html

## EXPIRES CACHING ##
# compress text, html, javascript, css, xml:
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
# Or, compress certain file types by extension:
<files *.html>
SetOutputFilter DEFLATE
</files>
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access plus 1 year"
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType image/gif "access plus 1 year"
ExpiresByType image/png "access plus 1 year"
ExpiresByType text/css "access plus 1 month"
ExpiresByType application/pdf "access plus 1 month"
ExpiresByType text/x-javascript "access plus 1 month"
ExpiresByType application/x-shockwave-flash "access plus 1 month"
ExpiresByType image/x-icon "access plus 1 year"
# ExpiresDefault "access plus 2 days"

</IfModule>
## EXPIRES CACHING ##
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^feed\/podcast\/? "https://lonniebruhn.com/ftn_podcast/feed/podcast/" [R=301,L]
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Yes, I saw that too. Thanks for also staying on top of this, I really appreciate it. I am going to paste both .htaccess blocks. The first one is that is in root.. and the second one is the one that is in the root folder where WordPress resides.

Public_html .htaccess

## EXPIRES CACHING ##
# compress text, html, javascript, css, xml:
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/xml
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
# Or, compress certain file types by extension:
<files *.html>
SetOutputFilter DEFLATE
</files>
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access plus 1 year"
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType image/gif "access plus 1 year"
ExpiresByType image/png "access plus 1 year"
ExpiresByType text/css "access plus 1 month"
ExpiresByType application/pdf "access plus 1 month"
ExpiresByType text/x-javascript "access plus 1 month"
ExpiresByType application/x-shockwave-flash "access plus 1 month"
ExpiresByType image/x-icon "access plus 1 year"
# ExpiresDefault "access plus 2 days"

</IfModule>
## EXPIRES CACHING ##
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

Public_html/blog/ .htaccess

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteBase /
RewriteRule ^feed\/podcast\/? "https://lonniebruhn.com/ftn_podcast/feed/podcast/" [R=301,L]
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

Thank you, I will use what you wrote. The snippet I had in there was what I copied that was an output from the cpanel 301 redirect. This is also why you see the separate host names because I had checked the wildcard.

I put your snippet in place of it, and I’ll wait another 24 hrs. Also, when I do get this resolved, I plan on leaving the redirect in there indefinitely or at least a year or until I have a reason to do otherwise.

Angelo,

The feed still doesn’t seem to be redirecting to the new feed and I really don’t understand why.

Here is the old feed and as you can see, nothing has changed.
https://lonniebruhn.com/feed/podcast/

This is what I have in my.htaccsess inside /blog where the core wp files are stored.

RewriteCond %{HTTP_HOST} ^lonniebruhn\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.lonniebruhn\.com$
RewriteRule ^feed\/podcast\/?(.*)$ "http\:\/\/lonniebruhn\.com\/ftn_podcast\/feed\/podcast\/$1" [R=301,L]

The only other thing I can try now is putting in the itunes tag but that still doesn’t explain why the main feed isn’t being redirected either.

Any thoughts?

Angelo,

Nice to meet you, thank you for jumping into the conversation. You must have posted literally around the same I did. If you read that entry, you’ll see I moved it over to the one inside /blog.

I always wondered if the redirect rule inside cpanel worked correctly in regards to WordPress, and I think if I was redirecting just the domain name, https://www.lonniebruhn.com to a new address, it would. Since this a wordpress feed dynamically built within WP, then I’m sure this was the problem.

The feed hasn’t updated yet, but I’ll let you know. I’m actually refreshing the subscription feed rather than the iTunes store feed because as I understand, it, that feed is updated almost immediately because it is specific to only my subscribers where as Itunes Store may take up to two days to update because of the large podcast index.

If I don’t see any changes after a day or so, My next step will be to use the iTunes tag because that is the one I am trying to fix.

Thanks again and I have loved your plug-in for many years. You have made an outstanding plugin I recommend to all of the comedians wanting to start a podcast..

LB

Yes, I do have access to all my flies in /public_html and even anything behind it in root. I do have more than one .htaccess though. I have one in /public_html and I have one in /blog/ where the core WP files are located.

My feed still hasn’t redirected to the new feed so I took a look at both. The one in my root WP folder, ie, /blog has the basic wp .htaccess entry and that is it.

In my public_html folder, the .htaccess file actually is the one that WordPress seems to be writing to because it has several caching entries stored in inside the WP block.

Below the # End WordPress however, it has the following rewrite entry:

RewriteCond %{HTTP_HOST} ^lonniebruhn\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.lonniebruhn\.com$
RewriteRule ^feed\/podcast\/?(.*)$ "http\:\/\/lonniebruhn\.com\/ftn_podcast\/feed\/podcast\/$1" [R=301,L]

I have both .htaccess files because at point I configured the wordpress site url to point away outside the wordpress dir so that the address wouldn’t show as .com/blog.

I’m just wondering now, if the entry should go into the .htaccess isiide the WordPress /blog dir?

As the next troubleshooting step, II pasted the same 301 entry above inside that .htaccess to see if this resolves my feed issue. I’ll report back my findings.

LB

I am using the 301 redirect from the cpanel of my web hosting company

When I look at the old feed, It has been cleared. There are no posts but the feed is still live and iTunes is not updating so something has clearly changed but I’m not sure what went wrong.

Sometimes when you get stumped your brain stops functioning rationally lol. I think after taking a look, I did screw up the redirect. The domain is already set so I think because I placed the feed in the way I did, it is reading the old feed as lonniebruhn.com/lonniebruhn/feed/podcast. And I think this might be the issue. I went ahead redid the 301 but because the / is at the beginning, only put in /feed/podcast and then redirected it to the new feed to: https://lonniebruhn.com/ftn_podcast/feed/podcast/

I think this will fix it because if not, I’m stumped.

Don’t know why it didn’t display the link but here it is again:
https://imgur.com/wpVANDU

The only thing I can think of is to add is a wildcard option.

Shawn, thanks for checking the new feed, I was about to check myself and do it cognito so I determine if it was a caching issue. You checking clarifies that.

Since there isn’t a way to add an attachment, I took a screenshot of my 301. I can’t see anything wrong but I thought I should have you take a look. I am not sure why it isn’t taking effect. Should I go ahead and use the iTunes Tag at this point? After that, I’m not sure what else I can do.

Here is the link:

Got it, so if I want to include the podcasts, I have to upload them all through the new custom post type interface I built.

So then the part that doesn’t seem to be working, right is that I am subscribed to the podcast, there has been one update, which is an old episode Ep70. The entire listing of all the old episodes is still showing up o the Itunes store and in my subscription. The new podcast episode (which is Ep71) has not shown up yet which leads me to believe, the 301 has not taken effect yet.

Secondly, what happens to the old feed, it just resides on it’s own and never gets updated again? And how do people know which is the correct podcast listing in Itune? Will there be two?

Thanks for the clarification. I don’t know why I didn’t know that since I am doing a lot of my own custom development but, yes, this makes complete sense because everything is served dynamically across many templates.

I still need clarification on the last post.

Regards
LB

Hello again,

Id appreciate some more input When I go to put in the iTunes tag to redirect it to the new custom post feed, it warns me that doing so will be permanent. I want to make sure I am not destroying my old feed.

Obviously the 301 redirect either hasn’t taken place yet or isn’t working correctly, and so I may have to do this to get iTunes to accept the new feed change. I want to make sure if I am doing this, that will not just start indexing the new episodes but that will pull over the other 70. Is that what is suppose to happen?

My new feed url again is: https://lonniebruhn.com/ftn_podcast/feed/podcast/ and it does show the new epiode. This is the right feed to place in that entry field, right. Not the old original feed, right?
LB

Thank you very much, I’ll do that now and wait a few days to see if it updates iTunes. As of earlier this morning, there has still been no update to my iTunes podcast feed. Not the regular listing nor my subscribers listing either.

The part that is bothering me is that the iTunes subscribers listing is supposed to be updated immediately because it checks the feed constantly where the regular listing is subject to the iTunes overloaded podcast index being spidered randomly.

I did 301 redirect yesterday and I’ll perform the iTunes tag now and I’ll wait 48 hrs to see if we have any success, so please hold off on changing this to resolved until I can verify the new working feed.

While I wait, can you tell me if there is a direct way to edit the rss feed outside of Powerpress interface. Sometimes there is a need to be able to have access to the feed outside of the plugin interface.

Thank you for the continued support.
LB