Skip to content

hugo server: Taxonomy pages not updated #13648

Closed

Description

@mkoskar

Steps to reproduce

  1. Run hugo: hugo server --disableFastRender
  2. Navigate to http://localhost:1313/tags/ and note the output
  3. Add tag to a content page, e.g., from tags = ['tag1'] to tags = ['tag1', 'tag2']
  4. Navigate to http://localhost:1313/tags/ and refresh. The content will be the same as in step 2. while it is expected it would reflect tag2
  5. Ctrl-C hugo server and restart (or run hugo build alongside`)
  6. Navigate to http://localhost:1313/tags/ and refresh. Now the content is updated.

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.146.7+extended+withdeploy linux/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?

Yes

Activity

  1. jmooring commented on Apr 27, 2025

    @jmooring
    Member
    git clone --single-branch -b hugo-github-issue-13648 https://github.com/jmooring/hugo-testing hugo-github-issue-13648
    cd hugo-github-issue-13648
    hugo server
    

    While hugo server is running:

    1. Visit the tags page
    2. Add another tag to content/posts/post-1.md

    Note that the tags page does not show the new tag.

  2. self-assigned this
    on Apr 27, 2025
  3. added this to the v0.148.0 milestone on Apr 27, 2025
  4. bep commented on Apr 28, 2025

    @bep
    Member

    So, #13662 fixes the common problem described in here, re-rendering of e.g. /tags when new terms are added, but we still don't handle tag renames, which is a harder problem to tackle in a reasonable simple and performant way -- but that should be a less common/annoying problem. But I'll keep this issue open.

  5. modified the milestones: v0.148.0, v0.149.0 on Jul 10, 2025
  6. modified the milestones: v0.149.0, v0.150.0 on Sep 4, 2025
  7. 31 remaining items

  8. added 11 commits that reference this issue on Nov 2, 2025
    f1f33c0
    20cb6f8
    9da7004
    8b87f20
    ad4a471
    3a37955
    1d5783c
    76389c6
    cdb3fcd
    c6ddeb2
    264022a
  9. github-actions commented on Nov 27, 2025

    @github-actions

    This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

  10. locked as resolved and limited conversation to collaborators on Nov 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions