Bug #9334
closedbogus dialogue on Limiter deletion
100%
Description
When deleting the last row of the Limiter config - an error "The last row may not be deleted." appears.
Clicking OK then presents "Are you sure you wish to delete limiter?".
On clicking OK the limiter is deleted.
Steps to reproduce:
1. Firewall / Traffic Shaper / Limiters - click New Limiter
2. Save limiter(s)
3. Apply changes
4. Diagnostics / Limiter Info - verify limiter config
5. Firewall / Traffic Shaper / Limiters - select Limiter
6. Click Delete Limiter
7. Observe dialog "The last row may not be deleted."
8. Click OK
9. Observe dialogue "Are you sure you wish to delete limiter?"
10. Click OK
11. Note that Limiter has been deleted
Updated by Johnny Good almost 5 years ago
David Burns wrote:
When deleting the last row of the Limiter config - an error "The last row may not be deleted." appears.
Clicking OK then presents "Are you sure you wish to delete limiter?".
On clicking OK the limiter is deleted.
Steps to reproduce:
1. Firewall / Traffic Shaper / Limiters - click New Limiter
2. Save limiter(s)
3. Apply changes
4. Diagnostics / Limiter Info - verify limiter config
5. Firewall / Traffic Shaper / Limiters - select Limiter
6. Click Delete Limiter
7. Observe dialog "The last row may not be deleted."
8. Click OK
9. Observe dialogue "Are you sure you wish to delete limiter?"
10. Click OK
11. Note that Limiter has been deleted
Same issue here. I was going to create a new report but after searching came across this old report. I'm surprised nothing was done about it?
Updated by Viktor Gurov almost 5 years ago
Updated by Jim Pingle almost 5 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.5.0
Updated by Renato Botelho almost 5 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Renato Botelho
- % Done changed from 0 to 100
Pull request has been merged. Thanks!
Updated by Viktor Gurov almost 5 years ago
- Status changed from Feedback to Resolved
works as expected on 2.5.0.a.20200211.1811
Updated by Jim Pingle over 4 years ago
- Status changed from Resolved to Feedback
- Target version changed from 2.5.0 to 2.4.5-p1
Updated by Jim Pingle over 4 years ago
- Status changed from Feedback to Resolved
Only one prompt with the expected warning now.