Change Details

Because of T366505, the #CheckUser extension no longer writes data about log events to `cu_changes`. The code that handles autoblocks does not currently have support to read from `cu_log_event` and `cu_private_event`. =========Steps to replicate the issue* # Create a new account # Block that new account with autoblocks enabled **What happens?**: No autoblock is performed **What should have happened instead?**: An autoblock should have been performed, which autoblocks the IP that was used to create the account

Because of T366505, the #CheckUser extension no longer writes data about log events to `cu_changes`. The code that handles autoblocks does not currently have support to read from `cu_log_event` and `cu_private_event`. =========Steps to replicate the issue # Create a new account # Block that new account with autoblocks enabled **What happens?**: No autoblock is performed **What should have happened instead?**: An autoblock should have been performed, which autoblocks the IP that was used to create the account

Because of T366505, the #CheckUser extension no longer writes data about log events to `cu_changes`. The code that handles autoblocks does not currently have support to read from `cu_log_event` and `cu_private_event`. =========Steps to replicate the issue* # Create a new account # Block that new account with autoblocks enabled **What happens?**: No autoblock is performed **What should have happened instead?**: An autoblock should have been performed, which autoblocks the IP that was used to create the account