sitemap-tags.xml not present in XML Sitemap

[beardoggo]

Issue Summary

I'm not seeing sitemap-tags.xml generated in the root sitemap unlike other people's blogs.

I want it generated as can be seen in Ghost.org's sitemap:

Steps to Reproduce

1. Clean install Ghost

2. Install Asona Theme

3. Create random pages, posts, and tags

4. No sitemap-tags.xml generated

Ghost Version

5.95.0

Node.js Version

N/A

How did you install Ghost?

pikapods.com

Database type

MySQL 5.7

Browser & OS version

No response

Relevant log / error output

No response

Code of Conduct

• [X] I agree to be friendly and polite to people in this repository

[cathysarisky]

Quick check - do you have tags that are public (do not start with #), and are those tags applied to at least one published post?

[beardoggo]

Yes they are not internal tags (do not start with #) and I have hundreds of posts published for each tag.

[cathysarisky]

There may be something 'quirky' about your setup. I have a pikapods install, and once I added a published post with a public tag, the sitemap-tags.xml file appeared. Have you changed your routes.yaml from the default? If you don't have a tags collection, that might be to blame?

[beardoggo]

Oh I see, my routes.yaml looks like this. I'll try adding "tags" to "collections" and post the result again. Thanks!

routes:

collections:
  /:
    permalink: /{slug}/
    template: index

taxonomies:
  tag: /tag/{slug}/
  author: /author/{slug}/

[cathysarisky]

Sorry - my comment was unclear. I meant taxonomies, and so what you have looks fine!

[cathysarisky]

Looking to see if I can replicate this real quick...

Nope. Started a new 'pod, added two posts with public tags, no problems seeing the sitemap.

[allouis]

@beardoggo I only see this issue when all of my posts have zero tags attached to them. If that's the case then the tags don't actually have any content and so aren't included in the sitemap.

I'm going to close this issue for now - but if you are seeing that this is broken when the tags are being used, or if you think this behaviour is incorrect - please feel free to open a new issue detailing either reproduction steps or correct behaviour!