Did you update the SP sitemap plugin to the latest version – it was release just a few days back…?

Yes, we are running Version 2.1.3 of the SP sitemap plugin

On Tue, Apr 1, 2014 at 9:50 AM, Simple:Press Support wrote:

> >

So you should update it to 2.2 which should be showing up in your WordPress Update panel.

Thanks for the reply.

We still show the 2.1.3 with no update and also on the main plugins page it still shows 2.1.3 also.

Ah apologies. I see now that 2.2 is for the next update – something to do with changes to the way Google handles sitemaps.

The date and WP SEO issue was resolved in the previous update – probably the one you have – at least for any user at the time that had reported it. Is it the latest WP SEO as well? I will have to confer with colleagues either way.

Thanks again for the reply. Yes, both plugins are the latest. 

I should reiterate the only ones we are having issues with are those that were redirects from vBulletin, which is only 45 out of 15,000+, everything else is fine.

Example: When a user made a posted topic (thread) in the wrong group (forum) we would move it to the right group (forum) and vBulletin would have an option to leave the topic in place with a redirect and that’s what we did, those original URL redirects got imported and those are the ones that we have the issues with. And when we go to those specific URLs that’s where we get the error: Access denied – you do not have permission to view this page – and those 45 are the ones that show the 1969 date in the sitemap.

Just wanted to give a little more info, because I did read those who were having the date problems that seems like ours is a different.   

a little confused… why would the old redirected urls be in the sitemap? and who put them there?

Technically I guess they are still links, they were put there by the sitemap generator, not by us or I would remove them. I turned the 301 redirect off on the following to show an example:

This was an original link before we move it (in vBulletin and left a redirect in place) http://demolitionforum.com/forums/industry-news/demolitions-scholarships-and-grants/

When we moved it (in vBulletin) it was moved to http://demolitionforum.com/forums/office-and-business/demolitions-scholarships-and-grants-1/

As you can see it was in the Industry News and we moved it to the Office Business forum. We left the redirect so if people looked in the industry news forum they would still see the topic. It’s just something that we did in vBulletin. 

On the first link, as you can see, even logged in as the admin we get the same message Access denied – you do not have permission to view this page.

If there is way to delete them, I would love to know and that would fix our issue. But since we can’t access it, not sure what to do. 

Hope that helps.

Edit: and these are old post, so I don’t even mind losing them if need be

Ah – sorry I got the wrong end of the stick yesterday. However, perhaps I am just dumb or it is too early in the morning but speaking personally I don’t even understand the question

These redirect ‘entries’ you refer to. Where are they? How do they work? If they exist somewhere then they should be removeable – bit where is it they exist?

Hey Guys sorry for not updating, with a new client and spring break we’re just getting back into things.

The redirects were there from the original vBulletin import that was done, they were in there using vBulletin, not sure if was internal 301 redirects or how it worked on the backend of vBulletin. 

We have now fixed the issues completely.

We temporarily did 301 redirects on all the post that were formally redirects within vBulletin to the newer posts until we could figure out a method to remove them from the sitemap and also to stop giving the group/post permission error.

In the end, we removed all the 301 redirects, installed the SP Database Cleaner plugin and used the sitemap as guide on which posts had the 1969 dates on them and we click on them one by one to see where the original origin of the post category and used the database clean up to delete them.

It was a long and tedious process but it worked, but now our sitemap is clean and there are no errors.

good to hear! sounds like hard work!