2

It seems the content synchronization module syncs entities UUIDs, but not their entity IDs (like TID, NID, etc). Since it only does UUID, this can result in environments with mismatched IDs for the same entity.

Views filters based on entities filter based on the entity ID and not the UUID.

If your deployment target ends up having different TID than your view is filtered on, it will result in it being broken or showing wrong results.

I assume we can't be the only organization using the combination of the core config sync and the content synchronization module and so I'm curious how others are dealing with this issue.

Right now we're considering just copying the database over or maybe writing a script to update the IDs in the DB.

  • I don't use that contrib module. I first play around in dev with dummy data, if necessary, to determine how I'll set it up. Then I add the real data to live as unpublished and pull down to dev. – No Sssweat Apr 16 at 4:19
  • I usually use Deploy - Content staging for this. I answered a similar question here: [drupal.stackexchange.com/questions/284491/… – Hodba Khalaf Apr 16 at 9:59
  • I had considered Deploy, but I was put off by it being beta and not updated since 2019 and it was failing tests. – fallenturtle Apr 16 at 17:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.