discourse/plugins/poll/config/settings.yml

plugins:
  poll_enabled:
    default: true
    client: true
  poll_maximum_options:
    default: 20
    min: 2
    max: 100
    client: true
  poll_edit_window_mins:
    default: 5
    min: 0
  poll_minimum_trust_level_to_create:
    default: 1
    client: true
    enum: 'TrustLevelSetting'
  poll_export_data_explorer_query_id:
    default: -16
    min: -9999
    client: true
- FEATURE: revamped poll plugin - add User.staff scope - inject MessageBus into Ember views (so it can be used by the poll plugin) - REFACTOR: use more accurate is_first_post? method instead of post_number == 1 - FEATURE: add support for JSON-typed custom fields - FEATURE: allow plugins to add validation - FEATURE: add post_custom_fields to PostSerializer - FEATURE: allow plugins to whitelist post_custom_fields - FIX: don't bump when post did not save successfully - FEATURE: polls are supported in any post - FEATURE: allow for multiple polls in the same post - FEATURE: multiple choice polls - FEATURE: rating polls - FEATURE: new dialect allowing users to preview polls in the composer 2015-04-23 13:33:29 -04:00			`plugins:`
			`poll_enabled:`
			`default: true`
FIX: disable poll dialect when poll plugin is disabled 2015-09-14 14:11:03 -04:00			`client: true`
FEATURE: new 'poll_maximum_options' site setting to limit the number of options in a poll 2015-05-01 10:44:51 -04:00			`poll_maximum_options:`
changed default 'poll maximum options' to 20 2015-05-19 08:33:27 -04:00			`default: 20`
REFACTOR: use tables instead of custom fields for polls (#6359) Co-authored-by: Guo Xiang Tan <tgx_world@hotmail.com> 2018-11-19 08:50:00 -05:00			`min: 2`
			`max: 100`
Expose poll_maximum_options to client At present this doesn't actually seem to be exposed to the client. I discovered this by accident whilst trying to write my own plugin: https://github.com/discourse/discourse/blob/7b6d6b76eb3b7dbf1982c382a1f0e981e7ff8eee/app/models/site_setting.rb#L17-L18 2015-07-19 16:41:14 -04:00			`client: true`
Extract polls edit window to a site settings. 2016-08-10 03:15:29 -04:00			`poll_edit_window_mins:`
			`default: 5`
REFACTOR: use tables instead of custom fields for polls (#6359) Co-authored-by: Guo Xiang Tan <tgx_world@hotmail.com> 2018-11-19 08:50:00 -05:00			`min: 0`
FEATURE: introduces minimum trust level for polls (#5391) * FEATURE: introduces minimum trust level for polls This commit makes `poll_enabled` less misleading and introduces `poll_minimum_trust_level_to_create`. If poll are enabled they will always be cooked, and if you have the required trust level you can create polls. As a side effect, it also fixes a bug where rebaking a post created by staff member when `poll_enabled=false` would end up not cooking it. It also adds more tests to ensure settings are respected. * admins should be whitelisted * checks for admin in post validation * test for >= instead of == trust level 2017-12-04 08:47:11 -05:00			`poll_minimum_trust_level_to_create:`
			`default: 1`
			`client: true`
			`enum: 'TrustLevelSetting'`
FEATURE: Add export poll button (#8370) This PR aims to make poll results easily exportable to staff in a CSV format, so they can be analyzed in external software. It also makes the export data easily customizable by allowing users to leverage any data explorer query to generate the report. By default, we use a query that ships with data explorer, but user can change the ID in settings or use 0 to disable this feature. One potential upgrade is using the recent work that allows arbitrary group to run data explorer and allow all the groups with access to the configured query to also export polls, but that can be added later. Co-Authored-By: Joffrey JAFFEUX <j.jaffeux@gmail.com> 2019-11-22 14:06:39 -05:00			`poll_export_data_explorer_query_id:`
			`default: -16`
			`min: -9999`
			`client: true`