How to restore my rss feed?

More than likely, you established this redirect via a plugin or added it to your .htaccess file.

I recommend first checking to see if you have any plugins, like Feedburner or Redirection active, then check their settings.

If not, edit the .htaccess file in your site’s web root. To do so, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), and edit the file with a plain text editor.

If you do not see a .htaccess file in your site’s web root, make sure your SFTP or FTP client is set to display invisible or hidden files.

Hi James,
I’ve checked your suggestions. There is a lot of code in my htaccess file. On this particular site Autoptimize, Comet Cache, Really Simple SSL Pro and Shield Security are active. They leave some code in htaccess by design.

The problem started when I removed the Feedburner feed from the Google site, and those plugins were active already.

Perhaps I could deactivate them, remove their htaccess code and replace the standard WordPress code? Then rebuild the code by activating the plugins again. What your view on that?

I’ve got the same problem on another site which is using Safe Redirect Manager, WP Rocket, Really Simple SSL Pro and Shield Pro. All Genesis/StudioPress based theming.

Thanks, Bart

What redirects do you have under Safe Redirect Manager?

I’ve got 7 redirects (301), 4 from renamed or deleted pages, from renamed blogs. But both sites have this problem, one has no redirects at all.

Ok, please share the content of the .htaccess file from the site that does not have the plugin.

@bvm When you deleted the Feedburner feed, did you set a permanent redirection to your original feed? See https://follow.it/docs/publishers/getting-followers/how-can-i-switch-from-feedburner-to-follow-it

@d4d5bh6 I’m afraid it did not, Nick.

Ok, then as far as I know, you cannot do much about your Feedburner feed showing an error. In terms of https://bartvanmaanen.nl/feed redirecting to https://feeds.feedburner.com/BartvanMaanen, James is right, there must be still some redirect active on your site. Who set up the redirect initially? He/she may know how it was done.

Okay, I’ve found two htaccess files on the site without the redirection plugin. One (1) is inside the WordPress installation folder, one outside (2).

1:

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

<IfModule deflate_module>
	<IfModule filter_module>
		AddOutputFilterByType DEFLATE text/plain text/html
		AddOutputFilterByType DEFLATE text/xml application/xml application/xhtml+xml application/xml-dtd
		AddOutputFilterByType DEFLATE application/rdf+xml application/rss+xml application/atom+xml image/svg+xml
		AddOutputFilterByType DEFLATE text/css text/javascript application/javascript application/x-javascript
		AddOutputFilterByType DEFLATE font/otf font/opentype application/font-otf application/x-font-otf
		AddOutputFilterByType DEFLATE font/ttf font/truetype application/font-ttf application/x-font-ttf
	</IfModule>
</IfModule>

# END WordPress

2:

# BEGIN Comet Cache WmVuQ2FjaGU (the WmVuQ2FjaGU marker is required for Comet Cache; do not remove)

# Enable GZIP compression.
<IfModule deflate_module>
  <IfModule filter_module>
    AddOutputFilterByType DEFLATE text/plain text/html
    AddOutputFilterByType DEFLATE text/xml application/xml application/xhtml+xml application/xml-dtd
    AddOutputFilterByType DEFLATE application/rdf+xml application/rss+xml application/atom+xml image/svg+xml
    AddOutputFilterByType DEFLATE text/css text/javascript application/javascript application/x-javascript
    AddOutputFilterByType DEFLATE font/opentype application/font-otf application/x-font-otf
    AddOutputFilterByType DEFLATE font/truetype application/font-ttf application/x-font-ttf
  </IfModule>
</IfModule>

# END Comet Cache WmVuQ2FjaGU

# BEGIN Really_Simple_SSL_SECURITY_HEADERS
<IfModule mod_headers.c>
Header always set Strict-Transport-Security "max-age=31536000"  env=HTTPS
Header always set Content-Security-Policy "upgrade-insecure-requests" 
Header always set X-XSS-Protection "1; mode=block" 
Header always set X-Content-Type-Options "nosniff" 
Header always set Referrer-Policy "no-referrer-when-downgrade" 
Header always set Expect-CT "max-age=7776000, enforce" 
</IfModule>
# END Really_Simple_SSL_SECURITY_HEADERS

# BEGIN rlrssslReallySimpleSSL rsssl_version[5.0.6]
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
</IfModule>
# END rlrssslReallySimpleSSL
# BEGIN WordPress
# De richtlijnen (regels) tussen "BEGIN WordPress" en "END WordPress" worden
# dynamisch gegenereerd en zouden alleen aangepast mogen worden via WordPress filters.
# Alle wijzigingen aan de richtlijnen tussen deze markeringen worden overschreven.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
# Header unset ETag
FileETag None
## EXPIRES CACHING ##
<IfModule mod_expires.c>
ExpiresActive On
ExpiresByType image/jpg "access 1 year"
ExpiresByType image/jpeg "access 1 year"
ExpiresByType image/gif "access 1 year"
ExpiresByType image/png "access 1 year"
ExpiresByType text/css "access 1 month"
ExpiresByType text/html "access 1 month"
ExpiresByType application/pdf "access 1 month"
ExpiresByType text/x-javascript "access 1 month"
ExpiresByType application/x-shockwave-flash "access 1 month"
ExpiresByType image/x-icon "access 1 year"
ExpiresDefault "access 1 month"
</IfModule>

Yeah, none of those would be doing it, ok.

Try re-saving your permalink structure at Settings > Permalinks in your Dashboard. If WordPress cannot automatically edit the .htaccess file, it will provide manual instructions after saving.

Already tried this a few times, to no avail. F*cking Feedburner.

Ok, so here’s the thing. Feedburner cannot force your built-in feed https://bartvanmaanen.nl/feed/ to them https://feeds.feedburner.com/BartvanMaanen

And there’s nothing built-into WordPress for that either.

So there absolutely must be a plugin or theme function, a .htaccess rule somewhere, or a redirect set somewhere doing this.

Try retracing the steps you remember for setting up Feedburner.

If you don’t recall, please attempt to disable all plugins, and switch to the default Twenty Twenty-One theme. If the problem goes away, enable them one by one to identify the source of the problem.

If it’s not that, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your SFTP or FTP client to view invisible files. I know we went over this earlier, but please try this method anyway.

If it’s not that, start looking through your hosting account’s control panel for any redirect options, it may have been set in there.

I’ve let this problem simmer.
Is it possible that the fact that the WordPress installation is done (in 2008) in a subfolder is the culprit?

When I add the subfolder to the URI I do get the xml file for the comments feed.

• This reply was modified 3 years, 5 months ago by Bart van Maanen.
• This reply was modified 3 years, 5 months ago by Bart van Maanen.

No, that’s not possible.

Please try the steps in my reply above from 2 months ago.