You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an upload field, if you select "choose existing" and then click on a file, the "permissions" tab of the form on the right doesn't show the "viewer groups" and "editor groups" fields. These are SearchableDropdownField in 5.x-dev.
With yarn dev in silverstripe/admin, you get the following console output:
Uncaught exception TypeError: schema is undefined
onmatch SearchableDropdownFieldEntwine.js:16
When you insert the file, you get this console output:
Uncaught exception TypeError: Root is undefined
onunmatch SearchableDropdownFieldEntwine.js:27
How to reproduce
In any upload field, click "choose existing"
Click on a file, but don't insert it yet
Look in the "permissions" tab in the form on the right.
Possible Solution
No response
Additional Context
No response
Validations
Check that there isn't already an issue that reports the same bug
Double check that your reproduction steps work in a fresh installation of silverstripe/installer (with any code examples you've provided)
As per #1699 (comment) I'll leave it up to you to decide whether to close this issue and raise a separate one about TreeDropdownField not displaying, or whether you want to work on that as part of the existing issue.
Module version(s) affected
5.x-dev (unreleased feature for 5.2)
Description
In an upload field, if you select "choose existing" and then click on a file, the "permissions" tab of the form on the right doesn't show the "viewer groups" and "editor groups" fields. These are
SearchableDropdownField
in 5.x-dev.With
yarn dev
in silverstripe/admin, you get the following console output:When you insert the file, you get this console output:
How to reproduce
Possible Solution
No response
Additional Context
No response
Validations
silverstripe/installer
(with any code examples you've provided)PR
The text was updated successfully, but these errors were encountered: