This was occurring on all topics, not just QnA ones. We have a ‘Questions’ category when all topics are QnA, and also have the ‘question’ tag to make a topic QnA.
The behavior is slightly different now though, before the sort order they were given fixed them at the bottom of the list, now they are still out of order, but newer posts are below them.
Thanks @AJDurant.
One of our clients experienced this issue, so I was able to take a closer look at a dataset where it was occuring. I believe one issue here might be the when topics where a QA tag is removed are handled.
I’ve started a PR that addresses this issue, which @mbcahyono and I will work on
https://github.com/paviliondev/discourse-question-answer/pull/38
The way to fix the issue for a specific topic is:
./launcher enter app
rails c
topic = Topic.find(<topic_id>)
topic.posts.each { |p| p.update_columns(sort_order: p.post_number) }
If anyone needs any more hands on help addressing this issue on their server please reach out to me privately and I can help you address it (no charge).
Sorry for not responding sooner. I’ve been traveling this week. I can confirm your code above is fixing the individual posts with issues.
I also confirmed that running the following command does NOT fix the problem
rake "posts:reorder_posts[1234]"
Is there a way to run this across all posts - basically loop over all posts?
And you’ve just run rake posts:reorder_posts by itself and it doesn’t work? Please try that again first.
If that doesn’t work you can run this
./launcher enter app
rails c
Post.update_all("sort_order = post_number")
We have figured out what the issue is. It was introduced back in August. We’ll push a fix for it shortly, with a test for the case.
https://github.com/paviliondev/discourse-question-answer/pull/38#issuecomment-739137531
I ran the above command and got the following error
root@REMOVE-web-only:/var/www/discourse# rake posts:reorder_posts
rake aborted!
PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "post_timings_unique"
DETAIL: Key (topic_id, post_number, user_id)=(1567, 20, 3) already exists.
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-mini-profiler-2.2.0/lib/patches/db/pg.rb:110:in `exec'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-mini-profiler-2.2.0/lib/patches/db/pg.rb:110:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/mini_sql-0.3/lib/mini_sql/postgres/connection.rb:201:in `run'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/mini_sql-0.3/lib/mini_sql/postgres/connection.rb:173:in `exec'
/var/www/discourse/lib/tasks/posts.rake:368:in `block (3 levels) in <main>'
/var/www/discourse/lib/tasks/posts.rake:351:in `each'
/var/www/discourse/lib/tasks/posts.rake:351:in `block (2 levels) in <main>'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.3.3/lib/active_record/connection_adapters/abstract/database_statements.rb:280:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.3.3/lib/active_record/connection_adapters/abstract/transaction.rb:280:in `block in within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:26:in `block (2 levels) in synchronize'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.3.3/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.3.3/lib/active_record/connection_adapters/abstract/transaction.rb:278:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.3.3/lib/active_record/connection_adapters/abstract/database_statements.rb:280:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activerecord-6.0.3.3/lib/active_record/transactions.rb:212:in `transaction'
/var/www/discourse/lib/tasks/posts.rake:312:in `block in <main>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'
Tasks: TOP => posts:reorder_posts
(See full trace by running task with --trace)
I did not run the second command once I saw the duplicate key error thinking that might be a larger issue.
That looks like an issue with your db that’s independent of this, but blocking a fix here. I’ll pm you shortly and we can debug that seperately.
Thanks @angus that all seems to be working correctly now 
Message (49 copies reported)
Job exception: uninitialized constant Jobs::QaUpdateTopicsPostOrder
Did you mean? Jobs::UpdateTopicPostOrder
Jobs::QAUpdateTopicsPostOrder
Backtrace
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/inflector/methods.rb:284:in const_get' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/inflector/methods.rb:284:in block in constantize’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/inflector/methods.rb:280:in each' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/inflector/methods.rb:280:in inject’
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/inflector/methods.rb:280:in constantize' /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/core_ext/string/inflections.rb:68:in constantize’
/var/www/discourse/app/jobs/base.rb:288:in enqueue' /var/www/discourse/app/jobs/onceoff/onceoff.rb:40:in block in enqueue_all’
/var/www/discourse/app/jobs/onceoff/onceoff.rb:37:in each' /var/www/discourse/app/jobs/onceoff/onceoff.rb:37:in enqueue_all’
Sorry for the issue. Working on it, waiting to be merged:
https://github.com/paviliondev/discourse-question-answer/pull/39
Cool, I’m excited to see this merged and look forward to the fix. Happy Holidays.
What is the role of the “QnA one-to-many format.” setting that can be found in category settings?
It’s a deprecated feature, which we’ll be removing from the QnA Plugin in the near future. That feature now has it’s own dedicated plugin
How do you remove your vote? In options, there is a configuration of how much time you have to undo the vote, but I don’t see a way how to actually do that.
Are there any good examples of this plugin in use in the wild? I’d love to see it in action!
Select the yellow “Undo your upvote” text - see screenshot below.
I noticed a few feedback items:
qa trust level vote limits admin setting is deselected by default, but I still get an error “You cannot exceed the number of votes for your trust level” which doesn’t maek sense? 
That’s OK by design or there is a bug in my theme?
Thanks!
Can we recover the normal order of posts uninstalling the plugin?
I see that previous reported bug really messy our conversations 
Yes there seems to be a conflict between this plugin and the Solved Plugin, i.e. the “Solution” element in your screenshot. This plugin does not yet offiically support the Solved Plugin.
Yes, you just need to disable the plugin in a category in which its enabled and the posts will go back to their normal order.
Obrigado por este plugin! Uma pergunta: o que acontece com o conteúdo se o plugin for removido? Fica claro que os votos e a ordenação especial das respostas desaparecerão, mas o que aconteceria com as “respostas” e “comentários” de cada resposta? Elas permanecerão ou desaparecerão?
O motivo da minha pergunta é que começamos a usar este plugin para construir um guia colaborativo do usuário. Ter comentários para cada resposta é muito conveniente. Os votos são promissores também, mas e se eles vierem com consequências não intencionais e quisermos nos livrar deles? Seria uma pena perder o guia porque queremos remover os votos.
No pior cenário, acho que poderíamos remover a interface de votação via CSS, mantendo o plugin.
Ótima pergunta.
Comentários e respostas são apenas posts aparecendo em uma ordem diferente. Eles serão mantidos.
Se você quiser desinstalar o plugin, basta desmarcar “Tornar todos os tópicos nesta categoria QnA” nas configurações da categoria. Isso reverterá todos os posts para sua ordem original.
Por exemplo, acabei de reverter a categoria QnA em try.thepavilion.io para sua ordem padrão (ou seja, cronológica (mudará novamente em 24 horas).
Ok, saber disso é encorajador. Tentaremos o plugin e, se os votos não cumprirem sua missão, teremos duas opções para removê-los: a leve via CSS e a pesada desativando o plugin. Nenhum conteúdo perdido. Ótima adaptação dos componentes principais do Discourse!
A propósito, só para constar, estamos usando seu plugin para criar um guia de vídeo colaborativo de um produto, onde as pessoas são convidadas a vincular vídeos que criaram sobre aspectos deste produto. Personalizamos alguns rótulos para que funcione. Veja Bitwig Video Guide - Bitwish (acabamos de começar, então está quase vazio; além disso, a maioria das subcategorias está silenciada e é por isso que parece mais vazio para usuários anônimos).
