Replies: 3 comments 2 replies
-
Hi, The deletes should already happen at the end, but the switching of the type, will probably trigger the deletes inside Umbraco 😞 when you change a doctype that triggers all the internal events in umbraco and if a property is change umbraco updates all the content across the board. I am not sure there is much we can do about it, but i will look. |
Beta Was this translation helpful? Give feedback.
-
this is from last time we looked at it So the deletes of datatypes happen in post (which is after everything has synced). I am not sure but just changing a property from one editor to another of the same type "should't" trigger any umbraco stuff, but i wouldn't be supprised if it did. |
Beta Was this translation helpful? Give feedback.
-
ohh just found another bit. (just putting it here, so i have all the references for when i do look at). |
Beta Was this translation helpful? Give feedback.
-
Imagine a site with a number of block lists all with identical config each used by different document types.
What should happen if a change is made to swtich all the document types to use a single block list and the other datatypes are deleted.
Blocklist BWhen trying this out what appeared to happen on deployment is that the properties lost their value but ended up with correct configuration.
Is this a known limitation or a weird unexpected issue?
I'm guessing that what happened is that the deletes of the datatypes occurred before the update of the document types resulting in accidental data loss but it's just a guess.
If this is what happens would a two pass approach work where all deletes are processed on the second pass allowing for updates to take place first?
Beta Was this translation helpful? Give feedback.
All reactions