As of yesterday’s update (of my hosted server at https://doomemacs.discourse.group ), none of my custom CSS is applied. Changes to my theme(s) or components’ CSS have no effect (though changes their <head> or other HTML sections work fine). There is one suspect link tag pointing to an empty styleshe…

The fix is now merged in core and your site is deployed @hlissner . Note that I disabled two theme components: the one with custom styles (which you can enable) and discourse-theme-category-homepage, which needs to be updated upstream before you can enable it. More details on that in Enhanced categor…

I am not certain, but I think you might be hitting this change Restrict editing of remote themes Looks like this is incorrect :smiley:

Hi @hlissner , I am working on a fix for this, a recent upgrade to core broke the theme component on your instance. I should have a fix shortly.

Thank you! The stylesheets now correctly load, however, the SCSS color variables don’t appear to inherit my theme’s color scheme. e.g. $secondary yields its default value, #ffffff, instead of #282c34. Is this perhaps another regression from e8b8272 ?

Yes, it is another regression. It’s a bit of a tricky fix… and for the vast majority of color variables, theme components should be using CSS custom properties. You can look at this guide Updating themes and plugins to support automatic dark mode , for an overview and some examples on how to add cust…

I’ve done so where I can, but without access to these variables I cannot transform colors based off my active scheme. e.g. $primary-low: dark-light-choose(darken($secondary, 12%), lighten($secondary, 10%)); :root { --primary-low: #{$primary-low}; } Is there a better way around this? I could a…

Yes, that makes sense, did you try adding that SCSS above to a new file in common/color_definitions.scss? It should just work if you add it there. (There is also a tab in the UI for that special stylesheet.)

Was about to try exactly that, then the discourse went down with a The software powering this discussion forum encountered an unexpected problem, haha.

You can access the site via /safe-mode, that disables themes and components and then you can see what happened. This is yet another regression though, those SCSS errors should not blow up the whole site, I’ll certainly fix that in the next few days.

That worked! The color variables are properly set in color_definitions.scss's scope. Only trouble is I can’t import other stylesheets from it. e.g. // scss/globals.scss $foo: "#000000"; // color_definitions.scss @import "globals"; :root { --foo: #{$foo}; } Yields this in the Discourse error logs: …

Yes, I have a PR up to fix the import issue, should be merged by tomorrow. FIX: Improve SCSS handling in components master ← more-scss-theme-fixes merged 01:51PM - 04 Feb 21 UTC (UTC) …

我的 Discourse 未应用自定义 CSS

支持

rorycb (Rory Craig-Barnes) 2021 年2 月 3 日 11:21 2

~~我不确定，但我想你可能遇到了这个变更 https://meta.discourse.org/t/restrict-editing-of-remote-themes/170051~~
看来这是不正确的

话题		回复	浏览量
Referencing Discourse theme color variables in custom theme component? Support css	4	106	2025 年4 月 20 日
Use Discourse Core Variables in your Theme Developer Guides how-to , theme-guides	0	12039	2018 年1 月 9 日
Theme Developer Tutorial: 3. CSS in Themes Developer Guides	5	649	2025 年3 月 18 日
Feature proposal: Import user-defined SCSS files UX	4	1327	2018 年8 月 1 日
Color palettes loading incorrectly with 2.7.0.beta5 Bug	7	1226	2021 年3 月 18 日

我的 Discourse 未应用自定义 CSS

相关话题