'
> Tasks: TOP => db:migrate => db:load_config => environment
> (See full trace by running task with --trace)
> I, [2022-12-09T10:13:36.170591 #1] INFO -- : gem install rrule -v 0.4.4 -i /var/www/discourse/plugins/discourse-calendar/gems/2.7.6 --no-document --ignore-dependencies --no-user-install
> Successfully installed rrule-0.4.4
> 1 gem installed
>
> FAILED
> --------------------
>
> ```
1. Then i removed the first one. Build is ok but the app is no longer running :
- I got an HTTP 500
- nginx error logs give me something like :
```bash
root@slazvmeutp01:/opt/discourse# cat /var/opt/discourse/var-log/nginx/error.log
2022/12/09 10:47:34 [notice] 537#537: signal process started
2022/12/09 10:47:37 [error] 554#554: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 18.156.156.214, server: _, request: "POST /message-bus/76e1bd78eedf43a5a337b6f44a8b88d0/poll?dlp=t HTTP/2.0", upstream: "http://127.0.0.1:3000/message-bus/76e1bd78eedf43a5a337b6f44a8b88d0/poll?dlp=t", host: "mydiscourse.domain.com", referrer: "https://mydiscourse.domain.com/admin/plugins"
2022/12/09 10:59:08 [crit] 554#554: *398 SSL_do_handshake() failed (SSL: error:141CF06C:SSL routines:tls_parse_ctos_key_share:bad key share) while SSL handshaking, client: 212.102.40.218, server: 0.0.0.0:443
2022/12/09 11:25:50 [notice] 530#530: signal process started
```
I noticed that Git repo [https://github.com/discourse/discourse-question-answer](https://github.com/discourse/discourse-question-answer) now redirects to the second [https://github.com/discourse/discourse-post-voting](https://github.com/discourse/discourse-post-voting).
So it would explain the conflict on first build today.
But what about now ? It mentions TLS error rather than a plugin error…
Any idea ?
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [December 9, 2022, 12:19pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/2 "2022-12-09T12:19:58Z")
Only having `discourse-post-voting` is the right move. 👍
I’m not sure about nginx error logs, but I don’t suppose you also have `discourse-feature-voting` in your plugins too, do you?
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [December 9, 2022, 1:10pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/3 "2022-12-09T13:10:13Z")
> [@JammyDodger](#):
>
> I’m not sure about nginx error logs, but I don’t suppose you also have `discourse-feature-voting` in your plugins too, do you?
OMG you were right !!
I had it too and I can see Git repo also redirects to [https://github.com/discourse/discourse-post-voting](https://github.com/discourse/discourse-post-voting) !! 🙀
But wait… topic-voting AND q&a merged into post-voting ? Are features cumulated ?
So here is my latest plugin list :
```bash
hooks:
after_code:
- exec:
cd: $home/plugins
cmd:
- mkdir -p plugins
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/discourse/discourse-openid-connect
- git clone https://github.com/discourse/discourse-solved
- git clone https://github.com/discourse/discourse-yearly-review
- git clone https://github.com/discourse/discourse-checklist
- git clone https://github.com/discourse/discourse-docs
- git clone https://github.com/discourse/discourse-reactions
#- git clone https://github.com/discourse/discourse-feature-voting
- git clone https://github.com/discourse/discourse-calendar
#- git clone https://github.com/discourse/discourse-gamification
- git clone https://github.com/discourse/discourse-gamification && cd discourse-gamification && git checkout 6a399b4c220f31de62049504d27ff6e50611fbef
- git clone https://github.com/discourse/discourse-follow
- git clone https://github.com/discourse/discourse-spoiler-alert
- git clone https://github.com/paviliondev/discourse-news
- git clone https://github.com/cfstras/discourse-konami.git
#- git clone https://github.com/discourse/discourse-question-answer
- git clone https://github.com/discourse/discourse-post-voting
```
Discourse finally responds.
But now other problems :
1. Plugin admin show “question & answer”…
2. When I create a topic, the item menu is not good :
3. Config in category settings always show q&a
So it seems q&a is always there…
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [December 9, 2022, 1:18pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/4 "2022-12-09T13:18:21Z")
> [@gmoirod](#):
>
> I had it too and I can see Git repo also redirects to [GitHub - discourse/discourse-post-voting: Allows users to vote on posts within a topic · GitHub](https://github.com/discourse/discourse-post-voting) !!
Nope I am wrong !
This is separate projects sorry.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [December 9, 2022, 1:19pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/5 "2022-12-09T13:19:27Z")
`discourse-feature-voting` was the old name for [Discourse Topic Voting](https://meta.discourse.org/t/discourse-topic-voting/40121), and having the old name in there causes some loading conflicts when you also have `post-voting` in there as well. If you add the new `discourse-topic-voting` you should be able to have both again. 👍
I’m not sure why you have the old Q&A format still? I notice you’re checking out a specific Gamification version - is that because you’re locked to a certain compatibility?
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [December 9, 2022, 1:23pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/6 "2022-12-09T13:23:09Z")
> [@JammyDodger](#):
>
> I notice you’re checking out a specific Gamification version - is that because you’re locked to a certain compatibility?
Yes !
I am the one who tracks “stable” version of Discourse 😅
This is a workaround I mentioned here : [Database migrate fails in "stable" version - #2 by gmoirod](https://meta.discourse.org/t/database-migrate-fails-in-stable-version/243979/2)
> [@JammyDodger](#):
>
> If you add the new `discourse-topic-voting` you should be able to have both again.
Ok I am going for a test right now
> [@JammyDodger](#):
>
> I’m not sure why you have the old Q&A format still?
Me neither 😭
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [December 9, 2022, 1:26pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/7 "2022-12-09T13:26:02Z")
> [@gmoirod](#):
>
> > [@JammyDodger](#):
> >
> > I’m not sure why you have the old Q&A format still?
>
> Me neither 😭
The official `post-voting` plugin was renamed to ‘post-voting’ relatively recently, and was Q&A in the UI, etc for a while. It may be that your install is not picking up those changes as you’re tracking Stable?
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [December 9, 2022, 1:27pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/8 "2022-12-09T13:27:09Z")
Is there a way to properly “uninstall” a plugin ?
I could use that ton uninstall q&a and post-voting, then reinstall post-voting…
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [December 9, 2022, 1:30pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/9 "2022-12-09T13:30:11Z")
When you check your `/admin/upgrade` page, what version number do you see next to post-voting?
My test-passed, up-to-date one is: 5ea4dccf
**Edit:** I corrected the page address 🙂
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [December 9, 2022, 1:49pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/10 "2022-12-09T13:49:48Z")
> [@gmoirod](#):
>
> > [@JammyDodger](#):
> >
> > If you add the new `discourse-topic-voting` you should be able to have both again.
>
> Ok I am going for a test right now
Seems ok to have topic-voting now.
> [@JammyDodger](#):
>
> When you check your `/plugins` page, what version number do you see next to post-voting?
I do not have a `/plugins` page 🤔
But on the `/admin/upgrade` page I got :
1. Do not have post-voting
2. q&a shows without green check
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [December 9, 2022, 2:52pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/11 "2022-12-09T14:52:32Z")
It looks like you’re locked at [this commit](https://github.com/discourse/discourse-post-voting/commit/50d8ea4144a24ee78c6559746d3fc48443d49e21) from September when it was still question-answer:
Are you up-to-date with the Stable version? What version are you currently on?
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [December 9, 2022, 3:01pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/12 "2022-12-09T15:01:25Z")
> [@JammyDodger](#):
>
> Are you up-to-date with the Stable version? What version are you currently on?
It seems good.
* * *
* * *
New problem…
1. I removed post-voting and topic-voting and rebuilt app to try starting from something clean (q&a is not listed too since many attempts) : ok, no more plugins
2. I brought back post-voting and topic-voting and now rebuild fails…
> **Summary**
>
> ```bash
> I, [2022-12-09T14:27:32.724323 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile'
> Failed to update 'Discourse Loading Slider': Timeout::Error
> rake aborted!
> Timeout::Error: Timeout::Error
> /var/www/discourse/lib/final_destination/resolver.rb:28:in `block in lookup'
> /var/www/discourse/lib/final_destination/resolver.rb:7:in `synchronize'
> /var/www/discourse/lib/final_destination/resolver.rb:7:in `lookup'
> /var/www/discourse/lib/final_destination/ssrf_detector.rb:84:in `lookup_ips'
> /var/www/discourse/lib/final_destination/ssrf_detector.rb:64:in `lookup_and_filter_ips'
> /var/www/discourse/lib/theme_store/git_importer.rb:139:in `block in clone_http!'
> /var/www/discourse/lib/theme_store/git_importer.rb:131:in `each'
> /var/www/discourse/lib/theme_store/git_importer.rb:131:in `clone_http!'
> /var/www/discourse/lib/theme_store/git_importer.rb:93:in `clone!'
> /var/www/discourse/lib/theme_store/git_importer.rb:18:in `import!'
> /var/www/discourse/app/models/remote_theme.rb:126:in `update_remote_version'
> /var/www/discourse/lib/tasks/themes.rake:62:in `block in update_themes'
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/relation/batches.rb:71:in `block (2 levels) in find_each'
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/relation/batches.rb:71:in `each'
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/relation/batches.rb:71:in `block in find_each'
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/relation/batches.rb:138:in `block in find_in_batches'
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/relation/batches.rb:245:in `block in in_batches'
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/relation/batches.rb:229:in `loop'
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/relation/batches.rb:229:in `in_batches'
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/relation/batches.rb:137:in `find_in_batches'
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/activerecord-6.1.6.1/lib/active_record/relation/batches.rb:70:in `find_each'
> /var/www/discourse/lib/tasks/themes.rake:56:in `update_themes'
> /var/www/discourse/lib/tasks/themes.rake:87:in `block (2 levels) in '
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.0/lib/rails_multisite/connection_management.rb:80:in `with_connection'
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.0/lib/rails_multisite/connection_management.rb:90:in `each_connection'
> /var/www/discourse/lib/tasks/themes.rake:86:in `block in '
> /var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in `'
> /usr/local/bin/bundle:25:in `load'
> /usr/local/bin/bundle:25:in `'
> Tasks: TOP => themes:update
> (See full trace by running task with --trace)
> I, [2022-12-09T14:27:49.987988 #1] INFO -- : Checking 'Modern Category + Group Boxes' for 'default'... up to date
> Checking 'Dark-Light Toggle' for 'default'... updating from cd221006 to 3f72c88f
> Checking 'Discourse Loading Slider' for 'default'...
>
> FAILED
> --------------------
>
> ```
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [December 9, 2022, 4:56pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/13 "2022-12-09T16:56:19Z")
Rebuild again and it passed.
So the last problem with `'Discourse Loading Slider'` was just a glitch.
Forget that.
My main problem is that q&a remains instead of post-voting…
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [December 9, 2022, 5:42pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/14 "2022-12-09T17:42:30Z")
I think this may be a consequence of the build you’re using and compatibility. If you look at what should be `discourse-topic-voting` it’s showing on your page as `discourse-voting` still as well.
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [December 9, 2022, 5:44pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/15 "2022-12-09T17:44:44Z")
So you mean I should use ‘tests-passed’ version of discourse ?
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [December 9, 2022, 5:45pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/16 "2022-12-09T17:45:11Z")
If you want the latest versions of things. 🙂
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [December 9, 2022, 5:47pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/17 "2022-12-09T17:47:33Z")
I would prefer a ‘working’ versions of things actually 😅
I know there is topic about version to use pretending ‘tests-passed’ is good-to-go.
But I am a kind of a ‘debian guy’ you know… Stability for production !
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [December 9, 2022, 5:50pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/18 "2022-12-09T17:50:28Z")
I think that’s a fine choice too. 👍 🙂 The flipside is that you’ll need to wait for Version 3.0 to launch in the new year before you can get these latest updates working with Stable.
---
### Author:  [@gmoirod](https://meta.discourse.org/u/gmoirod)
#### Post date: [December 9, 2022, 5:56pm UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/19 "2022-12-09T17:56:14Z")
Okay…
This is a bit disappointing that plugin management do not offer a way to follow a given git ref.
And that plugins follow Discourse lifecycle.
So that you can globally follow ‘stable’ for discourse AND plugins.
Actually each rebuild, or plugin adoption, feels like a roulette wheel.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [December 10, 2022, 7:56am UTC](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372/20 "2022-12-10T07:56:56Z")
I’m afraid my knowledge about the Stable branch is fairly limited, but I think it’s geared more towards not changing things very often. So I would think adding new plugins and extras outside of a Stable release window would be counter-intuitive to that?
It’s also worth saying that most Discourse sites use tests-passed and generally don’t have any notable issues. Even following test-passed doesn’t mean you need to update every day though and be on the _very_ latest version, so it’s not as changeable as you may think. You would manually have to press the update button from your `/upgrade` page, or perform a rebuild, to pull those changes into your site.
Managed hosting also makes this process easier too as an alternative, as they’ll handle all of the technical stuff and let you concentrate on your community. 👍
[Next page](https://meta.discourse.org/t/plugin-post-voting-conflicts-with-previous-question-answer-plugin/248372.md?page=2)