The tests against 11.4.x are currently failing:

 Metatag Forum (Drupal\Tests\metatag\Functional\MetatagForum)
     ✘ Forum post
       ┐
       ├ Behat\Mink\Exception\ExpectationException: Current response status code is 500, but 200 expected.
       │
       │ /builds/project/metatag/vendor/behat/mink/src/WebAssert.php:888
       │ /builds/project/metatag/vendor/behat/mink/src/WebAssert.php:145
       │ /builds/project/metatag/tests/src/Functional/MetatagForumTest.php:85
 

Issue fork metatag-3582789

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:

Comments

damienmckenna created an issue. See original summary.

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

shubhamgoel’s picture

Status: Active » Needs review

Hi Team,

On Drupal 11.4 and later, entityBaseFieldInfo() read $entity_type->getDecoratedClasses()[0]. That array is empty for entity types whose class was never decorated. The empty read raises an undefined-index error, which would surface as a 500 when the node add page builds its entity definitions. It now falls back to $entity_type->getClass() when the array is empty.

Please review and merge the MR https://git.drupalcode.org/project/metatag/-/merge_requests/287/diffs

damienmckenna’s picture

Title: Fix tests against 11.4.x » Fix Forum tests against 11.4.x
Parent issue: » #3632962: Plan for Metatag 2.2.2

Thank you for identifying the source of the error and for providing a fix.

damienmckenna’s picture

Status: Needs review » Fixed

Committed, Thank you.

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.

shubhamgoel’s picture

Hi @damienmckenna,

Can you please review the contribution credit for this issue?

damienmckenna’s picture

Yes, it has been updated.

Status: Fixed » Closed (fixed)

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