Closed bugfolder closed 11 months ago
Thanks, seems to be a useful feature. So, for all of them on import: reason is "Imported during migration", uid is current user (who perform the migration) id, and time is import time. Seems OK for you?
So, for all of them on import: reason is "Imported during migration", uid is current user (who perform the migration) id, and time is import time. Seems OK for you?
That would probably be OK, but for maximum flexibility, maybe consider creating textfields that let the user set those values during the import, but specifying what you suggested as the default values.
And then also, since the table of blocked IPs could be quite large (on my site, there's over 70K blocked IPs), the import should be done as a batch job to prevent timeouts during the import.
Resolved in latest release.
I have found bug, so here one more release today.
Just to note how it was tested.
When installing this module on top of a site upgraded from D7 that has blocked IPs (in table
blocked_ips
), this module renames that table toblocked_ips_d7
) and creates its ownblocked_ips
table, which has 3 additional columns:reason
,uid
, andtime
.For people upgrading who have a lot of blocked IPs, they would likely like to keep those IPs blocked. So it would be nice if the
blocked_ips_d7
table exists, to offer admins the option to move those IPs intoblocked_ips
, specifying the reason, uid, and time to use for all of them upon import. And then drop theblocked_ips_d7
table.