Admin › Security: “Max Upload Size” field loses its unit while typing

[HermessNRJ]

Version: 3.0.2 (still present in 3.1.0)

Steps to reproduce

1. Go to Admin → Security → Uploads.
2. Clear the Max Upload Size field and type 150 MB.

Expected behavior

The limit is set to 150 MB.

Actual behavior

The field shows 50 B while typing (an intermediate state), and the value saved is 150 bytes.

Cause

The input is bound with v-model.number="state.humanUploadMaxFileSize". Vue casts the input to a number as soon as it starts with a digit, so the unit suffix is dropped before the filesize parser sees it. A human-readable size cannot be entered.

Workaround

1. Type the raw value in bytes, for example 157286400 for 150 MiB.
2. Save.
3. Restart the server: the setting only applies after a restart.

Suggested fix

• Remove the .number modifier and parse the human-readable string on save.
• Show a restart notice next to the field.

[karenrebecag]

The .number modifier on the field is the cause. Vue casts the input to a number as soon as it starts with a digit, so the unit is gone before the parser runs. Save then receives 150 and stores 150 bytes.

Workaround: type the size in bytes. 150 MiB is 157286400.

Evidence:

• frontend/src/pages/AdminSecurity.vue L315-L320 binds the field with v-model.number="state.humanUploadMaxFileSize".
• save() (L555-L563) runs filesizeParser(state.humanUploadMaxFileSize || '0'). The parser expects the string with its unit, and by then it has already been cast to a number.

Fix direction: drop .number so the model stays a string. save() already parses it with filesizeParser. I have not run that change, so treat it as the likely fix until someone tests it.

I read this from the code at a13a208; I did not run the UI.

[NGPixel]

Fixed via 60e813d. Will land in next release.