After updating Metatag to 8.x-1.0-beta3 there is the following error message on the status report page:

Entity/field definitions: Mismatched entity and/or field definitions

The following changes were detected in the entity type and field definitions.

Metatag defaults

  • Create the Metatag defaults entity type.

Core version is 8.0.1, tested on two different installations with same result.

I don't really understand what it means, the module is usable anyway.

Comments

majusz created an issue. See original summary.

damienmckenna’s picture

Version: 8.x-1.0-beta3 » 8.x-1.x-dev
Parent issue: » #2563607: Plan for Metatag 8.x-1.0-beta4 release
damienmckenna’s picture

Category: Bug report » Support request
Status: Active » Postponed (maintainer needs more info)

And you cleared all the cached and ran the db updates after updating the files?

majusz’s picture

Yes, cleared the cache several times, ran the DB updates.

grahl’s picture

I experience the same issue. I previously used 748d541fa1686e180f7278ce5259e1630fc3e626 and upgraded to 6f6ae020aaaa4f4363508538c500a66e967c5312.

The configuration entity is available and usable.

michèle’s picture

StatusFileSize
new9.43 KB

Hi, I've got the same issue here after updating from Drupal 8.01 to 8.02 (see screenshot).

damienmckenna’s picture

Category: Support request » Bug report
Status: Postponed (maintainer needs more info) » Active

Lets solve this.

damienmckenna’s picture

Priority: Normal » Major

I've confirmed that the problem occurs with the current codebase. Not sure why this is happening, any thoughts juampynr?

damienmckenna’s picture

Title: "Entity/field definitions" error after update to 8.x-1.0-beta3 » metatag_defaults entity configuration not created

So it seems to be because the entity configuration isn't being properly created in update 8103. Bummer.

damienmckenna’s picture

Status: Active » Needs review
StatusFileSize
new1.08 KB

Ok, so we need a new update script :)

damienmckenna’s picture

Status: Needs review » Needs work

Ok, so the new update script is going to be 8105, but we also need to fix 8103 because otherwise a field's default configuration will disappear.

damienmckenna’s picture

StatusFileSize
new2.03 KB

I found #2640894: Mismatched entity and/or field definitions which suggested running the following line:

  \Drupal::entityDefinitionUpdateManager()->applyUpdates();

Please try this patch. Thanks.

damienmckenna’s picture

Status: Needs work » Needs review
damienmckenna’s picture

Can someone please confirm the patch above fixes the problem? Thanks.

majusz’s picture

The patch in #12 solves the problem for me.

Thanks, DamienMcKenna!

damienmckenna’s picture

@majusz: Thanks for the update.

I'm going to test a clean update from beta 2 to the latest -dev before I'll commit this, just to be safe.

damienmckenna’s picture

Status: Needs review » Needs work

Updating from 8.x-1.0-beta2 to -dev with the patch applied, the following error is reported:

metatag module
Update #8103
Failed: Drupal\Core\Config\Schema\SchemaIncompleteException: Incomplete or missing schema for metatag.metatag_defaults.node__article in Drupal\Core\Config\Entity\ConfigEntityBase->toArray() (line 290 of core/lib/Drupal/Core/Config/Entity/ConfigEntityBase.php).

damienmckenna’s picture

Status: Needs work » Needs review
StatusFileSize
new1.68 KB

This appears to work.

  • DamienMcKenna committed 2fc86b4 on
    Issue #2636348 by DamienMcKenna: Config entity not working correctly...
damienmckenna’s picture

Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)

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