# Custom field casting affected by recent update?

**URL:** <https://meta.discourse.org/t/custom-field-casting-affected-by-recent-update/122746>\
**Category:** Development\
**Created:** [July 11, 2019, 11:34pm UTC](https://meta.discourse.org/t/custom-field-casting-affected-by-recent-update/122746 "2019-07-11T23:34:41Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)\
**Post date:** [July 12, 2019, 10:46am UTC](https://meta.discourse.org/t/custom-field-casting-affected-by-recent-update/122746/4 "2019-07-12T10:46:06Z")

</div>

> [@zogstrip](#):
>
> This _was_ a known bug with custom fields.

Yes, it’s cropped up a few times in the past. This latest rash seems to coincide with recent work on the `has_custom_fields.rb` concern, so there may be something to review there.

This doesn’t fix it, but helps to address it if it arises:

[https://github.com/discourse/discourse/pull/7886](https://github.com/discourse/discourse/pull/7886)

---

_[View the full topic](https://meta.discourse.org/t/custom-field-casting-affected-by-recent-update/122746)._