The module cannot currently be installed on Drupal 11 because metis.info.yml declares:

core_version_requirement: ^8 || ^9

This needs to be updated for current core support.

Proposed change:

- Update `core_version_requirement` to include Drupal 11.
- If Drupal 9 is no longer supported by the release branch, align the requirement with the actual supported core versions.

Suggested acceptance criteria:

- The module can be enabled on a clean Drupal 11 site.
- The project page/release metadata no longer advertises unsupported core versions for this branch.

Comments

sanduhrs created an issue. See original summary.

sanduhrs’s picture

sanduhrs
he/him
Primary language German
Location 🇪🇺 Heidelberg, Germany, Europe
commented
Issue tags: +D11 compatability
sanduhrs’s picture

sanduhrs
he/him
Primary language German
Location 🇪🇺 Heidelberg, Germany, Europe
commented
Issue summary: View changes
yan’s picture

yan commented
Assigned: Unassigned » yan

How should we handle Drupal 8? Remove from core_version_requirement? It's EOL anyway and it would probably be hard to keep code compatible in the long run. But I'm not sure what best pratice is in this sense.

sanduhrs’s picture

sanduhrs
he/him
Primary language German
Location 🇪🇺 Heidelberg, Germany, Europe
commented

I would aim for ^9 || ^10 || ^11 if possible, and even drop 9 if needed.

  • sanduhrs committed e3a558e9 on 2.0.x authored by yan 
    Issue #3608164: Drupal 11 compatibility fixes
sanduhrs’s picture

sanduhrs
he/him
Primary language German
Location 🇪🇺 Heidelberg, Germany, Europe
commented
Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

yan’s picture

yan commented

@sanduhrs, regarding versions, #3608168: Rewrite entity hooks to use the field API and remove hard-coded field_metis usage introduces Drupal 10/11-style #[FieldType(...)] attributes that I believe are compatible with 10.3+. Maybe next release should be 2.1.0 with compatibility 10.3+ / 11 and 2.05 would be the last version with d9 support? Since d9 ist EOL since 2023, that could be justified.

Status: Fixed » Closed (fixed)

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