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

Sitemap Job runs successfully but has zero entries #99

Open
PoojaJangam3714 opened this issue Dec 4, 2023 · 4 comments
Open

Sitemap Job runs successfully but has zero entries #99

PoojaJangam3714 opened this issue Dec 4, 2023 · 4 comments

Comments

@PoojaJangam3714
Copy link

We are using the Geta.SEO.Sitemaps 3.1.1 in Episerver CMS 12.19. The following is the configuration -
image

When the scheduled job is run there are no errors shown, even when we are using debug = true, and the job runs successfully -
image

But as seen in the image above and confirmed from the created sitemap.xml there are zero entries on the xml file.
image
image

  • Job runs successfully.
  • Debugging the solution locally shows no errors.
  • The same discrepancy / behaviour was observed in other environments but after rerunning the job the xml was correctly created.
  • There have been no changes to the code and version of Geta.SEO.Sitemaps is still same 3.1.1.

Please help on this as we are unable to figure out why the xml is empty at times and populated at others when there are no changes in configuration and code.

@mikemalloy-commscope
Copy link

@PoojaJangam3714 I don't know if this helps but on my lower environments I removed the 'Everyone' group to limit access. I noticed when I did that, the job would return 0 results. So, it might be a connectivity issue.

@PoojaJangam3714
Copy link
Author

@mikemalloy-commscope The user running the scheduled job has the Administrators access on the CMS. The same role is also the level to which the Sitemaps configuration is set to in code.

@Soleimsen
Copy link

I had a similar issue with sitemap generation, but I was able to fix it by giving the "Read" scope to the "Everyone" role. As per my understanding, a page needs to have Read on everyone to be part of the sitemap.

@valdisiljuconoks
Copy link
Member

Think by default sitemap should include pages with public access. Might be good idea to include skipped pages in log, but could grow log entry significantly. Maybe just include number of pages skipped..?

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

No branches or pull requests

5 participants