# Question Answer Plugin **URL:** https://meta.discourse.org/t/question-answer-plugin/56032 **Category:** Plugin **Tags:** deprecated **Created:** [January 19, 2017, 4:43pm UTC](https://meta.discourse.org/t/question-answer-plugin/56032 "2017-01-19T16:43:47Z") **Posts on this page:** 1 **Showing post:** 304
### 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: [October 6, 2022, 1:29pm UTC](https://meta.discourse.org/t/question-answer-plugin/56032/304 "2022-10-06T13:29:46Z")
As mentioned in the other topic, essentially you’re experiencing an issue with a migration in the Upvotes Plugin. The ultimate solution here is for that migration to handle edge cases that can arise with Discourse custom fields when used at scale. > [@Plugin causing errors during rebuild](https://meta.discourse.org/t/plugin-causing-errors-during-rebuild/241110/23): > > @Jaap-Jan_Swijnenburg I’m sorry you’ve experienced an issue. I’ll respectfully disagree with you there slight_smile The old QnA plugin used [standard Discourse custom field type casting](https://github.com/paviliondev/discourse-question-answer/blob/master/plugin.rb#L85), which is meant to handle casting that field to JSON. But that just doesn’t work in some cases (like this one), which is why you (ideally) need to build in format checks when you’re working with Discourse custom fields (particularly if you’re working with quite old code and data like this). I would suggest th… --- _[View the full topic](https://meta.discourse.org/t/question-answer-plugin/56032)._