Pathauto users currently are confused by entity field definition mismatch errors appearing on the status report.
That is because pathauto has to make path fields computed. The strange part about that is that getFieldStorageDefinitions() "eats" computed fields, so it's as if it vanished.
The thing is that already in core, that field uses custom storage (actually: no storage at all). So we go from custom storage to computed.
As quickly discussed with @plach, I'm proposing to ignore any change and deletion (possibly addition too?) of fields with custom storage [in status reports].
See also SqlContentEntityStorageSchema::requiresFieldStorageSchemaChanges(), which already ignores most changes of storage definitions that has custom storage. Which makes sense, as there's absolutely nothing that it could do anyway.
Closed: outdated
11.0 🔥
It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
There has been no follow up to the prompt 2 years ago for more information. Therefor, I am closing this is as outdated.
If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue → (starting from "Install Drupal core").
Thanks!