# Update Collection After Editing Settings

**URL:** <https://discourse.getcockpit.com/t/update-collection-after-editing-settings/1768>\
**Category:** Support\
**Created:** [January 5, 2021, 3:10pm UTC](https://discourse.getcockpit.com/t/update-collection-after-editing-settings/1768 "2021-01-05T15:10:42Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![raffaelj](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/raffaelj/32/331_2.png) [@raffaelj](https://discourse.getcockpit.com/u/raffaelj)\
**Post date:** [January 6, 2021, 2:24pm UTC](https://discourse.getcockpit.com/t/update-collection-after-editing-settings/1768/3 "2021-01-06T14:24:46Z")

</div>

@tophermurphy @pixelkarma See my answer in this thread:

> [@Remove Collection Field data from Entry when Field is deleted?](https://discourse.getcockpit.com/t/remove-collection-field-data-from-entry-when-field-is-deleted/1760/2):
>
> It’s not a bug - it’s a feature, but I see the problem. Keeping only active fields is probably a bad idea, because there are a lot of hidden fields, e. g.: meta info \_created, \_modified etc. localized fields with language code suffixes title\_de auto generated slugs title\_slug some addons create hidden meta fields, e. g. UniqueSlugs… But there is a cli command to fix that behaviour. cd /path/to/cockpit php ./cp collection/removefield --collection \<collection name\> --field \<field name\> cd…

---

_[View the full topic](https://discourse.getcockpit.com/t/update-collection-after-editing-settings/1768)._