You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exclude rules should be saved correctly, even if some of them do not contain IP addresses.
Actual Behavior
If there are multiple exclude rules and some of them have no IP address(es) set, settings are not saved correctly. The set IP addresses are then assigned to the wrong authors or roles, because they are displayed one after the other, ignoring whether an IP address was set in the current row at all.
I could replicate the issue and it's probably caused by the way the form uses non-indexed input field names name[] which fails when some of them have an empty value.
@tyrann0us Could you please test with the fix/1035-exclude-rules-table branch? You will probably need to run npm run build to re-build the minified JS files with the latest changes.
Bug Report
Expected Behavior
Exclude rules should be saved correctly, even if some of them do not contain IP addresses.
Actual Behavior
If there are multiple exclude rules and some of them have no IP address(es) set, settings are not saved correctly. The set IP addresses are then assigned to the wrong authors or roles, because they are displayed one after the other, ignoring whether an IP address was set in the current row at all.
Steps to Reproduce the Problem
Screenshots
Before save
After save
System Information
dev-fix/ip-address
The text was updated successfully, but these errors were encountered: