Make it easier for admins to enable SDG processes

In order to ensure compatibility with existing CONSUL installations, we
disabled all settings related to SDG. However, we also made it much
harder to enable SDG globally on the site, since administrators first
had to enable the SDG feature and then enable it for each process.

Most people will expect SDG is enabled for all processes once they
enable the SDG feature, so that's what we're doing. They can of course
disable specific processes should they wish to do so.
This commit is contained in:
Javi Martín
2021-04-21 18:31:11 +02:00
parent 24a4c46465
commit 32a61f826c
2 changed files with 5 additions and 10 deletions

View File

@@ -186,11 +186,11 @@ class Setting < ApplicationRecord
"remote_census.response.name": "",
"remote_census.response.surname": "",
"remote_census.response.valid": "",
"sdg.process.debates": false,
"sdg.process.proposals": false,
"sdg.process.polls": false,
"sdg.process.budgets": false,
"sdg.process.legislation": false
"sdg.process.debates": true,
"sdg.process.proposals": true,
"sdg.process.polls": true,
"sdg.process.budgets": true,
"sdg.process.legislation": true
}
end

View File

@@ -16,11 +16,6 @@ section "Creating Settings" do
"org_name": "CONSUL",
"proposal_code_prefix": "MAD",
"proposal_notification_minimum_interval_in_days": 0,
"sdg.process.debates": "true",
"sdg.process.proposals": "true",
"sdg.process.polls": "true",
"sdg.process.budgets": "true",
"sdg.process.legislation": "true",
"telegram_handle": "CONSUL",
"twitter_handle": "@consul_dev",
"twitter_hashtag": "#consul_dev",