Core's StorageComparer class thinks tvi.taxonomy_vocabulary.NAME.yml is a renamed version of taxonomy.vocabulary.NAME.yml. This is caused by the fact that tvi_submit_handler sets the configuration entity's uuid to the same uuid as the vocabulary.

This isn't a problem when the tvi config is imported separately from the vocabulary config, but when they get imported together StorageComparer checks their uuids and falsely determines that one is actually a rename of the other. tvi is obviously wrong here because a config entity's uuid should be set by Drupal's config system and not by any implementing code.

The attached patch fixes this by storing the uuid under the vocabulary_uuid key.

Comments

legolasbo created an issue. See original summary.

legolasbo’s picture

Status: Active » Needs review
legolasbo’s picture

StatusFileSize
new2.7 KB

Further investigation shows that we actually don't need to store the vocabulary's uuid, because that value never gets accessed by the code.

kristiaanvandeneynde’s picture

Status: Needs review » Reviewed & tested by the community

Setting UUIDs is bad m'kay :)

star-szr’s picture

Status: Reviewed & tested by the community » Closed (duplicate)

Closing in favour of the older #2852645: tvi_submit_handler() should not copy the UUID over that has the same diff.

kristiaanvandeneynde’s picture

Could you please add legolasbo to the people receiving credit in the other issue then?

star-szr’s picture

@kristiaanvandeneynde a maintainer of this project would have to do that, feel free to comment on the other issue to ask for that.