MORPH
SIGN IN SIGN UP
payloadcms / payload UNCLAIMED

Payload is the open-source, fullstack Next.js framework, giving you instant backend superpowers. Get a full TypeScript backend and admin panel instantly. Use Payload as a headless CMS or for building powerful applications.

41461 0 1 TypeScript
Normal View History Raw
chore(ui): simplifies adminThumbnail functionality (#5615)
2024-04-03 08:49:31 -04:00
export const usersCollectionSlug = 'users'
export const customViews1CollectionSlug = 'custom-views-one'
export const customViews2CollectionSlug = 'custom-views-two'
feat(next): reorder document view tabs (#12288) Introduces the ability to customize the order of both default and custom tabs. This way you can make custom tabs appear before default ones, or change the order of tabs as you see fit. To do this, use the new `tab.order` property in your edit view's config: ```ts import type { CollectionConfig } from 'payload' export const MyCollectionConfig: CollectionConfig = { // ... admin: { components: { views: { edit: { myCustomView: { path: '/my-custom-view', Component: '/path/to/component', tab: { href: '/my-custom-view', order: 100, // This will put this tab in the first position }, } } } } } } ``` --------- Co-authored-by: Jacob Fletcher <jacobsfletch@gmail.com>
2025-06-13 15:28:29 +01:00
export const reorderTabsSlug = 'reorder-tabs'
chore(ui): simplifies adminThumbnail functionality (#5615)
2024-04-03 08:49:31 -04:00
export const geoCollectionSlug = 'geo'
feat(ui): allow array fields to be filtered in list view (#11925) ### What? Allows array fields to be filtered in the list view. ### Why? Array fields were not filterable in the list view although all other field types were filterable already. ### How? Adds handling for array fields as filter option. ![image](https://github.com/user-attachments/assets/6df1a113-1d9f-4d50-92f7-d1fceed294d0)
2025-05-01 20:19:43 +02:00
export const arrayCollectionSlug = 'array'
chore(ui): simplifies adminThumbnail functionality (#5615)
2024-04-03 08:49:31 -04:00
export const postsCollectionSlug = 'posts'
fix(ui): publish button shows locale-specific text without localized fields (#14690) ### What? Updates the publish button logic to check whether a collection/global has localized fields before displaying locale-specific button text ("Publish in [locale]"). The button now only shows locale-specific text when both conditions are met: 1. The collection/global has localized fields 2. `localization.defaultLocalePublishOption` is set to `'active'` ### Why? PR #13459 fixed the submenu "Publish in [specific locale]" button to not appear on collections without localized fields, but missed updating the main button label logic. This caused the main publish button to display "Publish in [locale]" even when a collection had no localized fields (when `defaultLocalePublishOption: 'active'` was set). ### How? - Updated `publishAll` calculation to check `canPublishSpecificLocale` (which includes the `hasLocalizedFields` check) instead of just checking if localization is enabled - Changed the button label rendering from `{localization ? defaultLabel : label}` to `{canPublishSpecificLocale ? defaultLabel : label}` Fixes #14386
2025-11-20 13:44:13 -05:00
export const localizedCollectionSlug = 'localized'
chore(ui): simplifies adminThumbnail functionality (#5615)
2024-04-03 08:49:31 -04:00
export const group1Collection1Slug = 'group-one-collection-ones'
export const group1Collection2Slug = 'group-one-collection-twos'
export const group2Collection1Slug = 'group-two-collection-ones'
export const group2Collection2Slug = 'group-two-collection-twos'
fix: field inside an unnamed group field erroring when used as a title (#12771) Fixes https://github.com/payloadcms/payload/issues/12632 Config sanitisation will error without this PR when attempting to useAsTitle a field inside an unnamed group field.
2025-06-12 05:57:37 -07:00
export const useAsTitleGroupFieldSlug = 'use-as-title-group-field'
chore(ui): simplifies adminThumbnail functionality (#5615)
2024-04-03 08:49:31 -04:00
export const hiddenCollectionSlug = 'hidden-collection'
feat: allows excluding entities from the nav sidebar / dashboard without disabling its routes (#9897) ### What? Previously, the `admin.group` property on `collection` / `global` configs allowed for a custom group and the `admin.hidden` property would not only hide the entity from the nav sidebar / dashboard but also disable its routes. ### Why? There was not a simple way to hide an entity from the nav sidebar / dashboard but still keep the entities routes. ### How? Now - we've added the `false` type to the `admin.group` field to account for this. Passing `false` to `admin.group` will hide the entity from the sidebar nav and dashboard but keep the routes available to navigate. I.e ``` admin: { group: false, }, ```
2024-12-11 13:31:12 -05:00
export const notInViewCollectionSlug = 'not-in-view-collection'
chore(ui): simplifies adminThumbnail functionality (#5615)
2024-04-03 08:49:31 -04:00
export const noApiViewCollectionSlug = 'collection-no-api-view'
feat: move disableDuplicate out of admin and update APIs (#5620)
2024-04-05 16:44:41 -04:00
export const disableDuplicateSlug = 'disable-duplicate'
feat(ui): adds disable copy to locale option to collection config (#11546) ### What? Adds new option to disable the `copy to locale` button, adds description to docs and adds e2e test. ### Why? Client request. ### How? The option can be used like this: ```ts // in collection config admin: { disableCopyToLocale: true, }, ```
2025-03-07 12:48:08 +00:00
export const disableCopyToLocale = 'disable-copy-to-locale'
chore(ui): simplifies adminThumbnail functionality (#5615)
2024-04-03 08:49:31 -04:00
export const uploadCollectionSlug = 'uploads'
feat(ui): make select and relationship field placeholder configurable (#12253) ### What? Allows to overwrite the default placeholder text of select and relationship fields. ### Why? The default placeholder text is generic. In some scenarios a custom placeholder can guide the user better. ### How? Adds a new property `admin.placeholder` to relationship and select field which allows to define an alternative text or translation function for the placeholder. The placeholder is used in the form fields as well as in the filter options. ![Screenshot 2025-04-29 at 15 28 54](https://github.com/user-attachments/assets/d83d60c8-d4f6-41b7-951c-9f21c238afd8) ![Screenshot 2025-04-29 at 15 28 19](https://github.com/user-attachments/assets/d2263cf1-6042-4072-b5a9-e10af5f380bb) --------- Co-authored-by: Dan Ribbens <DanRibbens@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Dan Ribbens <dan.ribbens@gmail.com>
2025-05-01 21:17:47 +02:00
export const placeholderCollectionSlug = 'placeholder'
fix(next): incorrect active state for partial matches of collection names in sidebar (#11511) Previously, collections with similar names (e.g., `uploads` and `uploads-poly`) both appeared active when viewing either collection. This was due to `pathname.startsWith(href)`, which caused partial matches. This update refines the `isActive` logic to prevent partial matches.
2025-03-03 16:46:47 -05:00
export const uploadTwoCollectionSlug = 'uploads-two'
feat: add support for custom Status component in document controls (#11154) ### What? This PR adds the ability to replace the Status section of the document or global edit view, without the need to replace the whole Edit view. ### Why? In certain cases there may be a need to add custom elements before or after the original Status component. In our case, we need to replace the whole Status component to support custom locale publishing logic and also for additional status indicators for the users. ### How? **In the `docs` package:** - Added a description of the Status component to the components section within both the collections and globals sections. **In the `next` package:** - Enabled rendering of the custom Status component. - Modified the Live Preview components to include the Status component prop. **In the `payload` package:** - Introduced type definitions for the Status component. - Implemented importMap generation for the Status component. **In the `ui` package:** - Modified the Edit view to pass the Status component to DocumentControls. - Updated the DocumentControls component to accept and render a custom Status component if defined. Now supports the following Status component in admin ```ts admin: { components: { edit: { Status: '/components/Status/index.tsx#Status', }, }, }, ``` --------- Co-authored-by: Elmo Egers <elmo.egers@smit.ee> Co-authored-by: Elmo Egers <uplaymedia@gmail.com> Co-authored-by: Jacob Fletcher <jacobsfletch@gmail.com>
2026-01-13 21:11:32 +02:00
export const customDocumentControlsSlug = 'custom-document-controls'
fix: update select options when the options prop changes (#6878) Fixes https://github.com/payloadcms/payload/issues/6869 Before, options from props were being stored in state and would not update when props changed. Now options are memoized and will update when the incoming `options` prop changes.
2024-06-20 12:01:29 -04:00
export const customFieldsSlug = 'custom-fields'
chore: passes allowCreate into list drawer and adds test (#11284) ### What? We had an `allowCreate` prop for the list drawer that doesn't do anything. This PR passes the prop through so it can be used. ### How? Passes `allowCreate` down to the list view and ties it with `hasCreatePermission` #### Testing - Use `admin` test suite and `withListDrawer` collection. - Test added to the `admin/e2e/list-view`. Fixes #11246
2025-02-20 12:31:36 +00:00
export const listDrawerSlug = 'with-list-drawer'
fix(ui): cannot filter by virtual relationship fields in WhereBuilder (#13686) ### What? - Fixed an issue where virtual relationship fields (`virtual: string`, e.g. `post.title`) could not be used in the WhereBuilder filter dropdown. - Ensured regular virtual fields (`virtual: true`) are still excluded since they are not backed by database fields. ### Why? Previously, attempting to filter by a virtual relationship caused runtime errors because the field was treated as a plain text field. At the same time, non-queryable virtuals needed to remain excluded to avoid invalid queries. ### How? - Updated `reduceFieldsToOptions` to recognize `virtual: string` fields and map them to their underlying path while keeping their declared type and operators. - Continued to filter out `virtual: true` fields in the same guard used for hidden/disabled fields.
2025-09-04 11:17:10 -04:00
export const virtualsSlug = 'virtuals'
feat: adds admin.formatDocURL function to control list view linking (#13773) ### What? Adds a new `formatDocURL` function to collection admin configuration that allows users to control the linkable state and URLs of first column fields in list views. ### Why? To provide a way to disable automatic link creation from the first column or provide custom URLs based on document data, user permissions, view context, and document state. ### How? - Added `formatDocURL` function type to `CollectionAdminOptions` that receives document data, default URL, request context, collection slug, and view type - Modified `renderCell` to call the function when available and handle three return types: - `null`: disables linking entirely - `string`: uses custom URL - other: falls back to no linking for safety - Added function to server-only properties to prevent React Server Components serialization issues - Updated `DefaultCell` component to support custom `linkURL` prop --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1211211792037945
2025-09-24 15:20:54 -04:00
export const formatDocURLCollectionSlug = 'format-doc-url'
chore: improve test suites, upgrade jest and playwright, add debug utilities for lexical (#4011) * feat(richtext-lexical): 'bottom' position value for plugins * feat: TestRecorderFeature * chore: restructuring to seed and clear db before each test * chore: make sure all tests pass * chore: make sure indexes are created in seed.ts - this fixes one erroring test * chore: speed up test runs through db snapshots * chore: support drizzle when resetting db * chore: simplify seeding process, by moving boilerplate db reset / snapshot logic into a wrapper function * chore: add new seeding process to admin test suite * chore(deps): upgrade jest and playwright * chore: make sure mongoose-specific tests are not skipped * chore: fix point test, which was depending on another test (that's bad!) * chore: fix incorrect import * chore: remove unnecessary comments * chore: clearly label lexicalE2E test file as todo * chore: simplify seed logic * chore: move versions test suite to new seed system
2023-11-06 16:38:40 +01:00
export const collectionSlugs = [
usersCollectionSlug,
customViews1CollectionSlug,
customViews2CollectionSlug,
geoCollectionSlug,
feat(ui): allow array fields to be filtered in list view (#11925) ### What? Allows array fields to be filtered in the list view. ### Why? Array fields were not filterable in the list view although all other field types were filterable already. ### How? Adds handling for array fields as filter option. ![image](https://github.com/user-attachments/assets/6df1a113-1d9f-4d50-92f7-d1fceed294d0)
2025-05-01 20:19:43 +02:00
arrayCollectionSlug,
chore: improve test suites, upgrade jest and playwright, add debug utilities for lexical (#4011) * feat(richtext-lexical): 'bottom' position value for plugins * feat: TestRecorderFeature * chore: restructuring to seed and clear db before each test * chore: make sure all tests pass * chore: make sure indexes are created in seed.ts - this fixes one erroring test * chore: speed up test runs through db snapshots * chore: support drizzle when resetting db * chore: simplify seeding process, by moving boilerplate db reset / snapshot logic into a wrapper function * chore: add new seeding process to admin test suite * chore(deps): upgrade jest and playwright * chore: make sure mongoose-specific tests are not skipped * chore: fix point test, which was depending on another test (that's bad!) * chore: fix incorrect import * chore: remove unnecessary comments * chore: clearly label lexicalE2E test file as todo * chore: simplify seed logic * chore: move versions test suite to new seed system
2023-11-06 16:38:40 +01:00
postsCollectionSlug,
group1Collection1Slug,
group1Collection2Slug,
group2Collection1Slug,
group2Collection2Slug,
hiddenCollectionSlug,
noApiViewCollectionSlug,
feat: add support for custom Status component in document controls (#11154) ### What? This PR adds the ability to replace the Status section of the document or global edit view, without the need to replace the whole Edit view. ### Why? In certain cases there may be a need to add custom elements before or after the original Status component. In our case, we need to replace the whole Status component to support custom locale publishing logic and also for additional status indicators for the users. ### How? **In the `docs` package:** - Added a description of the Status component to the components section within both the collections and globals sections. **In the `next` package:** - Enabled rendering of the custom Status component. - Modified the Live Preview components to include the Status component prop. **In the `payload` package:** - Introduced type definitions for the Status component. - Implemented importMap generation for the Status component. **In the `ui` package:** - Modified the Edit view to pass the Status component to DocumentControls. - Updated the DocumentControls component to accept and render a custom Status component if defined. Now supports the following Status component in admin ```ts admin: { components: { edit: { Status: '/components/Status/index.tsx#Status', }, }, }, ``` --------- Co-authored-by: Elmo Egers <elmo.egers@smit.ee> Co-authored-by: Elmo Egers <uplaymedia@gmail.com> Co-authored-by: Jacob Fletcher <jacobsfletch@gmail.com>
2026-01-13 21:11:32 +02:00
customDocumentControlsSlug,
fix: update select options when the options prop changes (#6878) Fixes https://github.com/payloadcms/payload/issues/6869 Before, options from props were being stored in state and would not update when props changed. Now options are memoized and will update when the incoming `options` prop changes.
2024-06-20 12:01:29 -04:00
customFieldsSlug,
feat: move disableDuplicate out of admin and update APIs (#5620)
2024-04-05 16:44:41 -04:00
disableDuplicateSlug,
chore: passes allowCreate into list drawer and adds test (#11284) ### What? We had an `allowCreate` prop for the list drawer that doesn't do anything. This PR passes the prop through so it can be used. ### How? Passes `allowCreate` down to the list view and ties it with `hasCreatePermission` #### Testing - Use `admin` test suite and `withListDrawer` collection. - Test added to the `admin/e2e/list-view`. Fixes #11246
2025-02-20 12:31:36 +00:00
listDrawerSlug,
fix(ui): cannot filter by virtual relationship fields in WhereBuilder (#13686) ### What? - Fixed an issue where virtual relationship fields (`virtual: string`, e.g. `post.title`) could not be used in the WhereBuilder filter dropdown. - Ensured regular virtual fields (`virtual: true`) are still excluded since they are not backed by database fields. ### Why? Previously, attempting to filter by a virtual relationship caused runtime errors because the field was treated as a plain text field. At the same time, non-queryable virtuals needed to remain excluded to avoid invalid queries. ### How? - Updated `reduceFieldsToOptions` to recognize `virtual: string` fields and map them to their underlying path while keeping their declared type and operators. - Continued to filter out `virtual: true` fields in the same guard used for hidden/disabled fields.
2025-09-04 11:17:10 -04:00
virtualsSlug,
feat: adds admin.formatDocURL function to control list view linking (#13773) ### What? Adds a new `formatDocURL` function to collection admin configuration that allows users to control the linkable state and URLs of first column fields in list views. ### Why? To provide a way to disable automatic link creation from the first column or provide custom URLs based on document data, user permissions, view context, and document state. ### How? - Added `formatDocURL` function type to `CollectionAdminOptions` that receives document data, default URL, request context, collection slug, and view type - Modified `renderCell` to call the function when available and handle three return types: - `null`: disables linking entirely - `string`: uses custom URL - other: falls back to no linking for safety - Added function to server-only properties to prevent React Server Components serialization issues - Updated `DefaultCell` component to support custom `linkURL` prop --- - To see the specific tasks where the Asana app for GitHub is being used, see below: - https://app.asana.com/0/0/1211211792037945
2025-09-24 15:20:54 -04:00
formatDocURLCollectionSlug,
fix(ui): publish button shows locale-specific text without localized fields (#14690) ### What? Updates the publish button logic to check whether a collection/global has localized fields before displaying locale-specific button text ("Publish in [locale]"). The button now only shows locale-specific text when both conditions are met: 1. The collection/global has localized fields 2. `localization.defaultLocalePublishOption` is set to `'active'` ### Why? PR #13459 fixed the submenu "Publish in [specific locale]" button to not appear on collections without localized fields, but missed updating the main button label logic. This caused the main publish button to display "Publish in [locale]" even when a collection had no localized fields (when `defaultLocalePublishOption: 'active'` was set). ### How? - Updated `publishAll` calculation to check `canPublishSpecificLocale` (which includes the `hasLocalizedFields` check) instead of just checking if localization is enabled - Changed the button label rendering from `{localization ? defaultLabel : label}` to `{canPublishSpecificLocale ? defaultLabel : label}` Fixes #14386
2025-11-20 13:44:13 -05:00
localizedCollectionSlug,
chore: improve test suites, upgrade jest and playwright, add debug utilities for lexical (#4011) * feat(richtext-lexical): 'bottom' position value for plugins * feat: TestRecorderFeature * chore: restructuring to seed and clear db before each test * chore: make sure all tests pass * chore: make sure indexes are created in seed.ts - this fixes one erroring test * chore: speed up test runs through db snapshots * chore: support drizzle when resetting db * chore: simplify seeding process, by moving boilerplate db reset / snapshot logic into a wrapper function * chore: add new seeding process to admin test suite * chore(deps): upgrade jest and playwright * chore: make sure mongoose-specific tests are not skipped * chore: fix point test, which was depending on another test (that's bad!) * chore: fix incorrect import * chore: remove unnecessary comments * chore: clearly label lexicalE2E test file as todo * chore: simplify seed logic * chore: move versions test suite to new seed system
2023-11-06 16:38:40 +01:00
]
feat: add support for custom Status component in document controls (#11154) ### What? This PR adds the ability to replace the Status section of the document or global edit view, without the need to replace the whole Edit view. ### Why? In certain cases there may be a need to add custom elements before or after the original Status component. In our case, we need to replace the whole Status component to support custom locale publishing logic and also for additional status indicators for the users. ### How? **In the `docs` package:** - Added a description of the Status component to the components section within both the collections and globals sections. **In the `next` package:** - Enabled rendering of the custom Status component. - Modified the Live Preview components to include the Status component prop. **In the `payload` package:** - Introduced type definitions for the Status component. - Implemented importMap generation for the Status component. **In the `ui` package:** - Modified the Edit view to pass the Status component to DocumentControls. - Updated the DocumentControls component to accept and render a custom Status component if defined. Now supports the following Status component in admin ```ts admin: { components: { edit: { Status: '/components/Status/index.tsx#Status', }, }, }, ``` --------- Co-authored-by: Elmo Egers <elmo.egers@smit.ee> Co-authored-by: Elmo Egers <uplaymedia@gmail.com> Co-authored-by: Jacob Fletcher <jacobsfletch@gmail.com>
2026-01-13 21:11:32 +02:00
export const customGlobalDocumentControlsSlug = 'custom-global-document-controls'
chore(ui): simplifies adminThumbnail functionality (#5615)
2024-04-03 08:49:31 -04:00
export const customGlobalViews1GlobalSlug = 'custom-global-views-one'
export const customGlobalViews2GlobalSlug = 'custom-global-views-two'
export const globalSlug = 'global'
export const group1GlobalSlug = 'group-globals-one'
export const group2GlobalSlug = 'group-globals-two'
export const hiddenGlobalSlug = 'hidden-global'
feat!: custom views are now public by default and fixed some issues with notFound page (#8820) This PR aims to fix a few issues with the notFound page and custom views so it matches v2 behaviour: - Non authorised users should always be redirected to the login page regardless if not found or valid URL - Previously notFound would render for non users too potentially exposing valid but protected routes and creating a confusing workflow as the UI was being rendered as well - Custom views are now public by default - in our `admin` test suite, the `/admin/public-custom-view` is accessible to non users but `/admin/public-custom-view/protected-nested-view` is not unless the checkbox is true in the Settings global, there's e2e coverage for this - Fixes https://github.com/payloadcms/payload/issues/8716
2024-10-30 11:29:29 -06:00
feat: allows excluding entities from the nav sidebar / dashboard without disabling its routes (#9897) ### What? Previously, the `admin.group` property on `collection` / `global` configs allowed for a custom group and the `admin.hidden` property would not only hide the entity from the nav sidebar / dashboard but also disable its routes. ### Why? There was not a simple way to hide an entity from the nav sidebar / dashboard but still keep the entities routes. ### How? Now - we've added the `false` type to the `admin.group` field to account for this. Passing `false` to `admin.group` will hide the entity from the sidebar nav and dashboard but keep the routes available to navigate. I.e ``` admin: { group: false, }, ```
2024-12-11 13:31:12 -05:00
export const notInViewGlobalSlug = 'not-in-view-global'
feat!: custom views are now public by default and fixed some issues with notFound page (#8820) This PR aims to fix a few issues with the notFound page and custom views so it matches v2 behaviour: - Non authorised users should always be redirected to the login page regardless if not found or valid URL - Previously notFound would render for non users too potentially exposing valid but protected routes and creating a confusing workflow as the UI was being rendered as well - Custom views are now public by default - in our `admin` test suite, the `/admin/public-custom-view` is accessible to non users but `/admin/public-custom-view/protected-nested-view` is not unless the checkbox is true in the Settings global, there's e2e coverage for this - Fixes https://github.com/payloadcms/payload/issues/8716
2024-10-30 11:29:29 -06:00
export const settingsGlobalSlug = 'settings'
chore: improve test suites, upgrade jest and playwright, add debug utilities for lexical (#4011) * feat(richtext-lexical): 'bottom' position value for plugins * feat: TestRecorderFeature * chore: restructuring to seed and clear db before each test * chore: make sure all tests pass * chore: make sure indexes are created in seed.ts - this fixes one erroring test * chore: speed up test runs through db snapshots * chore: support drizzle when resetting db * chore: simplify seeding process, by moving boilerplate db reset / snapshot logic into a wrapper function * chore: add new seeding process to admin test suite * chore(deps): upgrade jest and playwright * chore: make sure mongoose-specific tests are not skipped * chore: fix point test, which was depending on another test (that's bad!) * chore: fix incorrect import * chore: remove unnecessary comments * chore: clearly label lexicalE2E test file as todo * chore: simplify seed logic * chore: move versions test suite to new seed system
2023-11-06 16:38:40 +01:00
export const noApiViewGlobalSlug = 'global-no-api-view'
export const globalSlugs = [
customGlobalViews1GlobalSlug,
customGlobalViews2GlobalSlug,
globalSlug,
group1GlobalSlug,
group2GlobalSlug,
hiddenGlobalSlug,
noApiViewGlobalSlug,
]
fix(ui): fixed many bugs in the WhereBuilder relationship select menu (#10553) Following https://github.com/payloadcms/payload/pull/10551, I found and fixed a handful more bugs: - When writing to the input, the results that were already there were not cleaned, causing incorrect results to appear. - the scroll was causing an infinite loop that showed repeated elements - optimization: only the required field is selected (not required) - refs are set to the initial value to avoid a state where nothing can be searched
2025-01-20 16:14:49 -03:00
export const with300DocumentsSlug = 'with300documents'
feat(ui): adds new editMenuItems custom component (#12649) ## What Adds a new custom component called `editMenuItems` that can be used in the document view. This options allows users to inject their own custom components into the dropdown menu found in the document controls (the 3 dot menu), the provided component(s) will be added below the default existing actions (Create New, Duplicate, Delete and so on). ## Why To increase flexibility and customization for users who wish to add functionality to this menu. This provides a clean and consistent way to add additional actions without needing to override or duplicate existing UI logic. ## How - Introduced the `editMenuItems` slot in the document controls dropdown (three-dot menu) - in edit and preview tabs. - Added documentation and tests to cover this new custom component #### Testing Use the `admin` test suite and go to the `edit menu items` collection
2025-06-03 14:57:48 +01:00
export const editMenuItemsSlug = 'edit-menu-items'
Reference in New Issue Copy Permalink