Skip to content

Public contentnode tree returns no children for an uppercase node id #6417

Open

Description

@rtibbles

🙂 Looking for an issue? Welcome! This issue is open for contribution. If this is the first time you’re requesting an issue, please:

  • Read Contributing guidelines carefully. Pay extra attention to Using generative AI. Pull requests and comments that don’t follow the guidelines won’t be answered.
  • Confirm that you’ve read the guidelines in your comment.

Overview

The public contentnode tree endpoint accepts its node id in any form Python's UUID() parses, including uppercase hex, but then matches children by comparing each child's parent with the id exactly as sent. For an uppercase id the comparison never matches, so the response has the parent node with no children.

Complexity: Low
Target branch: hotfixes

Context

  • ContentNodeTreeViewset.retrieve validates pk with UUID(pk) and later tests desc["parent"] == pk.
  • Reproduced: GET /api/public/v2/contentnode_tree/<id in uppercase>/ returns 200 with no children key, and the same id in lowercase returns the children.

The Change

  • The endpoint should normalise the id it accepts to lowercase hex before using it.

Acceptance Criteria

General

  • GET /api/public/v2/contentnode_tree/<id>/ with the id in uppercase returns the same response as with the id in lowercase.

Testing

  • The criterion has a regression test.

AI usage

I scoped the audit. Claude Code found and reproduced this failure and drafted this issue.

Activity

  1. added theissue type on Nov 15, 2026
  2. added
    good first issueSelf-contained, straightforward, low-complexity
    help wantedOpen source contributors welcome
    on Nov 15, 2026
  3. learning-equality-bot commented on Nov 15, 2026

    @learning-equality-bot
    Contributor

    Hi! 👋

    This issue is available for contribution and supports self-assignment. Here's how to get started:

    • Comment /assign to assign yourself to this issue
    • You can have up to 2 issues assigned at a time across all community repos
    • Dropping an issue has a 7-day cooldown before the slot opens up
    • Link your pull request to this issue when you submit it

    📖 Read the Contributing guidelines before starting.

    Are you preparing for Google Summer of Code? See our GSoC guidelines.

  4. ManyaJain111 commented on Nov 16, 2026

    @ManyaJain111

    /assign

  5. learning-equality-bot commented on Nov 16, 2026

    @learning-equality-bot
    Contributor

    Hi! 👋

    You've been assigned to this issue. Here's what to do next:

    • Read the issue description carefully and make sure you understand the requirements
    • Link your pull request to this issue when you submit it
    • If you can no longer work on this, unassign yourself so others can pick it up

    Good luck! 😊

    Are you preparing for Google Summer of Code? See our GSoC guidelines.

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

Metadata

Metadata

Assignees

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions