Deploy-2.1.4 and Umbraco-7.15.7 on Umbraco-Cloud.
I have an existing doc-type and have added 2 Umbraco.DropDown.Flexible data type properties to it.
Now, when a deploy is triggered, either by pushing from local-dev, or updating from baseline-master, or by an Umbraco update, or even by a change in project membership, then the current selected value on these dropdown properties is lost on existing nodes.
Although a deploy will complete, as the site is restarting after the deploy, it then complains about missing/corrupt Examine Index:
WARN Umbraco.Web.PublishedCache.XmlPublishedCache.PublishedMediaCache - Failed (10 times) to retrieve medias from Examine index and had to load them from DB. This may indicate that the Examine index is corrupted.
The Examine internal indexer then needs to be manually rebuilt.
The data itself is not initially lost from the cmsContentXml table, but is no longer the selected value of the dropdown property, and there is no simple way to restore it.
Of course, when the admin next edits the node they don't notice and save the blank fields, resulting in full data-loss.
Curiously, there is a previously existing Umbraco.DropDown.Flexible data type property that does not lose its current selected value - suggesting perhaps an issue with array or split parsing?
I have only recently encountered this, after adding 2 Umbraco.DropDown.Flexible data type properties to the doc-type, which makes me suspect a possible recent regression of Deploy-2.x
This issue has been reproduced and acknowledged by cloud support, and I have even managed to reproduce it on a local site by triggering deploy to run locally.
This is obviously a critical data-loss situation, which can happen at any time and without warning, and is the source of much aggro from the client involved.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4