- Issue created by @chfoidl
- Status changed to Fixed
10 months ago 9:15am 19 February 2024 Automatically closed - issue fixed for 2 weeks with no activity.
- 🇩🇪Germany Anybody Porta Westfalica
@chfoidl if you're using the core flood services, shouldn't this better live in flood_control module?
✨ Add an expiration (setting) for blocked IPs and usernames ActiveYou might suggest using flood_control in combination with this module to have all the advanced options and unblocking UI?
- 🇦🇹Austria chfoidl Salzburg
@anybody The
flood_control
contrib module provides just the UI portion for the Drupal Coreflood
module's functionality.Configuration of attempt count and expiry window is already part of Drupal Core, but there is no native UI for configuring those parameters.
The
flood_control
contrib module does not need change anything to support any other module using the flood system. The unblock form supports any event registered via the core flood service, so it naturally works with themagic_code
module as well.Right now there is no UI to configure the attempt count and expiry window specific to the
magic_code
module. If you want to configure it right now, you have to set those parameters insettings.php
, but it would definetly make sense to expand on theflood_control
configuration form to allow configuration of this module's flood settings. - Status changed to Needs work
8 months ago 1:41pm 17 April 2024 - 🇩🇪Germany Anybody Porta Westfalica
Thank you very very much for your feedback @chfoidl!
Yes I agree. And I think both modules would benefit from that. Nice project btw. I just came across this issue and wanted to let you know :)