Provide upgrade path from 8.x-2.x to 3.0.x

Created on 25 November 2020, over 4 years ago
Updated 21 October 2022, over 2 years ago

Problem/Motivation

There is no upgrade path from 8.x-2.x to 3.0.x. See #3162309: Save encrypted data as part of the entity and not as a separate entity β†’ for discussions.

Explore is this is possible. I'm not sure it is. Or can be done in a way that doesn't have quite severe risks.

Proposed resolution

This issue will not block the release of 3.0.0 and is explicitly not tagged with '3.0.0 milestone'

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Active

Version

3.0

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

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.

  • πŸ‡ΊπŸ‡ΈUnited States joegl

    We had a site not get updated properly on a multi-site and couldn't downgrade back to the old version. I have not found a perfect path to upgrade, but the process I've used is:

    1. Go to `/admin/config/system/field-encrypt/field-overview`. This lists all the encrypted fields on the site.

    2. Retrieve the values of these fields or make sure you have them on hand already (also perform a database backup). There is a "Decrypt" button on the field-overview page, but I could not get it to work.

    3. Uninstall the `field_encrypt` module

    4. Re-install the `field_encrypt` module. We use config management, so I did this with importing config with drush instead `drush ci` and `drush updatedb`.

    5. Go to `/admin/config/system/field-encrypt/process-queues` and click the button to process the queues.

    6. Re-fill in the values for the fields you have encrypted.

    Perhaps there's a better way to do this, but this worked for our needs.

  • Status changed to Closed: won't fix about 2 months ago
  • πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

    Going to close this as a won't fix because no one has done the work over the years. And it is not a priority now.

Production build 0.71.5 2024