Problem/Motivation

The entity usage module has created a new release branch for Drupal 12 compatibility that drops compatibility for versions prior to 11.4.

Since this module is dependent on that module, we'll need to mimic that same branch structure.

In the 2.x branch, add Drupal 12 and entity_usage 5.x compatibility and drop Drupal 10 compatibility.

Issue fork entity_usage_plus-3620257

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:

About issue forks

Comments

jastraat created an issue. See original summary.

jastraat opened merge request !7

jastraat’s picture

jastraat commented

The entity_usage 5.x branch made some big changes to how the usage page is assembled, so entity_usage_plus will need to update to use the new methods in the Controller.

jastraat’s picture

jastraat commented

The MR has a working solution that separates the parent and child entities on the usage tab into separately paged tables. This allows for better separation from entity usage decisions regarding the contents and build of the usage tab table. (e.g. when columns change)

jastraat’s picture

jastraat commented
Status: Active » Needs review
jasongose’s picture

jasongose commented
Status: Needs review » Reviewed & tested by the community

This looks good to me (tested in D11 and D12)

  • jastraat committed 4d5d4be4 on 2.0.x 
    task: #3620257 Add compatibility with Drupal 12 and entity_usage 5.x

By...
jastraat’s picture

jastraat commented

Thank you @jasongose!

Remembered that this is in a new branch (2.x) to match the new branch of entity_usage.

jastraat’s picture

jastraat commented
Status: Reviewed & tested by the community » 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.

Status: Fixed » Closed (fixed)

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