A user, madmath03, encountered a startup error related to the Discourse Styleguide plugin, specifically an SCSS variable error: $danger-low-mid undefined. simon suggested the issue might stem from using Bitnami’s outdated Discourse version, though madmath03 noted they were on Discourse 2.5.3. sam clarified that the Styleguide is now built into Discourse core and not a separate plugin, and marked the issue as unsupported-install due to Bitnami’s non-standard setup. madmath03 acknowledged the redundancy of installing the plugin and suggested the GitHub repo should reflect its deprecation. codinghorror reminded the user that multiple support topics for unsupported installs consume limited community resources. madmath03 clarified they were reporting perceived bugs, not seeking install help, and expressed willingness to contribute to improving Discourse. Stephen reiterated that no free support is offered for third-party installs, even for official plugins, because of unpredictable side effects. madmath03 noted the Styleguide is an official plugin, but Stephen emphasized the unsupported environment invalidates support. codinghorror explained policies exist to enable free support for standard installs, and non-standard setups are “hard mode” beyond their scope. Finally, j.jaffeux confirmed the plugin repo has been blanked out to avoid confusion.
It is possible that there is a bug in the plugin, but it looks like your Discourse site is installed on Bitnami. The issue you are finding could be related to Bitnami’s using an old version of Discourse.
I just installed the styleguide plugin on my up to date Discourse site without any issues.
Styleguide is now shipped with core, not in a separate plugin repo
In that case, this has nothing to do with Bitnami.
It’s just I should not have requested install of this plugin since it’s already there by default (unless I misunderstood).
If that’s the case then, the GitHub repo should defintely mention it.
So far, by my count, you’ve opened 3 support topics about an unsupported install.
Perhaps now you can understand why we have a standard way of installing and supporting Discourse. Our time is not free, just as I’m sure your time is not free.
Perhaps now you can understand why we have a standard way of installing and supporting Discourse. Our time is not free, just as I’m sure your time is not free.
@codinghorror I opened those tickets because I believed those were bugs in the commands or plugins themselves.
I never asked for help regarding the install as I know you will NOT support it (I directly open issues to Bitnami for that).
Of course I understand your point, but I’m sure you can also understand that unfortunately the standard way you provide does not answer all needs. Though I would love to help improve it
I’m not trying to make you lose time, I just wish to help by reporting what I believe might be issues in Discourse itself.
To be clear we can’t offer any free support for any aspect of a third party installation, including plugins.
Third party packages can have all kinds of unintended and unpredictable side effects. As we can’t rule those out we can’t work through such issues. That’s just a step too far for the free assistance provided here.
If you insist on using something other than the standard install your only support options are via the package maintainer, or via the Marketplace.
I don’t mean to come across as rude, all Discourse instances are a net positive to the world whether we host them or not.. but.. we have the policies we have (e.g. a standard install) so that we can support the open source installs effectively “for free”.
If you sign up for “hard mode” with a custom install, that’s not really our responsibility, and the resulting topics are more of a distraction than anything else.