Create item in empty collection with folders enabled

[JesperWe]

Describe the Bug

Going into the collections with folders: true and clicking "Create New" causes a crash:

 GET /admin/collections/members/create 200 in 45ms
 ⨯ TypeError: Cannot destructure property 'config' of '(0 , _providers_Config_index_js__WEBPACK_IMPORTED_MODULE_9__.useConfig)(...)' as it is undefined.
    at MoveDocToFolder (../../../../src/elements/FolderView/MoveDocToFolder/index.tsx:46:2)
  44 |   const [fromFolderName, setFromFolderName] = React.useState(() => `${t('general:loading')}...`)
  45 |
> 46 |   const { config } = useConfig()
     |  ^
  47 |   const modalID = useId()
  48 |
  49 |   React.useEffect(() => { {
  digest: '4115836182'
}

Link to the code that reproduces this issue

https:... Cannot build due to other crash, so only pnpm dev at the moment

Reproduction Steps

I am testing the new folders in 3.39.0.

I have enabled folders on a couple of collections in an existing project (using postgres).
Starting using pnpm dev with an empty database, so all tables are created from scratch.

Which area(s) are affected? (Select all that apply)

area: core

Environment Info

Binaries:
  Node: 20.11.0
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: 10.11.0
Relevant Packages:
  payload: 3.39.0
  next: 15.3.2
  @payloadcms/db-postgres: 3.39.0
  @payloadcms/email-nodemailer: 3.39.0
  @payloadcms/graphql: 3.39.0
  @payloadcms/next/utilities: 3.39.0
  @payloadcms/payload-cloud: 3.39.0
  @payloadcms/plugin-cloud-storage: 3.39.0
  @payloadcms/richtext-lexical: 3.39.0
  @payloadcms/storage-s3: 3.39.0
  @payloadcms/translations: 3.39.0
  @payloadcms/ui/shared: 3.39.0
  react: 19.1.0
  react-dom: 19.1.0

[PatrikKozak]

Hey @JesperWe! We just merged a fix for this here: #12501!

Really appreciate you testing folders out right away!

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload

[github-actions]

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.