Summary
Deleting a custom field causes all custom fields to disappear from the Custom Fields administration page.
Environment
- Windshift self-hosted
- Docker deployment
Steps to Reproduce
- Open Administration/System Settings.
- Navigate to Content & Structure → Custom Fields.
- Create multiple custom fields.
- Delete one of the custom fields.
- Return to the Custom Fields list.
Actual Behavior
After deleting a custom field, all custom fields disappear from the Custom Fields administration page.
The existing custom fields are no longer visible in the configuration list, even though only a single field was deleted.
Expected Behavior
Deleting one custom field should only remove that specific field.
All remaining custom fields should continue to be displayed and available for configuration.
Additional Information
The issue seems to affect the custom fields listing after a delete operation.
The deletion action appears to trigger an incorrect refresh or state update, causing the entire custom field list to become empty.
Possible Cause
Possible issues include:
- The frontend state is not being refreshed correctly after deletion.
- The delete operation invalidates or clears the entire custom fields collection.
- The API response after deletion is not being handled correctly.
- A failed reload causes the UI to display an empty list.
Request
Please verify the custom field deletion flow:
- Deleting a single custom field.
- Refreshing the custom field list after deletion.
- Preserving existing custom field configurations.
Thanks!
Summary
Deleting a custom field causes all custom fields to disappear from the Custom Fields administration page.
Environment
Steps to Reproduce
Actual Behavior
After deleting a custom field, all custom fields disappear from the Custom Fields administration page.
The existing custom fields are no longer visible in the configuration list, even though only a single field was deleted.
Expected Behavior
Deleting one custom field should only remove that specific field.
All remaining custom fields should continue to be displayed and available for configuration.
Additional Information
The issue seems to affect the custom fields listing after a delete operation.
The deletion action appears to trigger an incorrect refresh or state update, causing the entire custom field list to become empty.
Possible Cause
Possible issues include:
Request
Please verify the custom field deletion flow:
Thanks!