Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Splitting sitemaps resulting in empty part. #48

Open
scottblackburn opened this issue May 22, 2017 · 2 comments
Open

Splitting sitemaps resulting in empty part. #48

scottblackburn opened this issue May 22, 2017 · 2 comments
Assignees
Labels

Comments

@scottblackburn
Copy link

Hi,

I've enabled the 'split post based sitemaps' feature on a large site (6000+ posts). I'm finding that the last sitemap generated is always empty, in this case when using a 1000 split limit post_part6.xml is empty. This results in google webmaster tools not being able to validate the sitemapindex. I've tried changing the split limits but the same issue occurs. No errors appear in the sitemap logs but the following appears when trying to view the last sitemap:

BWP Google XML Sitemaps Error: post_part3.xml does not have any item. There are no public Post. Enable/disable sitemaps via BWP Sitemaps >> XML Sitemaps.

Thanks

@scottblackburn
Copy link
Author

Update
The problem appears to occur when you combine excluding categories with the split sitemap functionality. The original query appears to ignore the excluded categories and get the total number of posts instead. Total posts is divided by the split amount and individual xml files are created for each 'part'. The next query does take the excludes into account so as they're added into the files you're left with empty parts. Essentially too many empty files are created because the original query isn't taking into account and exclude terms.

Could the original query take the excludes into account?

Many Thanks.

@kminh kminh added the Bug label Nov 10, 2017
@kminh kminh self-assigned this Nov 10, 2017
@kminh
Copy link
Collaborator

kminh commented Nov 10, 2017

@scottblackburn thank you for reporting the issue. At the moment I do not have a good solution yet. Will keep you posted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants