Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
modules/user/user.install:562: update_variables_to_config('user.flood'
Thanks in advance for helping many hands to make light work!
See #2181257: [meta] Variables to config migration [d7] for instructions
Comment | File | Size | Author |
---|---|---|---|
#23 | 2132221-23.patch | 9.58 KB | phenaproxima |
#20 | 2132221-20.patch | 9.64 KB | phenaproxima |
#19 | 2132221-19.patch | 9.67 KB | phenaproxima |
#14 | 2132221-13.patch | 3.98 KB | joshtaylor |
Comments
Comment #1
fastangel CreditAttribution: fastangel commentedworking on this.
Comment #2
fastangel CreditAttribution: fastangel commentedI can't find mapping for this. In d8 we have:
But in d6 the table flood is into module system. And the variables to settings flood are managed with system module (That were implemented in other issues)
Comment #3
chx CreditAttribution: chx commentedLet me try to explain this once again: if you were to copy the problematic Drupal 7 variables then I would not need to open user.install , find the update function and that we talk about user_failed_login_user_limit. This is frustrating and wastes my time. You have this in front of you. Please save a little time for me. What we have in Drupal 8 is (almost) irrelevant in this case because we need to see what the variable is used for in D7 and then compare to D8.
In this specific case, if you run a search on user_failed_login_user_limit in D7 then you can find that it has no UI to set and it's read merely twice. It's not upgraded from D6, that's for sure. It is visible that it's used a configuration for flood control.
Searching for flood_is_allowed in D6 shows that only contact was flood controlled and user login was not. So this is D7 only.
Comment #4
eliza411 CreditAttribution: eliza411 commentedMoving to the core queue to consolidate issues now that we're doing all the work there.
Comment #5
eliza411 CreditAttribution: eliza411 commentedComment #6
eliza411 CreditAttribution: eliza411 commentedComment #7
eliza411 CreditAttribution: eliza411 commentedComment #8
eliza411 CreditAttribution: eliza411 commentedComment #9
joshtaylor CreditAttribution: joshtaylor commentedI am working on this.
Comment #10
joshtaylor CreditAttribution: joshtaylor commentedComment #11
benjy CreditAttribution: benjy commentedWhy would all these be null?
Shouldn't this be
d6_variable
?Comment #12
joshtaylor CreditAttribution: joshtaylor commentedGood catch - I've updated to d6_config as per the new standard.
I also can't get the tests to pass - for some reason after loading the dumps it thinks it is null.
This is also my first interdiff, let me know if it is incorrect.
Comment #13
benjy CreditAttribution: benjy commentedThis key doesn't match above?
Ident is wrong on this.
Comment #14
joshtaylor CreditAttribution: joshtaylor commentedSorry for the delay on this - I have updated the files to mimic https://drupal.org/node/2130283 .
I've fixed the indentation levels, updated the YML for user_failed_login_identifier_uid_only, and all tests pass.
Comment #15
joshtaylor CreditAttribution: joshtaylor commentedComment #16
benjy CreditAttribution: benjy commentedThanks. Committed to drupal7 c641847
Comment #18
jcost CreditAttribution: jcost commentedWill need to be submitted again to Core since moving from sandbox.
Comment #19
phenaproximaRerolled against 8.0.x, with a test of the d7_user_flood migration.
Comment #20
phenaproximaDeleted a bit of extraneous cruft from the test.
Comment #22
phenaproximaBlocked by #2495755: Create MigrateDrupal7TestBase.
Comment #23
phenaproximaComment #24
phenaproximaNeeds to be merged into the parent issue.
Comment #25
phenaproximaMerged into #2414651: Migration Files for Drupal 7 Users.