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.
This commit is contained in:
Sahil Batra 2024-11-14 19:55:03 +05:30 committed by Tim Abbott
parent 2de648df02
commit dccf39a245
1 changed files with 2 additions and 0 deletions

View File

@ -1293,6 +1293,8 @@ function check_maximum_valid_value(
if ( if (
property_name === "realm_message_content_edit_limit_seconds" || property_name === "realm_message_content_edit_limit_seconds" ||
property_name === "realm_message_content_delete_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" property_name === "email_notifications_batching_period_seconds"
) { ) {
setting_value = parse_time_limit($custom_input_elem); setting_value = parse_time_limit($custom_input_elem);