-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
luci-app-firewall: Improper processing of multi-selects for "Allow forward..." within Zone Settings #7563
Comments
Thanks for bringing this to our attention. Resolved in 7046a1c. Evidently enforcing a datatype on the widget (in the way it was done) did not handle multiple values well. That's been removed. You can wait a few days for an updated luci package, or replace this file immediately. Or edit it yourself to remove as follows: dropdown_items: this.dropdown_size || this.size || 5,
validate: L.bind(this.validate, this, section_id),
- datatype: L.hasSystemFeature('firewall4') ? 'uciname' : 'and(uciname,maxlength(11))',
create: !this.nocreate,
create_markup: '' +
|
@adelton your original commit was removed, but the result ended up being removing length restrictions elsewhere, via the check for fw4 (instead of adding the restriction in the widget). There may be other areas where the Zone widget in other places can receive a similar treatment (removing the length check via fw4 check) |
Ah, sorry about that. Would you like to reopen #7522 as that is effectively no longer resolved? |
The Firewall zones page was fixed not to limit the name length to 11 characters. So, problem resolved I think. |
I've now filed #7564 which adds the |
Is there an existing issue for this?
screenshots or captures
Actual behaviour
Any multi-select in either the "Allow forward to destination zones:" or "Allow forward from source zones:" results in an "Expecting: valid UCI identifier" error and an inability to Save. This appears to have been recently introduced.
Expected behaviour
The multi-select should be valid and saving should proceed as normal.
Steps to reproduce
Additional Information
What browsers do you see the problem on?
Chrome, Microsoft Edge
Relevant log output
No response
The text was updated successfully, but these errors were encountered: