Problem/Motivation
Site won't load after upgrading to 2.0.0
Steps to reproduce
Upgrade existing installation via composer in the usual way. Try to load site. Get white screen and error message.
I tried to uninstall module using Drush, and got this error message:
" The 'core_version_requirement' constraint (^9 || ^10) requires the 'core' k
ey not be set in modules/composer/copyright_block/copyright_block.info.yml"
Proposed resolution
I commented that line out of copyright_block.info.yml and cleared the cache with Drush. The site returned. I assume that line needs to go away, but don't now if there are any other issues.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | copyright_block-fix-core-version-3357937.patch | 682 bytes | mrchristophy |
Issue fork copyright_block-3357937
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
maxilein commentedSame issue here
Comment #5
papagrandeThis also happens when attempting database updates.
Comment #6
robbmlewis commentedI can confirm, removing "core: 8.x" fixes the issue.
Comment #7
mrchristophy commentedPatch attached
Comment #8
maxilein commentedI can confirm, removing "core: 8.x" fixes the issue.
Comment #9
papagrande@RobbMLewis, @mrchristophy, @maxilein, thanks for testing and creating the patch. Would one of you be so kind and change the status to RTBC?
Then we can advocate for this to be merged in and a new version released.
Comment #10
jpro commentedThe patch at #7 works for me.
Comment #12
opdaviesComment #14
jpro commentedI don't understand why this issue is marked as fixed if no new release has been issued. Are we missing a step here?
Comment #15
papagrande@jpro, it's fixed in the sense that the patch has been committed and is now part of the 2.x branch.
However, you are correct that the fix hasn't been released. It looks like @opdavies created the 2.0.1 tag, but never actually released it. @opdavies, can you release a new version?
Comment #16
jpro commentedThanks, @PapaGrande