# 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:** 141

<div class="post-metadata">

### Author: ![bletch](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bletch/32/69088_2.png) [@bletch](https://meta.discourse.org/u/bletch)
#### Post date: [August 27, 2018, 10:05pm UTC](https://meta.discourse.org/t/question-answer-plugin/56032/141 "2018-08-27T22:05:00Z")

</div>

Hi @angus, I’ve tested the latest version of the QA Plugin on our live site and I can’t reproduce the problem.

> [@bletch](#):
>
> However, on my live site I have disabled the QA Plugin and the error is still there - hence my comment that it might be shared code with one of your other plugins which are still enabled (but I’m guessing there).

As I mention above, I’m wondering if the problem is in code shared across plugins because I re-enabled your Elections Plugin (which I had disabled whilst trying to track down the bug) and I was then able to reproduce the problem again.

Both the Elections and the QA Plugin were enabled at that point.

Disabling the Elections plugin, but leaving the QA Plugin enabled meant that I was no longer able to reproduce the problem.

So it looks fixed in the QA Plugin but maybe still present in the Elections Plugin?

Thanks for all your efforts, it’s really appreciated out there in Discourse land!

Cheers, Bletch.

---

_[View the full topic](https://meta.discourse.org/t/question-answer-plugin/56032)._