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.

Command icon 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:

  • 2.x Comparechanges, plain diff MR !1

Comments

jpro created an issue. See original summary.

maxilein’s picture

Same issue here

PapaGrande made their first commit to this issue’s fork.

papagrande’s picture

Title: Upgrading to version 2.0.0 breaks site » Remove deprecated core key that breaks site
Status: Active » Needs review

This also happens when attempting database updates.

robbmlewis’s picture

I can confirm, removing "core: 8.x" fixes the issue.

mrchristophy’s picture

Patch attached

maxilein’s picture

I can confirm, removing "core: 8.x" fixes the issue.

papagrande’s picture

@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.

jpro’s picture

Status: Needs review » Reviewed & tested by the community

The patch at #7 works for me.

  • mrchristophy authored 2ec602ea on 2.x
    Issue #3357937 by PapaGrande, mrchristophy: Remove deprecated core key...
opdavies’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

jpro’s picture

I don't understand why this issue is marked as fixed if no new release has been issued. Are we missing a step here?

papagrande’s picture

@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?

jpro’s picture

Thanks, @PapaGrande