David Taylor c687e2b921 FIX: Use `saved_change_to_value?` in site_setting_saved event ... Since Rails 5.2, the behavior of `attribute_changed?` inside `after_save` callbacks has changed, so we need to use `saved_change_to_attribute` instead. The site setting local_process_provider in test mode was covering up the issue.		2019-04-17 10:07:00 -04:00
..
db_provider.rb	DEV: remove all calls to SqlBuilder use DB.build instead	2018-06-20 17:53:49 +10:00
defaults_provider.rb	FIX: "false" didn't work as locale_default	2018-09-11 13:42:10 +02:00
deprecated_settings.rb	REFACTOR: Rename site settings to make them less confusing	2019-03-14 13:40:14 +01:00
local_process_provider.rb	FIX: Use `saved_change_to_value?` in site_setting_saved event	2019-04-17 10:07:00 -04:00
type_supervisor.rb	FEATURE: Allow categories to be prioritized/deprioritized in search. (#7209)	2019-03-25 10:59:55 +08:00
validations.rb	FIX: don't raise error if s3 set via global setting	2019-02-01 14:17:10 +05:30
yaml_loader.rb	FEATURE: Upload Site Settings. (#6573)	2018-11-14 15:03:02 +08:00