discourse/plugins/poll/config/settings.yml

plugins:
  poll_enabled:
    default: true
    client: true
  poll_maximum_options:
    default: 20
    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 12:33:29 -05:00			`plugins:`
			`poll_enabled:`
			`default: true`
FIX: disable poll dialect when poll plugin is disabled 2015-09-14 13:11:03 -05:00			`client: true`
FEATURE: new 'poll_maximum_options' site setting to limit the number of options in a poll 2015-05-01 09:44:51 -05:00			`poll_maximum_options:`
changed default 'poll maximum options' to 20 2015-05-19 07:33:27 -05:00			`default: 20`
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 15:41:14 -05:00			`client: true`