Support for Verification API 2.x has been added in the 2.x branch!
Hi @grasmash!
Thank you for your contribution.
I made some additional tweaks to your code:
- Added unique error code for each flood block response.
- Updated tests
I just tried removing jooplan as a maintainer from the project, but the page displays the user status as locked
The `AdvancedUserRegistrationResource` now supports a custom HTTP Header to disable E-Mail notifications.
See https://git.drupalcode.org/project/user_api/-/commit/3ea71fd23a26aeb8dc4...
@anybody The flood_control contrib module provides just the UI portion for the Drupal Core flood 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 the magic_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 in settings.php, but it would definetly make sense to expand on the flood_control configuration form to allow configuration of this module's flood settings.
chfoidl → created an issue. See original summary → .
Thank you for your contribution!
Thank you for your contribution!
I appended Block to the block class (and filename) and made the block id more specific.
Additionally a test was added to test the block.
Merged!
Thank you for your contribution!
Merged!
Thank you for your contribution!
Thank you both for your contribution!
But this project is about 12 hours old, and I am currently actively working on it.
I will add a properly formatted readme with proper contents describing the module soon.
Release files for commit 524433671f08983b5fc402f046ead04eeae2b854