discourse/app/models/theme_site_setting.rb
Martin Brennan 19af83d39e
FEATURE: Themeable site settings (#32233)
This commit introduces the concept of themeable site settings,
which is a new tool for theme authors that lives alongside theme
modifiers and theme settings. Here is a quick summary:

* Theme settings - These are custom settings used to control UI and functionality within your theme or component and provide configuration options. These cannot change core Discourse functionality.
* Theme modifiers - Allows a theme or a component to modify selected server-side functionality of core Discourse as an alternative to building a plugin.
* Themeable site settings (new) - Allows a theme (not components) to override a small subset of core site settings, which generally control parts of the UI and other minor functionality. This allows themes to have a greater control over the full site experience.

Themeable site settings will be shown for all themes, whether the theme
changes
the value or not, and have a similar UI to custom theme settings.

We are also introducing a new page at
`/admin/config/theme-site-settings` that
allows admins to see all possible themeable site settings, and which
themes
are changing the value from the default.

### Configuration

Theme authors can configure initial values themeable site settings using
a section in the `about.json` file like so:

```json
"theme_site_settings": {
  "search_experience": "search_field"
}
```

These values will not change when the theme updates, because we cannot
know if admins have manually changed them.

### Limitations

Themeable site settings are only really intended to control elements of
the UI, and when retrieving their value we require a theme ID, so these
limitations apply:

- Themeable site settings cannot be used in Sidekiq jobs
- Themeable site settings cannot be used in markdown rules
- Themeable site settings will be cached separately to client site
settings using theme ID as a key
- Themeable site settings will override keys on the `siteSettings`
service on the client using the application preloader
- `SiteSetting.client_settings_json` will not include themeable site
settings, instead you can call `SiteSetting.theme_site_settings_json`
with a theme ID

### Initial settings

There are only two site settings that will be themeable to begin with:

* `enable_welcome_banner`
* `search_experience`

And our new Horizon theme will take advantage of both. Over time, more
settings that control elements of the UI will be exposed this way.
2025-07-16 11:00:21 +10:00

123 lines
4.2 KiB
Ruby
Vendored

# frozen_string_literal: true
# Copies the same schema as SiteSetting, since the values and
# data types are identical. This table is used as a way for themes
# to overrride specific site settings that we make available in
# core based on the `themeable` designation on a site setting.
#
# Creation, updating, and deletion of theme site settings is done
# via the `Themes::ThemeSiteSettingManager` service.
class ThemeSiteSetting < ActiveRecord::Base
belongs_to :theme
# Gets a list of themes that have theme site setting records
# and the associated values for those settings, where the
# value is different from the default site setting value.
#
# @return [Array<Hash>] an array of hashes where each hash contains:
# - :theme_id [Integer] the ID of the theme
# - :theme_name [String] the name of the theme
# - :setting_name [Symbol] the name of the setting
# - :value [String] the value of the setting
# - :data_type [Integer] the data type of the setting
def self.themes_with_overridden_settings
sql = <<~SQL
SELECT theme.id AS theme_id, theme.name AS theme_name,
tss.name AS setting_name, tss.value, tss.data_type
FROM themes theme
INNER JOIN theme_site_settings tss ON theme.id = tss.theme_id
WHERE theme.component = false AND tss.name IN (:setting_names)
ORDER BY tss.name, theme.name
SQL
DB
.query(sql, setting_names: SiteSetting.themeable_site_settings)
.each { |row| row.setting_name = row.setting_name.to_sym }
.select do |row|
# Do not consider this as an "overridden" setting if the value
# is the same as the default site setting value.
row.value !=
SiteSetting
.type_supervisor
.to_db_value(row.setting_name, SiteSetting.defaults[row.setting_name])
.first
end
.each do |row|
row.value =
SiteSetting.type_supervisor.to_rb_value(row.setting_name, row.value, row.data_type)
end
end
def self.can_access_db?
!GlobalSetting.skip_redis? && !GlobalSetting.skip_db? &&
ActiveRecord::Base.connection.table_exists?(self.table_name)
end
# Generates a map of theme IDs to their site setting values. When
# there is no theme site setting for a given theme, the default
# site setting value is used.
#
# @return [Hash] a map where keys are theme IDs and values are hashes:
#
# {
# 123 => {
# setting_name_1 => value_1,
# setting_name_2 => value_2,
# ...
# }
# }
def self.generate_theme_map
# Similar to what SiteSettings::DbProvider and SiteSettings::LocalProcessProvider do
# for their #all method, we can't try to load settings if the DB is not available,
# since this method is called within SiteSetting.refresh! which is called on boot.
return {} if !can_access_db?
theme_site_setting_values_map = {}
Theme
.includes(:theme_site_settings)
.not_components
.each do |theme|
SiteSetting.themeable_site_settings.each do |setting_name|
setting = theme.theme_site_settings.find { |s| s.name == setting_name.to_s }
value =
if setting.nil?
SiteSetting.defaults[setting_name]
else
SiteSetting.type_supervisor.to_rb_value(
setting.name.to_sym,
setting.value,
setting.data_type,
)
end
theme_site_setting_values_map[theme.id] ||= {}
theme_site_setting_values_map[theme.id][setting_name] = value
end
end
theme_site_setting_values_map
end
def setting_rb_value
SiteSetting.type_supervisor.to_rb_value(self.name, self.value, self.data_type)
end
end
# == Schema Information
#
# Table name: theme_site_settings
#
# id :bigint not null, primary key
# theme_id :integer not null
# name :string not null
# data_type :integer not null
# value :text
# created_at :datetime not null
# updated_at :datetime not null
#
# Indexes
#
# index_theme_site_settings_on_theme_id (theme_id)
# index_theme_site_settings_on_theme_id_and_name (theme_id,name) UNIQUE
#