Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/web/templates/settings/organization_settings_admin...

202 lines
11 KiB
Handlebars
Raw Normal View History

settings: Add data-name entries for administration pages.
2017-02-09 08:10:58 +01:00
<div id="organization-settings" data-name="organization-settings" class="settings-section">
settings: Remove form-horizontal class from settings template. This commit removes form-horizontal class from form elements in user profile, org profile, org settings and org permission pages. We also add margin-bottom property for select elements in this page. We can safely remove this class since vertical-align property is already present due to other bootstrap CSS. And margin-bottom property for checkbox inputs are added by bootstrap and for text inputs it is handled in app_components.css. The display property for inputs other than checkbox and select elements is set to inline-block by other bootstrap CSS. For checkbox-type inputs browser sets display property to inline-block but it is eventually computed to "block" as the float property is set to left and so it is not required to set display property for checkbox type inputs. We have added CSS for select elements in settings.css which can be removed later once we remove bootstrap for select elements completely.
2023-01-10 11:33:08 +01:00
<form class="admin-realm-form org-settings-form">
Restructure organization settings and permissions. This restructures organization settings and permissions to be more accurately grouped and for the permissions page to not be too long. CHANGES: PROFILE: (this was split out) organization-profile-admin.handlebars: form #1: name description (SUBMIT) avatar: (UPLOAD) (DELETE) SETTINGS: organization-settings-admin.handlebars: language (mostly untouched) message editing: time limit/history/retention message feed: mandatory-topics preview images preview websites PERMISSIONS: organization-permissions-admin.handlebars (mostly stuff was removed) Joining: restrict domains require invite User Identity: name changes email changes Streams/Emoji: creating streams: waiting period (ADDED) adding emojis (SUBMIT) for whole panel The profile group (name, description, avatar) were split into a new page that did not previously exist, and the permissions was stripped of message settings (message editing, message feed), but keeping the "waiting period" input and putting it in the "Streams & custom emoji" section. Fixes: #5844.
2017-08-18 01:23:55 +02:00
settings: Rename "org-subsection-parent" class to "settings-subsection-parent". This commit renames the "org-subsection-parent" class used for organization settings subsections to "settings-subsection-parent" such that we can use same for the stream settings and avoid duplicating code for handling save-discard widget which will be added in future.
2022-11-03 13:18:42 +01:00
<div id="org-notifications" class="settings-subsection-parent">
org settings: Reorder the major sections of Organization settings.
2019-02-07 22:40:51 +01:00
<div class="subsection-header">
org-settings: Update "Notifications" header and subheaders. Updates header "Notifications" to "Automated messages and emails". Updates these subheaders in that section: - "New stream notifications" to "New stream announcements" - "New user notifications" to "New user announcements" - "Notifications language" to "Language for automated messages and invitation emails". Co-authored by: Lauryn Menard <lauryn@zulip.com>
2022-06-27 22:34:52 +02:00
<h3>{{t "Automated messages and emails" }}</h3>
templates: Use upstream Handlebars partials syntax. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-11 04:05:28 +02:00
{{> settings_save_discard_widget section_name="notifications" }}
org settings: Reorder the major sections of Organization settings.
2019-02-07 22:40:51 +01:00
</div>
<div class="inline-block organization-settings-parent">
settings: Reorder settings in "Automated messages and emails" section. This commit reorders the settings in "Automated messages and emails" subsection such that most useful options are at top and automated messages and email settings are grouped together as proposed in #25339.
2023-05-02 19:10:43 +02:00
<div class="realm_default_language">
{{> language_selection_widget
section_name="realm_default_language"
setting_value=realm_default_language_name
language_code=realm_default_language_code
section_title=admin_settings_label.realm_default_language
help_link_widget_link="/help/configure-organization-language"}}
</div>
settings_org: Migrate dropdowns to new DropdownWidget. This also moves [Disabled] button inside the dropdown.
2023-07-19 16:14:00 +02:00
{{> ../dropdown_widget_with_label
settings: Rename notifications_stream to new_stream_announce..._stream. This commit renames the realm-level setting 'notifications_stream' to 'new_stream_announcements_stream'. The new name reflects better what the setting does.
2024-02-07 12:13:02 +01:00
widget_name="realm_new_stream_announcements_stream_id"
label=admin_settings_label.realm_new_stream_announcements_stream
settings_org: Migrate dropdowns to new DropdownWidget. This also moves [Disabled] button inside the dropdown.
2023-07-19 16:14:00 +02:00
value_type="number"}}
settings: Reorder settings in "Automated messages and emails" section. This commit reorders the settings in "Automated messages and emails" subsection such that most useful options are at top and automated messages and email settings are grouped together as proposed in #25339.
2023-05-02 19:10:43 +02:00
settings_org: Migrate dropdowns to new DropdownWidget. This also moves [Disabled] button inside the dropdown.
2023-07-19 16:14:00 +02:00
{{> ../dropdown_widget_with_label
settings: Rename signup_notifications_stream realm setting. This commit renames the realm-level setting 'signup_notifications_stream' to 'signup_announcements_stream'. The new name reflects better what the setting does.
2024-02-07 17:11:43 +01:00
widget_name="realm_signup_announcements_stream_id"
label=admin_settings_label.realm_signup_announcements_stream
settings_org: Migrate dropdowns to new DropdownWidget. This also moves [Disabled] button inside the dropdown.
2023-07-19 16:14:00 +02:00
value_type="number"}}
settings: Add realm-level setting 'zulip_update_announcements_stream'. This commit adds a realm-level setting named 'zulip_update_announcements_stream' that configures the stream to which zulip updates should be posted. Fixes part of #28604.
2024-01-26 14:45:37 +01:00
{{> ../dropdown_widget_with_label
widget_name="realm_zulip_update_announcements_stream_id"
label=admin_settings_label.realm_zulip_update_announcements_stream
value_type="number"}}
settings: Reorder settings in "Automated messages and emails" section. This commit reorders the settings in "Automated messages and emails" subsection such that most useful options are at top and automated messages and email settings are grouped together as proposed in #25339.
2023-05-02 19:10:43 +02:00
settings: Move setting to allow message content in email notifications. We move "Allow message content in message notification emails" setting from "Other settings" subsection to "Automated messages and emails" subsection. Fixes #25339.
2023-05-02 19:13:41 +02:00
{{> settings_checkbox
setting_name="realm_message_content_allowed_in_email_notifications"
prefix="id_"
is_checked=realm_message_content_allowed_in_email_notifications
label=admin_settings_label.realm_message_content_allowed_in_email_notifications}}
templates: Use upstream Handlebars partials syntax. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-11 04:05:28 +02:00
{{> settings_checkbox
setting_name="realm_send_welcome_emails"
prefix="id_"
is_checked=realm_send_welcome_emails
label=admin_settings_label.realm_send_welcome_emails}}
org settings: Allow admins to enable or disable digest emails.
2019-04-06 06:34:49 +02:00
{{#if settings_send_digest_emails }}
templates: Use upstream Handlebars partials syntax. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-11 04:05:28 +02:00
{{> settings_checkbox
setting_name="realm_digest_emails_enabled"
prefix="id_"
is_checked=realm_digest_emails_enabled
label=admin_settings_label.realm_digest_emails_enabled}}
org settings: Allow admins to enable or disable digest emails.
2019-04-06 06:34:49 +02:00
{{/if}}
digest: Move digest weekday drop-down next to the enable checkbox.
2019-05-08 08:01:56 +02:00
<div class="input-group">
<label for="realm_digest_weekday" class="dropdown-title">{{t "Day of the week to send digests" }}</label>
<select name="realm_digest_weekday"
id="id_realm_digest_weekday"
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
class="setting-widget prop-element settings_select bootstrap-focus-style"
org settings: Use standard "types" in `.get_input_element_value()`. The reason is to make the hardcoded property type values consistent with `typeof` operator.
2020-05-07 11:20:22 +02:00
data-setting-widget-type="number">
digest: Move digest weekday drop-down next to the enable checkbox.
2019-05-08 08:01:56 +02:00
<option value="0">{{t "Monday" }}</option>
<option value="1">{{t "Tuesday" }}</option>
<option value="2">{{t "Wednesday" }}</option>
<option value="3">{{t "Thursday" }}</option>
<option value="4">{{t "Friday" }}</option>
<option value="5">{{t "Saturday" }}</option>
<option value="6">{{t "Sunday" }}</option>
</select>
</div>
org settings: Reorder the major sections of Organization settings.
2019-02-07 22:40:51 +01:00
</div>
</div>
settings: Rename "org-subsection-parent" class to "settings-subsection-parent". This commit renames the "org-subsection-parent" class used for organization settings subsections to "settings-subsection-parent" such that we can use same for the stream settings and avoid duplicating code for handling save-discard widget which will be added in future.
2022-11-03 13:18:42 +01:00
<div id="org-message-retention" class="settings-subsection-parent">
org settings: Enable message_retention_days in org settings UI. Since production testing of `message_retention_days` is finished, we can enable this feature in the organization settings page. We already had this setting in frontend but it was bit rotten and not rendered in templates. Here we replaced our past text-input based setting with a dropdown-with-text-input setting approach which is more consistent with our existing UI. Along with frontend changes, we also incorporated a backend change to handle making retention period forever. This change introduces a new convertor `to_positive_or_allowed_int` which only allows positive integers and an allowed value for settings like `message_retention_days` which can be a positive integer or has the value `Realm.RETAIN_MESSAGE_FOREVER` when we change the setting to retain message forever. This change made `to_not_negative_int_or_none` redundant so removed it as well. Fixes: #14854
2020-05-07 13:19:54 +02:00
<div class="subsection-header">
retention: Add link to message-retention-policy docs next to the heading. This commit adds link to the message-retention-policy docs next to the heading for both realm-level and stream-level settings.
2020-06-26 22:10:22 +02:00
<h3>{{t "Message retention" }}
{{> ../help_link_widget link="/help/message-retention-policy" }}
</h3>
org settings: Enable message_retention_days in org settings UI. Since production testing of `message_retention_days` is finished, we can enable this feature in the organization settings page. We already had this setting in frontend but it was bit rotten and not rendered in templates. Here we replaced our past text-input based setting with a dropdown-with-text-input setting approach which is more consistent with our existing UI. Along with frontend changes, we also incorporated a backend change to handle making retention period forever. This change introduces a new convertor `to_positive_or_allowed_int` which only allows positive integers and an allowed value for settings like `message_retention_days` which can be a positive integer or has the value `Realm.RETAIN_MESSAGE_FOREVER` when we change the setting to retain message forever. This change made `to_not_negative_int_or_none` redundant so removed it as well. Fixes: #14854
2020-05-07 13:19:54 +02:00
{{> settings_save_discard_widget section_name="message-retention" }}
</div>
{{> upgrade_tip_widget }}
<div class="inline-block organization-settings-parent">
settings: Disable "Save changes" button for invalid values. This commit disables the "Save changes" button when there is an invalid value in custom input of message retention setting. This commit includes changes for both realm and stream message retention setting.
2023-01-16 10:56:14 +01:00
<div class="input-group time-limit-setting">
settings: Refactor code for realm message retention setting. This commit refactors the code for realm message retention setting to make it more similar to code for other time-limit realm settings. There are still separate functions for the message retention setting but they are similar to that of other time-limit settings and can probably help us to deduplicate the code in future. This refactor also helps us in reusing some code for stream message retention setting for changes in #23013. This commit also fixes a bug where save-discard widget not being hidden when resetting the setting to original value. This can only be reproduced when the original setting value is "retain_forever". Following changes have been done in this commit - - Added data-setting-widget-type attribute which is set to "message-retention-setting" similar to "time-limit" value for message edit and delete limit settings. - Added get_message_retention_setting_value function similar to get_time_limit_setting_value function which is used by get_input_element_value. - Removed "message-retention" block from get_complete_data_for_subsection and the message retention setting is now added to request data in populate_data_for_request itself using data-setting-widget-type attribute. - Updated id and class of elements to support the above changes.
2022-11-04 11:11:33 +01:00
<label for="id_realm_message_retention_days" class="dropdown-title">{{t "Message retention period" }}
realm: Allow only owners to set message retention policy for a realm. This commits adds restriction on admins to set message retention policy. We now only allow only organization owners to set message retention policy. Dropdown for changing retention policy is disabled in UI for admins also.
2020-06-11 21:16:53 +02:00
</label>
settings: Refactor code for realm message retention setting. This commit refactors the code for realm message retention setting to make it more similar to code for other time-limit realm settings. There are still separate functions for the message retention setting but they are similar to that of other time-limit settings and can probably help us to deduplicate the code in future. This refactor also helps us in reusing some code for stream message retention setting for changes in #23013. This commit also fixes a bug where save-discard widget not being hidden when resetting the setting to original value. This can only be reproduced when the original setting value is "retain_forever". Following changes have been done in this commit - - Added data-setting-widget-type attribute which is set to "message-retention-setting" similar to "time-limit" value for message edit and delete limit settings. - Added get_message_retention_setting_value function similar to get_time_limit_setting_value function which is used by get_input_element_value. - Removed "message-retention" block from get_complete_data_for_subsection and the message retention setting is now added to request data in populate_data_for_request itself using data-setting-widget-type attribute. - Updated id and class of elements to support the above changes.
2022-11-04 11:11:33 +01:00
<select name="realm_message_retention_days"
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
id="id_realm_message_retention_days" class="prop-element settings_select bootstrap-focus-style"
settings: Refactor code for realm message retention setting. This commit refactors the code for realm message retention setting to make it more similar to code for other time-limit realm settings. There are still separate functions for the message retention setting but they are similar to that of other time-limit settings and can probably help us to deduplicate the code in future. This refactor also helps us in reusing some code for stream message retention setting for changes in #23013. This commit also fixes a bug where save-discard widget not being hidden when resetting the setting to original value. This can only be reproduced when the original setting value is "retain_forever". Following changes have been done in this commit - - Added data-setting-widget-type attribute which is set to "message-retention-setting" similar to "time-limit" value for message edit and delete limit settings. - Added get_message_retention_setting_value function similar to get_time_limit_setting_value function which is used by get_input_element_value. - Removed "message-retention" block from get_complete_data_for_subsection and the message retention setting is now added to request data in populate_data_for_request itself using data-setting-widget-type attribute. - Updated id and class of elements to support the above changes.
2022-11-04 11:11:33 +01:00
data-setting-widget-type="message-retention-setting"
org settings: Enable message_retention_days in org settings UI. Since production testing of `message_retention_days` is finished, we can enable this feature in the organization settings page. We already had this setting in frontend but it was bit rotten and not rendered in templates. Here we replaced our past text-input based setting with a dropdown-with-text-input setting approach which is more consistent with our existing UI. Along with frontend changes, we also incorporated a backend change to handle making retention period forever. This change introduces a new convertor `to_positive_or_allowed_int` which only allows positive integers and an allowed value for settings like `message_retention_days` which can be a positive integer or has the value `Realm.RETAIN_MESSAGE_FOREVER` when we change the setting to retain message forever. This change made `to_not_negative_int_or_none` redundant so removed it as well. Fixes: #14854
2020-05-07 13:19:54 +02:00
{{#unless zulip_plan_is_not_limited}}disabled{{/unless}}>
settings: Refactor code for realm message retention setting. This commit refactors the code for realm message retention setting which will help us in reusing some code when adding save-discard widget for stream settings in further commits. Following changes have been done in this commit - - Renamed the "retain_for_period" option to "custom_period" and "retain_forever" option to "unlimited" to match with the stream settings options such that we can reuse the code. - Updated set_message_retention_setting_dropdown such that it can be used for stream message retention setting as well.
2022-11-04 11:11:33 +01:00
<option value="unlimited">{{t 'Retain forever' }}</option>
settings: Improve wording of retention period options. Replaced the "Retain for N days after posting" option with "Custom". Only show the spot for entering the time if that option is selected. Labeled the custom time like we do for message editing: "Retention period (days): [ ]". This is now consistent with similar settings. Fixes part of #23532.
2022-12-02 04:42:38 +01:00
<option value="custom_period">{{t 'Custom' }}</option>
org settings: Enable message_retention_days in org settings UI. Since production testing of `message_retention_days` is finished, we can enable this feature in the organization settings page. We already had this setting in frontend but it was bit rotten and not rendered in templates. Here we replaced our past text-input based setting with a dropdown-with-text-input setting approach which is more consistent with our existing UI. Along with frontend changes, we also incorporated a backend change to handle making retention period forever. This change introduces a new convertor `to_positive_or_allowed_int` which only allows positive integers and an allowed value for settings like `message_retention_days` which can be a positive integer or has the value `Realm.RETAIN_MESSAGE_FOREVER` when we change the setting to retain message forever. This change made `to_not_negative_int_or_none` redundant so removed it as well. Fixes: #14854
2020-05-07 13:19:54 +02:00
</select>
settings: Move the retention days input below the dropdown. Moved the "Retention period (days):" under the dropdown "Custom". This is consistent with similar date window inputs elsewhere, and conveniently just requires changing a single class. Fixes: #23532
2022-12-08 01:59:39 +01:00
<div class="dependent-settings-block">
settings: Refactor code for realm message retention setting. This commit refactors the code for realm message retention setting to make it more similar to code for other time-limit realm settings. There are still separate functions for the message retention setting but they are similar to that of other time-limit settings and can probably help us to deduplicate the code in future. This refactor also helps us in reusing some code for stream message retention setting for changes in #23013. This commit also fixes a bug where save-discard widget not being hidden when resetting the setting to original value. This can only be reproduced when the original setting value is "retain_forever". Following changes have been done in this commit - - Added data-setting-widget-type attribute which is set to "message-retention-setting" similar to "time-limit" value for message edit and delete limit settings. - Added get_message_retention_setting_value function similar to get_time_limit_setting_value function which is used by get_input_element_value. - Removed "message-retention" block from get_complete_data_for_subsection and the message retention setting is now added to request data in populate_data_for_request itself using data-setting-widget-type attribute. - Updated id and class of elements to support the above changes.
2022-11-04 11:11:33 +01:00
<label for="id_realm_message_retention_custom_input" class="inline-block realm-time-limit-label">
settings: Improve wording of retention period options. Replaced the "Retain for N days after posting" option with "Custom". Only show the spot for entering the time if that option is selected. Labeled the custom time like we do for message editing: "Retention period (days): [ ]". This is now consistent with similar settings. Fixes part of #23532.
2022-12-02 04:42:38 +01:00
{{t 'Retention period (days)' }}:
org settings: Enable message_retention_days in org settings UI. Since production testing of `message_retention_days` is finished, we can enable this feature in the organization settings page. We already had this setting in frontend but it was bit rotten and not rendered in templates. Here we replaced our past text-input based setting with a dropdown-with-text-input setting approach which is more consistent with our existing UI. Along with frontend changes, we also incorporated a backend change to handle making retention period forever. This change introduces a new convertor `to_positive_or_allowed_int` which only allows positive integers and an allowed value for settings like `message_retention_days` which can be a positive integer or has the value `Realm.RETAIN_MESSAGE_FOREVER` when we change the setting to retain message forever. This change made `to_not_negative_int_or_none` redundant so removed it as well. Fixes: #14854
2020-05-07 13:19:54 +02:00
</label>
settings: Refactor code for realm message retention setting. This commit refactors the code for realm message retention setting to make it more similar to code for other time-limit realm settings. There are still separate functions for the message retention setting but they are similar to that of other time-limit settings and can probably help us to deduplicate the code in future. This refactor also helps us in reusing some code for stream message retention setting for changes in #23013. This commit also fixes a bug where save-discard widget not being hidden when resetting the setting to original value. This can only be reproduced when the original setting value is "retain_forever". Following changes have been done in this commit - - Added data-setting-widget-type attribute which is set to "message-retention-setting" similar to "time-limit" value for message edit and delete limit settings. - Added get_message_retention_setting_value function similar to get_time_limit_setting_value function which is used by get_input_element_value. - Removed "message-retention" block from get_complete_data_for_subsection and the message retention setting is now added to request data in populate_data_for_request itself using data-setting-widget-type attribute. - Updated id and class of elements to support the above changes.
2022-11-04 11:11:33 +01:00
<input type="text" id="id_realm_message_retention_custom_input" autocomplete="off"
name="realm_message_retention_custom_input"
settings: Disable "Save changes" button for invalid values. This commit disables the "Save changes" button when there is an invalid value in custom input of message retention setting. This commit includes changes for both realm and stream message retention setting.
2023-01-16 10:56:14 +01:00
class="admin-realm-message-retention-days message-retention-setting-custom-input time-limit-custom-input"
org settings: Enable message_retention_days in org settings UI. Since production testing of `message_retention_days` is finished, we can enable this feature in the organization settings page. We already had this setting in frontend but it was bit rotten and not rendered in templates. Here we replaced our past text-input based setting with a dropdown-with-text-input setting approach which is more consistent with our existing UI. Along with frontend changes, we also incorporated a backend change to handle making retention period forever. This change introduces a new convertor `to_positive_or_allowed_int` which only allows positive integers and an allowed value for settings like `message_retention_days` which can be a positive integer or has the value `Realm.RETAIN_MESSAGE_FOREVER` when we change the setting to retain message forever. This change made `to_not_negative_int_or_none` redundant so removed it as well. Fixes: #14854
2020-05-07 13:19:54 +02:00
data-setting-widget-type="number"
{{#unless zulip_plan_is_not_limited}}disabled{{/unless}}/>
</div>
</div>
</div>
</div>
settings: Rename "org-subsection-parent" class to "settings-subsection-parent". This commit renames the "org-subsection-parent" class used for organization settings subsections to "settings-subsection-parent" such that we can use same for the stream settings and avoid duplicating code for handling save-discard widget which will be added in future.
2022-11-03 13:18:42 +01:00
<div id="org-other-settings" class="settings-subsection-parent">
org settings: Restructure org-settings-admin template. This restructures the organization-settings-admin template into different subsections. With this, we can easily limit the scope of event handlers and selectors within their subsection to which are applied. There will be no change in UI because of this.
2018-03-14 18:50:55 +01:00
<div class="subsection-header">
org settings: Move video chat provider into other settings.
2019-02-07 22:57:52 +01:00
<h3>{{t "Other settings" }}</h3>
templates: Use upstream Handlebars partials syntax. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-11 04:05:28 +02:00
{{> settings_save_discard_widget section_name="other-settings" }}
Clean organization-settings-admin to use 4 space indents.
2017-05-12 17:16:22 +02:00
</div>
org settings: Restructure org-settings-admin template. This restructures the organization-settings-admin template into different subsections. With this, we can easily limit the scope of event handlers and selectors within their subsection to which are applied. There will be no change in UI because of this.
2018-03-14 18:50:55 +01:00
<div class="inline-block organization-settings-parent">
org settings: Move video chat provider into other settings.
2019-02-07 22:57:52 +01:00
<div class="input-group">
<label for="realm_video_chat_provider" class="dropdown-title">
settings: Reference 'Call provider' in settings.
2023-10-17 15:15:56 +02:00
{{t 'Call provider' }}
help: Document "Jitsi server URL" setting. - Updates "Start a call", documents the "Jitsi server URL" setting, and links to it in a (?) from the relevant admin UI. - Fixes misplaced include block for opening the compose box. Fixes #26907.
2023-11-02 00:57:03 +01:00
{{> ../help_link_widget link="/help/start-a-call" }}
org settings: Move video chat provider into other settings.
2019-02-07 22:57:52 +01:00
</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_video_chat_provider" class ="setting-widget prop-element settings_select bootstrap-focus-style" id="id_realm_video_chat_provider" data-setting-widget-type="number">
org settings: Move video chat provider into other settings.
2019-02-07 22:57:52 +01:00
{{#each realm_available_video_chat_providers}}
templates: Always indent "each" blocks.
2021-12-04 15:39:38 +01:00
<option value='{{this.id}}'>{{this.name}}</option>
org settings: Move video chat provider into other settings.
2019-02-07 22:57:52 +01:00
{{/each}}
</select>
org_settings: Add frontend support for `realm_jitsi_server_url`. This commit adds a dropdown and custom input element to set the `realm_jitsi_server_url` when the video call provider is Jitsi. This allows organization administrators to add a custom Jitsi server as the organization's video call provider. Fixes #17914. Co-authored-by: Gaurav Pandey <gauravguitarrocks@gmail.com>
2023-09-19 18:10:23 +02:00
<div class="dependent-settings-block" id="realm_jitsi_server_url_setting">
<div>
<label for="id_realm_jitsi_server_url" class="dropdown-title">
{{t "Jitsi server URL" }}
help: Document "Jitsi server URL" setting. - Updates "Start a call", documents the "Jitsi server URL" setting, and links to it in a (?) from the relevant admin UI. - Fixes misplaced include block for opening the compose box. Fixes #26907.
2023-11-02 00:57:03 +01:00
{{> ../help_link_widget link="/help/start-a-call#configure-a-self-hosted-instance-of-jitsi-meet" }}
org_settings: Add frontend support for `realm_jitsi_server_url`. This commit adds a dropdown and custom input element to set the `realm_jitsi_server_url` when the video call provider is Jitsi. This allows organization administrators to add a custom Jitsi server as the organization's video call provider. Fixes #17914. Co-authored-by: Gaurav Pandey <gauravguitarrocks@gmail.com>
2023-09-19 18:10:23 +02:00
</label>
<select name="realm_jitsi_server_url" id="id_realm_jitsi_server_url" class="setting-widget prop-element settings_select bootstrap-focus-style" data-setting-widget-type="jitsi-server-url-setting">
{{#if server_jitsi_server_url}}
<option value="server_default">
{{#tr}}{server_jitsi_server_url} (default){{/tr}}
</option>
{{else}}
<option value="server_default">{{t 'Disabled' }}</option>
{{/if}}
<option value="custom">{{t 'Custom URL' }}</option>
</select>
</div>
<div>
<label for="id_realm_jitsi_server_url_custom_input" class="jitsi_server_url_custom_input_label">
{{t 'URL' }}
</label>
<input type="text" id="id_realm_jitsi_server_url_custom_input" autocomplete="off"
settings: Restrict length of realm Jitsi url custom input. We have a restriction of 200 characters for jitsi_server_url realm setting custom input element. Fixes part of #27355.
2023-12-14 16:53:21 +01:00
name="realm_jitsi_server_url_custom_input" class="realm_jitsi_server_url_custom_input settings_url_input" maxlength="200" />
org_settings: Add frontend support for `realm_jitsi_server_url`. This commit adds a dropdown and custom input element to set the `realm_jitsi_server_url` when the video call provider is Jitsi. This allows organization administrators to add a custom Jitsi server as the organization's video call provider. Fixes #17914. Co-authored-by: Gaurav Pandey <gauravguitarrocks@gmail.com>
2023-09-19 18:10:23 +02:00
</div>
</div>
org settings: Move video chat provider into other settings.
2019-02-07 22:57:52 +01:00
</div>
giphy: Set rating according to realm_giphy_rating. We set rating of GIFs retrieved from GIPHY according to realm_giphy_rating setting. Also, we allow user to set a rating in organization settings.
2021-04-27 21:58:19 +02:00
<div class="input-group">
<label for="realm_giphy_rating" class="dropdown-title">
{{t 'GIPHY integration' }}
giphy: Add a '?' icon besides the "GIPHY integration" label. We add a '?' icon besides the "GIPHY integration" label of giphy settings dropdown. The icon links to readthedocs page for setting up giphy API key when api key is not set, and it points to help center article of GIFs when the api key is added.
2021-05-19 20:56:53 +02:00
{{> ../help_link_widget link=giphy_help_link }}
giphy: Set rating according to realm_giphy_rating. We set rating of GIFs retrieved from GIPHY according to realm_giphy_rating setting. Also, we allow user to set a rating in organization settings.
2021-04-27 21:58:19 +02:00
</label>
settings: Add settings_select class to select elements. This commit adds settings_select class to select elements in user and organization settings, such that we can add CSS using this class and not using "select" as selector so that we can easily add a select element in future with different CSS if needed.
2023-02-16 10:57:08 +01:00
<select name="realm_giphy_rating" class ="setting-widget prop-element settings_select bootstrap-focus-style" id="id_realm_giphy_rating" data-setting-widget-type="number" {{#if giphy_api_key_empty}}disabled{{/if}}>
giphy: Set rating according to realm_giphy_rating. We set rating of GIFs retrieved from GIPHY according to realm_giphy_rating setting. Also, we allow user to set a rating in organization settings.
2021-04-27 21:58:19 +02:00
{{#each giphy_rating_options}}
templates: Always indent "each" blocks.
2021-12-04 15:39:38 +01:00
<option value='{{this.id}}'>{{this.name}}</option>
giphy: Set rating according to realm_giphy_rating. We set rating of GIFs retrieved from GIPHY according to realm_giphy_rating setting. Also, we allow user to set a rating in organization settings.
2021-04-27 21:58:19 +02:00
{{/each}}
</select>
</div>
org settings: Move video chat provider into other settings.
2019-02-07 22:57:52 +01:00
settings_org: Migrate dropdowns to new DropdownWidget. This also moves [Disabled] button inside the dropdown.
2023-07-19 16:14:00 +02:00
{{> ../dropdown_widget_with_label
dropdown-list-widget: Rename setting_name -> widget_name. This change is another in a series of commits that allows us to use DLW outside of realm_settings.
2020-05-18 23:08:30 +02:00
widget_name="realm_default_code_block_language"
settings_org: Refactor code for dropdown list widget settings. This commit refactors the code for dropdown list widget settings such that we can reuse the added functions for further settings that will use dropdown_list_widget. This change will be helpful when we will add group-based settings and change some of the existing role-based settings to be group-based. We add a new function "get_widget_for_dropdown_list_settings" to get the widget variable from setting name. The functions to get and set the setting value use "get_widget_for_dropdown_list_settings" function to get the widget and then gets or sets the setting value accordingly. We also add "data-setting-widget-type" and "data-setting-value-type" attributes to the element like other settings. The "data-setting-widget-type" attr is used by get_input_element_value to use "get_dropdown_list_widget_setting_value" function for dropdown-list-widget settings. The "data-setting-value-type" attribute is used to parse the setting value to correct types in "get_dropdown_list_widget_setting_value" function.
2022-12-29 10:59:51 +01:00
label=admin_settings_label.realm_default_code_block_language
settings_org: Migrate dropdowns to new DropdownWidget. This also moves [Disabled] button inside the dropdown.
2023-07-19 16:14:00 +02:00
value_type="string"}}
markdown: Allow setting a default language for code blocks. This adds a new realm setting: default_code_block_language. This PR also adds a new widget to specify a language, which behaves somewhat differently from other widgets of the same kind; instead of exposing methods to the whole module, we just create a single IIFE that handles all the interactions with the DOM for the widget. We also move the code for remapping languages to format_code function since we want to preserve the original language to decide if we override it using default_code_clock_language. Fixes #14404.
2020-03-31 15:21:27 +02:00
templates: Use upstream Handlebars partials syntax. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-11 04:05:28 +02:00
{{> settings_checkbox
setting_name="realm_mandatory_topics"
prefix="id_"
is_checked=realm_mandatory_topics
label=admin_settings_label.realm_mandatory_topics}}
Restructure organization settings and permissions. This restructures organization settings and permissions to be more accurately grouped and for the permissions page to not be too long. CHANGES: PROFILE: (this was split out) organization-profile-admin.handlebars: form #1: name description (SUBMIT) avatar: (UPLOAD) (DELETE) SETTINGS: organization-settings-admin.handlebars: language (mostly untouched) message editing: time limit/history/retention message feed: mandatory-topics preview images preview websites PERMISSIONS: organization-permissions-admin.handlebars (mostly stuff was removed) Joining: restrict domains require invite User Identity: name changes email changes Streams/Emoji: creating streams: waiting period (ADDED) adding emojis (SUBMIT) for whole panel The profile group (name, description, avatar) were split into a new page that did not previously exist, and the permissions was stripped of message settings (message editing, message feed), but keeping the "waiting period" input and putting it in the "Streams & custom emoji" section. Fixes: #5844.
2017-08-18 01:23:55 +02:00
settings: Add option in settings_checkbox to show some text in parens. There are cases where we add some text in italics inside parens along with the label in checkbox settings. This commit adds option to settings_checkbox template so that we can directly use it and not require to duplicate the settings_checkbox code and thus we now use settings_checkbox template for enable_read_receipts setting.
2022-09-24 12:34:41 +02:00
{{> settings_checkbox
setting_name="realm_enable_read_receipts"
prefix="id_"
is_checked=realm_enable_read_receipts
label=admin_settings_label.realm_enable_read_receipts
label_parens_text=admin_settings_label.realm_enable_read_receipts_parens_text}}
settings: Add checkbox for enable_read_receipts setting.
2022-08-04 13:49:15 +02:00
org settings: Restructure org-settings-admin template. This restructures the organization-settings-admin template into different subsections. With this, we can easily limit the scope of event handlers and selectors within their subsection to which are applied. There will be no change in UI because of this.
2018-03-14 18:50:55 +01:00
{{#if server_inline_image_preview}}
templates: Use upstream Handlebars partials syntax. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-11 04:05:28 +02:00
{{> settings_checkbox
setting_name="realm_inline_image_preview"
prefix="id_"
is_checked=realm_inline_image_preview
org settings: Minor changes to link icons and documentation. Changed `help` to `help_link` so as to denote that it's a link to docs. Also, updated `message feed` to `other settings` in docs.
2020-04-02 20:42:37 +02:00
label=admin_settings_label.realm_inline_image_preview
help_link="/help/allow-image-link-previews"}}
org settings: Restructure org-settings-admin template. This restructures the organization-settings-admin template into different subsections. With this, we can easily limit the scope of event handlers and selectors within their subsection to which are applied. There will be no change in UI because of this.
2018-03-14 18:50:55 +01:00
{{/if}}
Restructure organization settings and permissions. This restructures organization settings and permissions to be more accurately grouped and for the permissions page to not be too long. CHANGES: PROFILE: (this was split out) organization-profile-admin.handlebars: form #1: name description (SUBMIT) avatar: (UPLOAD) (DELETE) SETTINGS: organization-settings-admin.handlebars: language (mostly untouched) message editing: time limit/history/retention message feed: mandatory-topics preview images preview websites PERMISSIONS: organization-permissions-admin.handlebars (mostly stuff was removed) Joining: restrict domains require invite User Identity: name changes email changes Streams/Emoji: creating streams: waiting period (ADDED) adding emojis (SUBMIT) for whole panel The profile group (name, description, avatar) were split into a new page that did not previously exist, and the permissions was stripped of message settings (message editing, message feed), but keeping the "waiting period" input and putting it in the "Streams & custom emoji" section. Fixes: #5844.
2017-08-18 01:23:55 +02:00
org settings: Restructure org-settings-admin template. This restructures the organization-settings-admin template into different subsections. With this, we can easily limit the scope of event handlers and selectors within their subsection to which are applied. There will be no change in UI because of this.
2018-03-14 18:50:55 +01:00
{{#if server_inline_url_embed_preview}}
templates: Use upstream Handlebars partials syntax. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-11 04:05:28 +02:00
{{> settings_checkbox
setting_name="realm_inline_url_embed_preview"
prefix="id_"
is_checked=realm_inline_url_embed_preview
settings: Add link for help near the setting of link previews Next to the checkbox of "Show previews of linked websites" added a documentation link in order to help users not confuse its function. To do this: - Added the field 'help' which is the link for the documentation in organization_settings_admin.hbs - Added the if statement in settings_checkbox.hbs to check if the above field exists.In case it exists, a help icon which leads to the documentation link appears. The specific field was added in order to be able to add a help link in other settings as well. Co-authored-by: Katerina Perikou <44238834+kPerikou@users.noreply.github.com> Fixes: #13450
2020-04-02 21:40:28 +02:00
label=admin_settings_label.realm_inline_url_embed_preview
org settings: Minor changes to link icons and documentation. Changed `help` to `help_link` so as to denote that it's a link to docs. Also, updated `message feed` to `other settings` in docs.
2020-04-02 20:42:37 +02:00
help_link="/help/allow-image-link-previews"}}
org settings: Restructure org-settings-admin template. This restructures the organization-settings-admin template into different subsections. With this, we can easily limit the scope of event handlers and selectors within their subsection to which are applied. There will be no change in UI because of this.
2018-03-14 18:50:55 +01:00
{{/if}}
Restructure organization settings and permissions. This restructures organization settings and permissions to be more accurately grouped and for the permissions page to not be too long. CHANGES: PROFILE: (this was split out) organization-profile-admin.handlebars: form #1: name description (SUBMIT) avatar: (UPLOAD) (DELETE) SETTINGS: organization-settings-admin.handlebars: language (mostly untouched) message editing: time limit/history/retention message feed: mandatory-topics preview images preview websites PERMISSIONS: organization-permissions-admin.handlebars (mostly stuff was removed) Joining: restrict domains require invite User Identity: name changes email changes Streams/Emoji: creating streams: waiting period (ADDED) adding emojis (SUBMIT) for whole panel The profile group (name, description, avatar) were split into a new page that did not previously exist, and the permissions was stripped of message settings (message editing, message feed), but keeping the "waiting period" input and putting it in the "Streams & custom emoji" section. Fixes: #5844.
2017-08-18 01:23:55 +02:00
</div>
</div>
Clean organization-settings-admin to use 4 space indents.
2017-05-12 17:16:22 +02:00
</form>
Separate organization settings from admin_tab template. This separates organization settings into its own template in the templates/settings folder.
2016-10-05 02:34:45 +02:00
</div>