Bug #6801
closed
Rule separators are moving when multiple firewall rules are deleted together
100%
Description
Steps to reproduce:
1. Select multiple firewall rules
2. Delete together
3. The rule separators changed their position
IMPORTANT NOTE: Only the separators below the deleted firewall rules are moving.
Files
Updated by Anonymous about 8 years ago
- Status changed from New to Feedback
- Assignee changed from Anonymous to TCI User
Fixed and tested. Please confirm.
Updated by Anonymous about 8 years ago
- % Done changed from 0 to 100
Applied in changeset 00098bc80b6f85eb74f2f3bc2b4eb7430614110d.
Updated by TCI User about 8 years ago
Steve Beaver wrote:
Applied in changeset 00098bc80b6f85eb74f2f3bc2b4eb7430614110d.
Steve, would you provide me with basic instructions on how to apply the change so I can test it?
I already have the System_Patches package installed.
Thanks,
Slav
Updated by Anonymous about 8 years ago
Probably easiest to just wait from the next snapshot and update. Alternatively you could access the updated file here: https://github.com/pfsense/pfsense/blob/master/src/usr/local/www/firewall_rules.php and copy/paste it into your pfSense installation using Diagnostics -> Edit file.
Updated by Jim Pingle about 8 years ago
The wiki doc for the System Patches package explains how to use the commit ID from the above comment to apply the patch: https://doc.pfsense.org/index.php/System_Patches
Updated by TCI User about 8 years ago
Thank you Steve / Jim.
I found it safer to apply the changes through Diagnostics -> Edit file.
Confirming that firewall_rules.php works fine and the separators do not move.
Please apply the change and to firewall_nat.php
Regards,
Slav
Updated by Anonymous about 8 years ago
- Status changed from Feedback to Resolved
- Target version set to 2.3.2-p1
Thanks for confirming. Fix has now been applied to firewall_nat.php as well.
Updated by Max Frames about 5 years ago
It seems that the bug has returned, as I just had this exact issue when deleting multiple firewall rules with version 2.4.4-RELEASE-p3 (amd64).
Updated by Jim Pingle about 5 years ago
I couldn't reproduce the exact same bug stated here, but I did manage to reproduce a similar one. I opened #9887 and added details there.