Changing a slug from internal to external breaks things

[cathysarisky]

Issue Summary

OK, weird edge case, but here goes:

1 - Create and tag posts with an #internal tag. Then realize you didn't want it to be internal, and change its name and slug to match the external pattern.
This results in normal behavior at /tag/slug, however, routes are broken.
2 - add the following to routes.yaml:

collections:
  /vnn-archive/:
    permalink: /{slug}/
    template: tag
    filter: tags:[vnn-archive]
    data: 'tag.vnn-archive'

  /:
    permalink: /{slug}/
    template: home
    filter: tags:-[vnn-archive]

Now tags/vnn-archive redirects to /vnn-archive, but vnn-archive has no content (just the title). The posts aren't getting routed there.

Loading a routes.yaml file without the data attribute causes these posts to again appear at /tags/vnn-archive.

Steps to Reproduce

see above

Ghost Version

Ghost Pro

Node.js Version

Ghost Pro

How did you install Ghost?

Ghost Pro

Database type

MySQL 8

Browser & OS version

No response

Relevant log / error output

Code of Conduct

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

[cmraible]

Hi @cathysarisky, thanks for reporting! I've been able to reproduce this and agree that there is a bug here.

It looks to be a caching issue, so I do have a workaround: restarting the site should bring the posts back to the /vnn-archive/ index.

Since this is a pretty rare edge case, I've added the community label to this one — happy to review any PRs from the community with a fix here.

[cathysarisky]

"It looks to be a caching issue, so I do have a workaround: restarting the site should bring the posts back to the /vnn-archive/ index."

This was a Ghost Pro-hosted site. In that case, would we email support to request a restart?

(No action needed for this specific site -- I've long since deleted the tag and started over.)