New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deleting first Group and Organization custom field is not possible #4094
Comments
I confirm that this deletion issue exists and I've created a fix for that, PR to master is added. |
Also I want to mention, that first two links added at the description are throwing Eternal Server Error, when I'm trying to open them (authorized user and anonymous), but they should throw at least 403 Forbidden: |
…deletion [#4094] Update Orgs/Groups logic for custom fields delete and update
…deletion [#4094] Update Orgs/Groups logic for custom fields delete and update
CKAN Version if known (or site URL)
2.6+
Please describe the expected behaviour
Each Group or Organization custom field marked for deletion should be deleted once the Update button is clicked. The deletion button should be displayed as a red button with an icon.
Please describe the actual behaviour
Whey you try to delete the first Group or Organization custom field, it only gets deleted when there are at least two custom fields set. When you try to delete the first custom field, when it's the only one in the group with paired values added, it does not get deleted once the Update button is clicked.
Also the delete icon is not rendered in < 2.8 and it's displayed as a simple checkbox.
What steps can be taken to reproduce the issue?
Navigate to any of the links above and mark the first custom field for deletion, then click Update. The field will not be deleted. Then add values to at least two custom fields, Update and mark the first one for deletion. When you click on Update again, it will be deleted.
Also, note that the delete icon is not rendered and only a simple checkbox is shown for marking.
The custom fields functionality is fully working for datasets, so please check the Manage dataset page for reference.
The text was updated successfully, but these errors were encountered: