- Issue created by @cosmicdreams
- Assigned to brianperry
- πΊπΈUnited States brianperry
Don't have a solution yet, but I think I understand why this is behaving differently from the edit form. If I monitor the tempstore (the key_value_expire table) as I preview from node edit, each preview action overwrites the previous entry for that UUID. If I do the same from the node add form, each preview action gets keyed under a new UUID.
What isn't clear to me is if this is being caused by a flaw in our logic, or is a side effect of the entity not really existing until the entity is initially created.
- πΊπΈUnited States cosmicdreams Minneapolis/St. Paul
I don't think it's a flaw. The node hasn't been created yet so it hasn't been persisted with a UUID. I could route around for this but I suspect that there is logic that checks for the existence of a UUID and if one isn't found it generates a new one.
Maybe we could check the tempstore for the last inserted item
- @brianperry opened merge request.
- Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 4:46pm 26 February 2023 - πΊπΈUnited States brianperry
I was able to fix this by making the ajax callback a little more dynamic.
-
cosmicdreams β
committed 58d1cf72 on 1.0.x authored by
brianperry β
Issue #3344460 by brianperry, cosmicdreams: Make Preview override work...
-
cosmicdreams β
committed 58d1cf72 on 1.0.x authored by
brianperry β
- Status changed to Fixed
almost 2 years ago 1:04am 27 February 2023 - πΊπΈUnited States cosmicdreams Minneapolis/St. Paul
Looks good. Didn't manually test but good progress.