Error using folders after upgrading from v3.47.0 to v3.48.0

[kubyshkin-vladyslav]

After upgrading Payload CMS from v3.47.0 to v3.48.0, I encountered a PostgreSQL enum error when accessing the http://localhost:3000/admin/collections/media/payload-folders.

Error

[Error: Failed query: select distinct "payload_folders"."id", "payload_folders"."name", "payload_folders"."name", "payload_folders"."created_at", "payload_folders"."created_at" from "payload_folders" left join "payload_folders_folder_type" on "payload_folders"."id" = "payload_folders_folder_type"."parent_id" where (("payload_folders"."folder_id" is null or "payload_folders"."folder_id" is null) and ("payload_folders_folder_type"."value" in ($1) or "payload_folders_folder_type"."value" is null or "payload_folders_folder_type"."value" = $2 or "payload_folders_folder_type"."value" is null)) order by "payload_folders"."name" asc, "payload_folders"."created_at" desc
params: media,] {
  query: 'select distinct "payload_folders"."id", "payload_folders"."name", "payload_folders"."name", "payload_folders"."created_at", "payload_folders"."created_at" from "payload_folders" left join "payload_folders_folder_type" on "payload_folders"."id" = "payload_folders_folder_type"."parent_id" where (("payload_folders"."folder_id" is null or "payload_folders"."folder_id" is null) and ("payload_folders_folder_type"."value" in ($1) or "payload_folders_folder_type"."value" is null or "payload_folders_folder_type"."value" = $2 or "payload_folders_folder_type"."value" is null)) order by "payload_folders"."name" asc, "payload_folders"."created_at" desc',
  params: [Array],
  [cause]: [error: invalid input value for enum enum_payload_folders_folder_type: "{}"] {
    length: 154,
    severity: 'ERROR',
    code: '22P02',
    detail: undefined,
    hint: undefined,
    position: undefined,
    internalPosition: undefined,
    internalQuery: undefined,
    where: "unnamed portal parameter $2 = '...'",
    schema: undefined,
    table: undefined,
    column: undefined,
    dataType: undefined,
    constraint: undefined,
    file: 'enum.c',
    line: '129',
    routine: 'enum_in'
  }
}

It seems like the query is injecting {} as a value for the enum enum_payload_folders_folder_type, which causes a PostgreSQL error because {} is not a valid enum value.

Configuration

payload.config.ts:

export default buildConfig({
  // ...
  folders: {
    browseByFolder: false,
  },
})

I am only using folders feature in one collection: media. It is configured as follows:

import type { CollectionConfig } from 'payload'

export const Media: CollectionConfig = {
  slug: 'media',
  access: {
    read: () => true,
    update: ({ req: { user } }) => Boolean(user),
    create: ({ req: { user } }) => Boolean(user),
    delete: ({ req: { user } }) => Boolean(user),
  },
  admin: {
    group: 'Admin',
  },
  fields: [
    {
      name: 'alt',
      type: 'text',
      defaultValue: '',
    },
  ],
  upload: true,
  folders: true,
}

[Awinel]

I'm having the same problem and just realized of that

[kubyshkin-vladyslav]

I found that disabling folders.collectionSpecific in payload.config.ts eliminates the error:

export default buildConfig({
  // ...
  folders: {
    browseByFolder: false,
    collectionSpecific: false, // defaults to true
  },
})

However, I would prefer to use collectionSpecific: true, as that better fits my use case - but I can’t do so until this issue is resolved.

[kubyshkin-vladyslav]

Fixed in v3.49.0