shivamitakari → created an issue.
shivamitakari → made their first commit to this issue’s fork.
shivamitakari → created an issue.
shivamitakari → made their first commit to this issue’s fork.
shivamitakari → created an issue.
Created a patch to add support for configuring copy prevention per page basis.
shivamitakari → created an issue.
shivamitakari → created an issue.
shivamitakari → created an issue.
I have tested the patch select2-check-indexes-3271205-8.patch and it works fine.
Added patch which has same code added by akalam.
Hello Greg,
Apologies for coming late on this thread. May I please know what do you mean by adding that option in drush itself?
with this patch, I'm adding one parameter, and its used in the sql-sanitize command.
./vendor/bin/drush sql:sanitize --sanitize-tfa=no
This will skip the sanitization.
Hello Greg,
Thanks for quickly having look.
Yes disabling can be an option but I do still need users with admin roles to have TFA on non-prod env for safety and with the current TFA module there is no option to skip the TFA sanitization
This patch just gives an option for users if they want to skip sanitization.
Hello Greg,
Please find the below motivation for the patch.
I usually do production database sanitization before importing it to lower environments (like development and test).
I have TFA setup on a production website and whenever I sanitize the production database, TFA data is getting sanitized as it's not having the option to skip the sanitization. Due to this in lower environments, while testing users need to set up TFA again and they can't use the same TFA which they have set up on production.
shivamitakari → created an issue.
Fixed by setting default value as empty array.
shivamitakari → created an issue.