Content without uuid are generated on export, but that leads to lots of problems. UUIDs are optional, not mandatory.
Per EntityTypeInterface::getKeys documentation:
* - uuid: (optional) The name of the property that contains the universally
* unique identifier of the entity, which is used to distinctly identify
* an entity across different systems.
Ignore when the content entity doesn't provide a uuid field definition or uuid returned is empty.
Ignore entity references referencing content with empty uuid or no uuid field definition.
Review patch.
In single export and import forms, entity types not providing a UUID key are not listed.
None.
None.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 3279943-ignore-content-entities-without-uuid-3.patch | 5.16 KB | penyaskito |
Comments
Comment #2
penyaskitoAdded patch.
Comment #3
penyaskitoWe also need to ignore when calculating dependencies in entity references.
Comment #4
penyaskitoComment #5
penyaskito(edited)
Comment #6
penyaskitoSorry, commented on wrong ticket.
Comment #7
penyaskitoFor an example, I just found in Core (via @berdir) than Aggregator's Item entity doesn't define an uuid.
Comment #8
npaudyal001 commentedWhen the content entity doesn't provide a uuid field definition or uuid returned is empty and when referencing content with empty/no uuid field is defined, the entity references are ignored and the exports aren't seen for the lingotek metadata. This is tested by installing and enabling both content_sync module and lingotek tranlsation module. As a result, no exports are seen for the lingotek metadata.
Comment #9
blanca.esqueda commented