Declare upgrade status from D6, D7

Created on 19 February 2021, almost 4 years ago
Updated 22 February 2024, 9 months ago

Problem/Motivation

As of 8.8.x, modules can declare their Drupal 8 (or 9) upgrade status ( changelog , issue #2936365: Migrate UI - allow modules to declare the state of their migrations ).

Failing to do so makes it seem as if the Username Enumeration Prevention module has no migrations and/or is not ready to be upgraded... for example, see the following image...

... this could be a barrier preventing people from upgrading their sites to Drupal 8/9+.

But, there is no data to migrate to 8.x-1.x, so the migration is already finished!

Or rather,

  1. 6.x-1.x doesn't declare any tables, columns, or variables, so there's nothing to migrate
  2. 7.x-1.x doesn't declare any tables, columns, or variables, so there's nothing to migrate

Proposed resolution

Declare the finished upgrade path from D6 and D7 by creating a migrations/state/username_enumeration_prevention.migrate_drupal.yml and populating it appropriately.

Remaining tasks

  1. Review and feedback (especially, on whether the D6 and D7 migrations are in fact fully complete)
  2. RTBC and feedback
  3. Commit
  4. Release

User interface changes

None.

API changes

None.

Data model changes

None.

Feature request
Status

Closed: won't fix

Version

1.0

Component

Code

Created by

🇨🇦Canada mparker17 UTC-4

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇨🇦Canada mparker17 UTC-4

    While this patch only declares that the upgrade status is finished, and doesn't affect what actually gets migrated, I am happy to report that I was able to upgrade my Username Enumeration Prevention configuration from my drupal-7.99 site running username_enumeration_prevention-7.x-1.3 to a drupal-10.2.1 site running username_enumeration_prevention-8.x-1.3 using the migration code already in the D10 version of the module.

    But, hopefully, my success will help other people migrating D7 to D10.

    However, now that my D7 to D10 site migration is complete, my ability to contribute further to this issue if it ever gets reopened is severely limited, because the D7 site that I had been using to test has been retired. But, I'll keep an eye on this issue and try to answer questions to the best of my ability.

Production build 0.71.5 2024