mirror of
https://github.com/discourse/discourse.git
synced 2026-08-06 13:08:40 +08:00
## Summary The admin upcoming-changes toggle endpoint accepted any public zero-argument SiteSetting method as a valid setting name. The fix restricts eligibility to registered upcoming-change metadata by checking UpcomingChanges.exists? instead of SiteSetting.respond_to?, preventing invocation of non-setting methods like notify_changed!. ## Source - Patch Triage: https://patch.discourse.org/patch-triage/1508 Co-authored-by: discourse-patch-triage <272280883+discourse-patch-triage[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| about_controller_spec.rb | ||
| category_management_controller_spec.rb | ||
| color_palettes_controller_spec.rb | ||
| customize_controller_spec.rb | ||
| discourse_id_controller_spec.rb | ||
| fonts_controller_spec.rb | ||
| logo_controller_spec.rb | ||
| site_settings_controller_spec.rb | ||
| upcoming_changes_controller_spec.rb | ||
| welcome_banner_controller_spec.rb | ||