Problem/Motivation
I’m trying (yet again) to upgrade from D8 to D9.
With composer.json altered to have
- “drupal/core”: “^9.0"
- “drupal/core-composer-scaffold”: “^9.0"
- “drupal/core-recommended”: “^9.0"
- “drupal/core-dev”: “^9.0"
- “drush/drush”: “^10.0.0"
- “drupal/devel”: “^4.0"
I was finally able to run composer update --with-all-dependencies successfully. (Whoever came up with the output when composer has conflicts should be shot, twice, once in each leg.)
Next ran
- drush cr
- drush updb
- drush cr
- drush cim
Here’s where the next set of problems arise:
I may run out memory.
I can get around this by temporarily removing the limit with if(PHP_SAPI === 'cli'){ini_set('memory_limit', '-1');} added to the end of my settings.php file, but I instead get
Unexpected error during import with operation update for core.entity_view_display.commerce_product_variation.downloadable_file.default: The "commerce_file" plugin does not exist.
The plugin exists; has existed for a long time. I think I upgraded to 8.x-2.0-beta3 back in July.
Any idea why is drush unable to find it? The plugin appears to be properly annotated in src/Plugin/Commerce/LicenseType/File.php
I don't know whether the issue is with drush or commerce file. I started thinking the former, but maybe someone here has a clue?
Steps to reproduce
Start with a Drupal 8 site + Commerce File, latest versions.
Alter composer.json as above and run
- composer update --with-all-dependencies
- drush cr
- drush updb
- drush cr
- drush cim
Comments
Comment #2
msypes commentedI realize now that this is nonsense.
After the upgrade to D9, there's no sense in running
drush cim. Nothing altered the config yaml files such that they would need to update the database. Instead, the updates altered the database directly and those alterations need to be exported to update the config yaml files.