The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.When switching from a default display to a field level display, the UUID of the display is not changed. This means that subsequent IPE edits have the same UUID as the default and will show the in-progress edits of the specific node on every change until "save as custom" is clicked again.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2701349-2.patch | 768 bytes | eclipsegc |
Comments
Comment #2
eclipsegc commentedCODE!
Comment #3
dsnopekThanks! Just looking at the patch, that looks good. If we can get someone to independently test this and RTBC, that'd be amazing. :-) Otherwise, I'll try to find some time to test it myself later.
Comment #4
dsnopekWe have a similar bug in the D7 version: #2577031: Duplicated UUIDs after panelizer page override for specific node from node type template
I didn't mean to port the bugs too :-)
Comment #5
damienmckenna@dnsopek: :p Should this have tests too?
Comment #6
dsnopekOh, yeah, it'd be great if this had tests!
Comment #7
phenaproximaThis patch has been in Lightning since forever and it hasn't broken anything for us :) That hopefully qualifies as RTBC, but tests would be good. I'm willing to write those if someone will give me some guidance.
Comment #9
damienmckennaLets commit this and move the tests into a new issue: #2833728: Tests for generating new UUIDs for displays when switching from default to field storage
@phenaproxima: Can you please work on that one?