SubscriberHistory does not declare uuid entity key

Created on 31 March 2025, 9 days ago

Follow-up of #3266989: Subscriber does not declare uuid entity key . The UUID is missing for SubscriberHistory entities. That leads to errors in modules that expect UUIDs, for example default_content_deploy.

🐛 Bug report
Status

Active

Version

4.0

Component

Code

Created by

🇩🇪Germany mkalkbrenner 🇩🇪

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @mkalkbrenner
  • 🇩🇪Germany mkalkbrenner 🇩🇪
  • Pipeline finished with Success
    9 days ago
    Total: 759s
    #461565
  • 🇬🇧United Kingdom adamps

    I updated the title as it's different from #3266989 - the SubscriberHistory entity currently doesn't even have a uuid field.

    I didn't put a UUID for the reason that the entity doesn't seem to identify anything concrete. Equally a revision doesn't have a UUID. I am open to changing it, but we need to make sure it doesn't have a cost for the majority of sites that don't need it.

  • 🇩🇪Germany mkalkbrenner 🇩🇪

    We import users, webform submissions and newsletter subscriptions from different sites into one backend using default_content_deploy. So we need a UUID field to avoid id collisions.

    This works well for everything except the SubscriberHistory. With that patch applied, SubscriberHistory works as well.

    But I agree that the update hook requires a batch.

Production build 0.71.5 2024