mirror of
https://github.com/discourse/discourse.git
synced 2026-08-04 10:39:43 +08:00
3e012af58ePreviously, the duplicate topic title check compared new titles against every topic on the site regardless of visibility: users were blocked by titles in categories they couldn't see or unlisted topics they couldn't find, the bare "Title has already been used" error gave no way to locate the conflict (and doubled as an existence oracle for hidden titles), and the behavior was controlled by two entangled boolean settings. This change scopes the check to the destination category plus whatever the acting user can actually see, links the conflicting topic in the error — safe by construction, since being blocked now implies being able to see it: > This title has already been used by [another topic](). It also consolidates the two booleans into a single `duplicate_topic_titles` enum (`disallowed` / `allowed_across_categories` / `allowed`), with existing values migrated and the old names kept as hidden deprecated aliases that admin search still resolves. Reported in https://meta.discourse.org/t/title-has-already-been-used-in-a-secure-category/123047 Note for self-hosters: env-provided settings can't be migrated — `DISCOURSE_ALLOW_DUPLICATE_TOPIC_TITLES=true` configs need to switch to `DISCOURSE_DUPLICATE_TOPIC_TITLES=allowed`.
19 lines
406 B
Ruby
Vendored
19 lines
406 B
Ruby
Vendored
# frozen_string_literal: true
|
|
|
|
class EnumSiteSetting
|
|
def self.translate_names?
|
|
false
|
|
end
|
|
|
|
def self.wrap_values!
|
|
value_class = Class.new(String)
|
|
|
|
values.each do |entry|
|
|
value = entry[:value].to_s
|
|
value_class.define_method("#{value}?") { self == value }
|
|
end
|
|
|
|
const_set(:Value, value_class)
|
|
define_singleton_method(:wrap) { |value| self::Value.new(value) }
|
|
end
|
|
end
|
