From dccf39a24545c141d49a9fd4c93281063405a4f1 Mon Sep 17 00:00:00 2001 From: Sahil Batra Date: Thu, 14 Nov 2024 19:55:03 +0530 Subject: [PATCH] settings: Fix checking max values for message move limit settings. The setting value for message move limit seconds was not being converted to seconds before checking if the value was allowed or not and that resulted in requests being made for values greater than the allowed values. --- web/src/settings_components.ts | 2 ++ 1 file changed, 2 insertions(+) diff --git a/web/src/settings_components.ts b/web/src/settings_components.ts index 90968c2b7f..6e8d2b0ca5 100644 --- a/web/src/settings_components.ts +++ b/web/src/settings_components.ts @@ -1293,6 +1293,8 @@ function check_maximum_valid_value( if ( property_name === "realm_message_content_edit_limit_seconds" || property_name === "realm_message_content_delete_limit_seconds" || + property_name === "realm_move_messages_between_streams_limit_seconds" || + property_name === "realm_move_messages_within_stream_limit_seconds" || property_name === "email_notifications_batching_period_seconds" ) { setting_value = parse_time_limit($custom_input_elem);