Hi all,
Just installed the latest versions of each of these plugins on Discourse 3.4.6 and got these errors
These errors completely crash Discourse and can only see a blank page.
Hi all,
Just installed the latest versions of each of these plugins on Discourse 3.4.6 and got these errors
These errors completely crash Discourse and can only see a blank page.
Bummer!
Maybe update Discourse then try again?
Discourse is at 3.5.0.beta8-dev
For the tests-passed
branch, but if youāre tracking stable
then I think 3.4.6 is right (3.4.6: Security fix release)
There should be a compatibility file that ensures it doesnāt pull in anything from the plugin the main site isnāt ready for, but maybe thatās gone a little awry for this last one. Hopefully someone can identify what the issue is and smooth it out.
True enough but Discourse dev approach is so rock solid I stay with tests-passed and have nearly zero issues.
Any chance @HandSpy_v3 is not using the official plugin? His OP references two plugins, like we used to have.
Iām using the Official plugins, just added in my .yml under
hooks:
after_code:
- exec:
cd: $home/plugins
cmd:
...
- git clone https://github.com/discourse/discourse-topic-voting.git
- git clone https://github.com/discourse/discourse-post-voting.git
Brain dead, sorry. Two plugins, not one.
@HandSpy_v3 You might change to tests-passed in app.yml per Discourse recommendation.
params:
db_default_text_search_config: "pg_catalog.english"
## Set db_shared_buffers to a max of 25% of the total memory.
## will be set automatically by bootstrap based on detected RAM, or you can override
db_shared_buffers: "256MB"
## can improve sorting performance, but adds memory usage per-connection
#db_work_mem: "40MB"
## Which Git revision should this container use? (default: tests-passed)
#version: tests-passed
Yes, works in beta.
Generally we try to add a compatibility file into plugins to avoid situations like this, will alert the team.
Workaround is to check out an earlier version of the plugin on stable.