Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Folders(v3): Changing folder on draft documents does not reflect in folder view until published

Open
  • Is something wrong?
#18,316 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
nextjs, typescript
Domain
backend, frontend

Research direction

Start with the admin folder view and trace how a document's folder location is queried when drafts are enabled; compare that path with the existing draft-title and table-view behavior. Reproduce the move using the linked payload-testing repository, then verify that an unpublished folder change appears in the new folder and add coverage for the draft case.

Written by the indexing model from the issue text.

Description

area: ui Bug status: needs-triage v3
Describe the Bug

When moving or creating a document inside a folder within a collection that has versions: { drafts: true }, changing the folder on a draft does not update the document's location in the folder view until the document is published.

Following the fix in #17412 (which made the folder view prefer draft titles), the folder location is still queried from the published state, leaving draft documents in their old folder (or orphaned if newly created as a draft) until published.

For a better user experience, I think it is better to show the element in the new location to be more intuitive and consistent with the title or how the table view works, where all the values are fetched from the draft version.

I'm available to fix it.

Link to the code that reproduces this issue

https://github.com/XedaGmr/payload-testing

Reproduction Steps
  1. Configure a collection with both folders: true and versions: { drafts: true }.
  2. Create two folders: Folder A and Folder B.
  3. Create a document in Folder A and publish it.
  4. Edit the document and change its folder to Folder B without publishing it.
  5. Navigate back to the admin folder view.

The reproduction repository is already seeded with a test SQLite DB (payload-testing.db):

Visual Proof Image

Inside Test Folder 1 is possible to find the Test Post item.

Image

The value assigned to the item is Test Folder 2

Which area(s) are affected?

area: ui

Environment Info
Binaries:
  Node: 24.15.0
  npm: 11.12.1
  Yarn: N/A
  pnpm: 11.0.9
Relevant Packages:
  payload: 3.90.2
  next: 16.3.3
  @payloadcms/db-sqlite: 3.90.2
  @payloadcms/drizzle: 3.90.2
  @payloadcms/graphql: 3.90.2
  @payloadcms/live-preview: 3.90.2
  @payloadcms/live-preview-react: 3.90.2
  @payloadcms/next/utilities: 3.90.2
  @payloadcms/plugin-form-builder: 3.90.2
  @payloadcms/plugin-nested-docs: 3.90.2
  @payloadcms/plugin-redirects: 3.90.2
  @payloadcms/plugin-search: 3.90.2
  @payloadcms/plugin-seo: 3.90.2
  @payloadcms/richtext-lexical: 3.90.2
  @payloadcms/translations: 3.90.2
  @payloadcms/ui/shared: 3.90.2
  react: 19.2.6
  react-dom: 19.2.6
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Fri, 28 Aug 2026 11:47:30 +0000
  Available memory (MB): 15384
  Available CPU cores: 12
Dominant language
TypeScript
Stars
45.5k
Forks
4.3k
Avg merge
1d 19h
Merged PRs (30d)
295

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from payloadcms/payload

All issues in payloadcms/payload

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.