@jord8on you have it here
Sorry I missed this, and THANK YOU for the direct link.
@angus just a thought - Several other plugins offer a link in the main description of the plugin, to “see the plugin in action” Any chance you could add that link into the main topic description, here? Just a thought.
Thanks for the note. I’ve added an example link in the first post
Angus, you are a great Plugin Author. I have been following your posts.
I found a problem, this plugin is not compatible with some themes.
Or equally you might say that that Theme does not consider this plugin?
Is that Theme overriding a template? If so that may be part of the issue. The plugins we support target the base install and if a Theme works that’s a pleasant benefit. I would extract the elements of that Theme that work and create your own.
I’m now maintaner of this plugin and here is a quick update regarding our update policy:
Pavilion will focus on ensuring compatibility of this plugin with Discourse Core
tests-passed branch during the first 5 days of every month.
Any bugs which arise because of an incompatibility will be addressed asap during this ‘supported period’, preferably by the 7th day. Low severity bugs or Beta features may be kept out of supported scope.
Consider testing your update on your own staging server built from a back-up of your production site. You can switch this server off for the rest of the month so you don’t get charged for up-time. Use this opportunity to test out all basic functionality to identify any issues with plugins. Report all critical and high issues asap on the relevant plugin topic.
Aim to update your Production Discourse instance in the first 5 days of every month. You will get more focussed support from the Pavilion team on any issues with their plugins during this period.
You update your Production server outside of the first 5 days of the month at your own risk.
Major code rewrite is coming. You can follow it here:
Pardon the confusion: I’m reading I update by the 5th day. Are you saying additional bug fixes will be released through the seventh day?
This is a policy that covers all Pavilion plugins.
Sorry for the confusion. What we are saying is any high or critical severity issue identified by the fifth day will be rectified hopefully by the 7th. Then you can update the plugin ONLY and things should work again. The main takeaway is that there may be a small lag involved before a fix is issued, hence the difference in those two numbers (5 versus 7).
If the bug is SO bad that you have to remove the plugin, obviously that will require a rebuild to replace it and Discourse will get updated too. We’ll deal with those occasions when they crop up. Hopefully those will be very unusual.
It seems you’re trying to install it as a theme. This is a plugin, not a theme. Please follow this guide:
It is so awesome to hear! Some questions if you may:
- Technically speaking, how should I run the tests branch from production?
- You said that this plugin will be rewritten. Is there a plan what is going to change and what is going to be added?
Thank you very much!
- It’s optional. We have our own staging site and you can test the plugin here: try.thepavilion.io
However, you could setup your own staging site and test the plugin there if you’d like to.
- More like code refactor. No new feature has been added.
Any plans for future? Saw a post about it a while ago on Pavilion.
Can you please assist, I am getting 502 Bad Gateway error after adding below plugin hook.
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/paviliondev/discourse-question-answer.git
Have you tried to comment this line and rebuild?
how can i default sort all posts on a topic to have the most voted/most liked posts on top, like stackoverflow does? @angus
After removing the plugin the site is back to normal, how to fix this issue ? is it not compatible with latest discourse version ?
This is the first time you install any custom plugin? Just tested locally and everything works fine. This is isolated case unless someone else report the same issue.
502 usually means the frontend (Nginx) is running but the backend (Rails server/Unicorn?) is not.
What’s your app.yml looks like?
other plugins are working fine.
## Plugins go here ## see https://meta.discourse.org/t/19157 for details hooks: after_code: - exec: cd: $home/plugins cmd: - git clone https://github.com/discourse/docker_manager.git - git clone https://github.com/discourse/discourse-sitemap.git - git clone https://github.com/pmusaraj/discourse-sidebar-blocks.git # - git clone https://github.com/paviliondev/discourse-question-answer.git
I really like this suggestion. Will developers consider adding these features to plugins?