When I turn on this extension - there are error in the report.
turn it off - the error disappears.
Drupal 8.0.2
Mismatched entity and/or field definitions
The following changes were detected in the entity type and field definitions.

| Comment | File | Size | Author |
|---|---|---|---|
| #31 | fix-mismatched-entity-and-field-definitions-2661178-31.patch | 3.43 KB | ilya.no |
| #26 | 2661178.26.patch | 4.55 KB | pingers |
| #24 | 2661178.24.patch | 4.55 KB | pingers |
| #11 | 2661178.11.patch | 4.56 KB | alexpott |
| #11 | 2661178.test-only.patch | 1.13 KB | alexpott |
Comments
Comment #2
fomenkoandrey commentedComment #3
meichr commentedI've had the same issue after turning on pathauto, token and ctools on a website with existing content types.
There is a workaround for the time being, if you can use drush, described on a similar issue (Mismatched entity and/or field definitions after upgrade from RC1 to RC2).
drush entity-updates
This corrects the entity. Nevertheless, Pathauto should do this during its installation by itself.
Thanks for the work on the module to the maintainers!
Comment #4
berdirthat's not so easy because pathauto alters any path field and makes it computed. We don't really know which ones are out there (although by default it is only node and taxonomy_term). But a module could be added later and add a field.
The thing is that we're changing a field that has custom storage and are making it computed. It had no storage before and it still doesn't, so there really couldn't possibly a change. I'm even considering a core issue to not consider this a change. Or change core to make the field computed.
Also note that while this is reported as an *error*, it's completely irrelevant and you can happily ignore it.
Comment #5
juampynr commentedThere was a previous issue reporting the same error: #2646784: Mismatched field definitions.
Comment #6
Anonymous (not verified) commentedI do get this also. pathauto version used: 8.x-1.0-alpha1 on drupal 8.0.3
Comment #7
frazac_naba commentedI get the same error.
I added a pattern in pathauto automation, when I try to bulk generate, I get:
And
(see screenshot)
My setting:
Drupal 8.0.3
Pathauto 8.x-1.0-alpha1
Ctools 8.x-3.0-alpha23
Tokens 8.x-1.0-alpha2
One notice: previously I changed the display name of "Article" content type but not everywhere I read the same new name, somewhere it remains "Article". It seems there's some db mismatching field (update.php and clear cache already done). It has something to do?
Now I'll uninstall waiting for upgrades. In the meantime: thanks to all!
Comment #8
frazac_naba commentedComment #9
berdirOpened #2673628: Ignore field definition removals/additions from fields with custom storage.
Comment #10
galactus86 commentedI am seeing the same 'error' message under reports. But so far pathauto is working. My first Drupal 8 build so will be watching these types of things closely. While it may not effect site, would be great to resolve.
Comment #11
alexpottWe should take of this on install and uninstall of pathauto. Having a warning in the UI that looks really ominous but the user can't do anything about is a bad idea.
Comment #14
alexpottI've just added a test to #2673628: Ignore field definition removals/additions from fields with custom storage - I think that is the correct fix here. #11 is complex and specific to pathauto.
Comment #15
Primajin commentedI have a total fresh Drupal 8.1.0 installation with this issue. Running
drush entity-updatesgives me:However the Error still shows up, like nothing happened?
Comment #16
2pharunning
removed the error on the status page for me,
Drupal 8.1.0
Pathauto 8.x-1.0-alpha3
Comment #17
drupalfan2 commentedHow can I get rid of this error message
Error: Mismatched entity and/or field definitionswithout using drush?
Comment #18
michèle commented@DrupalFan2
Here is a solution which works perfectly for me without using drush:
https://www.drupal.org/node/2601762#comment-10835098
Comment #19
fomenkoandrey commented8.1.0 i have this error + beta3 version has fatal error with tokens in taxonomy.
Is it possible to fix these errors without drush (doesnt use it) and temporary hacks?
Comment #20
drupalfan2 commentedThank you, #18 works.
Comment #21
f0ns commentedRunning
drush entity-updatesFixed this issue for me! Thanks!
Comment #22
fomenkoandrey commentederror will be corrected in the module? or in the core of Drupal?
Comment #23
stefan.r commentedIs there a core issue for this?
Comment #24
pingers commentedJust a re-roll of alexpott's #11 patch to account for update hook increment.
Comment #26
pingers commentedSorry for the noise. Same patch... a coding standards patch went in and the previous patch no longer applies. Doh!
Comment #27
kristiaanvandeneynde@stefan.r: See these related core issues:
Comment #28
cheans commented#18 @Michèle Thanks for share. It works for me.
Comment #29
berdir#2539634: PathItem::delete() never runs because the path field type is a computed field in disguise has been committed today to Drupal 8.2. 8.2.0 will be released on October 5, 2016, and there will be no more additinal 8.1.x releases.
That means this problem will go away with 8.2 for good. Until then, ignore the error (again, this has _zero_ impact on the functionality of this module or anything else) or if you can't live with that message showing up, run drush entity-updates.
Marking this as fixed, it's more a closed (duplicate) but fixed means it's visible by default for another two weeks.
Comment #31
ilya.no commentedI have this issue with 8.x-1.5 module and 8.7.5 core. Drush doesn't seem to be an option, so I re-rolled patch with corresponding changes.