# 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:** 38
### 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: [May 16, 2017, 10:05pm UTC](https://meta.discourse.org/t/question-answer-plugin/56032/38 "2017-05-16T22:05:50Z")
> [@stantyan](#): > > Do you think this plugin could possibly significantly slow down page load speed? if there are lot’s of posts in a topic. No, it won’t affect page load speed. > [@stantyan](#): > > Also, is there any possibility that this plugin will conflict with future discourse developments and updates. For example, if t hey decided to roll out their own “posts up-voting” feature. Yes, this is a possibility with any plugin. If Discourse releases a core mechanism for up-voting posts then I will discontinue work on this and use that instead of this. > [@stantyan](#): > > And the last one, is there any was to turn your plugin active site-wide in all categories? I have about 100 categories, and going to each category settings to turn on the plugin is PITA No, there isn’t yet. I could add this, but I strongly suggest you test this in a single category first, for at least a few weeks. This is a new plugin. I don’t use it in production myself yet. [quote=“stantyan, post:37, topic:56032”] As far as I understood, vote counts of each post are saved in a database and remain there even if I remove this plugin, is this correct?[/quote] Correct. > [@stantyan](#): > > And if yes, could it possibly cause some issues in future discourse updates? The main question here is whether a future Discourse version will use the existing `vote_count` property of posts. If it does, then all votes made with this plugin will be picked up by the new core functionality. Remember that `vote_count` is a property in the core Discourse code itself. It’s been there since the [initial release](https://github.com/discourse/discourse/blob/5dbd6a304bed5400be481d71061d3e3ebb4d6785/db/migrate/20120924182031_add_vote_count_to_posts.rb) of Discourse, i.e. 2013. The alternative way of handling the storage of votes would have been to create a post custom field, i.e. `post.custom_fields['vote_count']`. The reason I chose not to do this was because it seemed redundant given there was an existing post property, and it would also make it harder to migrate the data created by this plugin if the core `vote_count` field were used in the future for a similar purpose. Also, I would have to re-create the front-end post-action UI and translations that already exist for voting. I suppose there is a risk that `vote_count` could be used in the future in a such a way that does not conceptually relate to the way I am using it here, however I doubt it. Something called `vote_count` on a post object could only really be used for storing the count of how many people have voted for that post. If you’re wondering whether this plugin conflicts with the [poll plugin](https://github.com/discourse/discourse/tree/master/plugins/poll) or the [topic voting plugin](https://meta.discourse.org/t/discourse-voting/40121), it doesn’t. Those plugins use different fields. All are about voting, but different kinds of voting… ![image](https://global.discourse-cdn.com/meta/original/3X/2/4/2476c7081e17ec668e19af3baa27fd661ac7f912.gif) --- _[View the full topic](https://meta.discourse.org/t/question-answer-plugin/56032)._