bug is caused by next line:
/usr/share/redmine/app/models/setting.rb,166
setting ||= new(:name => name, :value => @@available_settings[name]['default']) if @@available_settings.has_key? name
new (:name => name, :value =>> ...) depends on correct order of params in hash, i.e. (name,value) , because Settings.value= is depended on Settings..name attribute to get 'serialized' attr from @@available_settings
but last security change in hash processing in ruby is mixed some level of randomness (process PID?) in hash function, so order of hash params sometimes is reversed
bug is caused by next line: redmine/ app/models/ setting. rb,166 settings[ name][' default' ]) if @@available_ settings. has_key? name
/usr/share/
setting ||= new(:name => name, :value => @@available_
new (:name => name, :value =>> ...) depends on correct order of params in hash, i.e. (name,value) , because Settings.value= is depended on Settings..name attribute to get 'serialized' attr from @@available_ settings
but last security change in hash processing in ruby is mixed some level of randomness (process PID?) in hash function, so order of hash params sometimes is reversed