Bug #5069
closed
system_authservers.php - "Type" value cleared on save
0%
Description
- Create a RADIUS server entry
- Save
- Edit the RADIUS server entry -- Name and Type are disabled since they cannot be changed
- Make a change such as altering the hostname/IP address
- Save
- Edit the RADIUS server entry again -- The altered values did not save and the server now shows LDAP.
Running a diff from the config history shows the "type" value is empty after saving.
Quick demo:
Updated by Jim Pingle over 8 years ago
Same thing happens to the Descriptive Name field with LDAP... Save and the name and type both go blank. Probably since the form fields are disabled.
IIRC in cases like this in the past some code would re-enable disabled fields when clicking save before POST so the fields would still be submitted.
Updated by Anonymous over 8 years ago
- Status changed from Confirmed to Feedback
- Assignee changed from Anonymous to Jim Pingle
Inputs should be readonly, not disabled when not required. Disabling prevents them from being submitted and breaks the form.
Updated by Jim Pingle over 8 years ago
- Status changed from Feedback to Assigned
- Assignee changed from Jim Pingle to Anonymous
The save behavior is OK but there is a weird display issue with the "Type" drop-down, it still renders as a drop-down but with the other choice disabled. So it's good in that you can't change it, but it still appears as though it's enabled and able to be changed.
Current behavior is fine, if the look can't be changed this can just be closed.
Updated by Anonymous over 8 years ago
- Status changed from Assigned to Closed
- Assignee changed from Anonymous to Jim Pingle
This is a bootstrap oddity. "<select>"s don't support the readonly attribute so you have to disable them. Disabling prevents them being submitted in the form, however. The solution is to disable the options, but not the select.
There have been many complaints about this and it is expected to be addressed in a future release.
Updated by Jim Pingle over 8 years ago
OK. In the 2.2.x the value was presented as plain text when editing, rather than any sort of entry control. That may be something else to consider if they don't fix it.