- Issue created by @blanca.esqueda
"Field Settings" tab is not available anymore, it is a change done in core, it seems like introduced for 10.2 and forward - reference https://www.drupal.org/node/3347291 →
Before:
Now:
When adding a new field, config enforce doesn't seems to be creating the storage or config.
It appears on the screen but not on git.
How to replicate errors:
When creating a new field if the first screen is used to set enforce config we get the following warnings/errors
Coming back to the record and clicking save again to config enforce send to an error screen
And the following warnings when opening another page
When creating a field skipping config enforce on the first screen, then the record is saved and coming back to edit the record and update config enforce don't fail, and seem to create the files, but unable to select where the storage will be saved.
By doing the above it creates both the regular yml file and the storage one.
The only problem is it creates the storage yml under the default folder, so after update this information on the config settings (bulk form).
However, it was noticed that when fields are updated, they seems to delete the field permissions and dependencies (as conditional fields) from the storage yml files.
TBD - Include the missing config enforce fields on the add/edit file form.
TBD - Include the missing config enforce fields on the add/edit file form.
Active
2.0
Code