# Follow up: Assign Plugin Conflict

**URL:** https://meta.discourse.org/t/follow-up-assign-plugin-conflict/126324
**Category:** Support
**Created:** [August 20, 2019, 5:42pm UTC](https://meta.discourse.org/t/follow-up-assign-plugin-conflict/126324 "2019-08-20T17:42:33Z")
**Posts on this page:** 1
**Showing post:** 23

<div class="post-metadata">

### Author: ![Roman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/roman/32/157504_2.png) [@Roman](https://meta.discourse.org/u/Roman)
#### Post date: [October 1, 2019, 12:00pm UTC](https://meta.discourse.org/t/follow-up-assign-plugin-conflict/126324/23 "2019-10-01T12:00:21Z")

</div>

I’m glad that we could troubleshoot and solve this Jim!

I’m closing this now since we’re already tracking this issue here:

> [@Discourse Assign - bug taking site down](https://meta.discourse.org/t/discourse-assign-bug-taking-site-down/128049):
>
> I recently changed the site setting for the group(s) that are able to use Discourse Assign. Something went awfully wrong when I hit the update button, it took the whole site down. I have since disabled Discourse Assign, which has got the site back up, but I am unable to get Discourse Assign working again. When I re-enable it, the site is taken down, and cannot change the site settings for the Discourse Assign plugin. I am looking at the error logs, there are two: ActiveRecord::StatementInva…

---

_[View the full topic](https://meta.discourse.org/t/follow-up-assign-plugin-conflict/126324)._