Closed (fixed)
Project:
Drupal core
Version:
11.x-dev
Component:
default content system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jul 2024 at 20:35 UTC
Updated:
1 Dec 2025 at 15:24 UTC
Jump to comment: Most recent
Comments
Comment #2
thejimbirch commentedComment #3
phenaproximaI'm not clear on what the benefit of doing this would be...? Could that be fleshed out a bit in the issue summary?
Comment #4
geek-merlin@phenaproxima Seriously?? It's one of a gazillion "update copied code like the original" issues. Did you read the linked original?
Comment #5
phenaproximaI had not! Thanks for the pointed reminder. :)
That rationale makes sense, although default content is never "syncing" as such. It's always getting created anew; we're always calling
enforceIsNew(). It's a weirdly named method, frankly.But I think I can see the benefit and purpose here. It won't harm anything.
Comment #7
phenaproximaOne-line change and an extremely easy-to-write test, thanks to https://www.drupal.org/node/3553794!
Comment #8
geek-merlin@phenaproxima: Glad you understood my surprise ;-)
And thanks for the hooks-in-tests pointer, this is a life-saver!
And yes, "syncing" is an odd-nomer. See also #3057483: Better describe how SynchronizableInterface should be used for content entities.
Comment #9
geek-merlinCode is straightforward. Test is green. Test-only breaks the way expected.
Get it in!
Comment #10
alexpottCommitted and pushed e7d3637a19d to 11.x and 24c74c20b50 to 11.3.x. Thanks!
Comment #14
alexpott