The PostSave event does not include the value of a Block List after the deleting and creating Block List items.
Umbraco v8.8.0
The deletion of an item in a Block List followed by publishing seems to break empty Block Lists on a page.
After the deletion of a Block List item, publishing and without reloading the page, adding new items to an empty list will result in those items not being saved on the page. But the publishing event is still successful, giving the editor the impression that the content was saved to the page when in in fact - it was not. This is an issue that can result in editors loosing data.
As of now, I have found two ways to produce the error. The first way uses only one Block List property on a page, and the second uses two or more.
Tested in:
Using a clean install of Umbraco v8.8.0 with starter kit.
Block List property on Document Type "Home".Element Type containing a Textbox and add it to the newly created Block List.Document Type and go to Content and edit the page "Home".Block List property and publish the page.PostSave event does not send the correct Block List valueBlock List property value is now empty, even though last published version should contain an item.OR
Block List properties on Document Type "Home".Element Type containing a Textbox and add it to both of the newly created Block List properties.Document Type and go to Content and edit the page "Home".Block List property and publish the page.Block List, then create a new item in the second empty Block List.PostSave event does not send the correct Block List value for the second Block List.Block List property value is now empty, even though last published version should contain an item.The Block List should contain the last published item.
The Block List is empty and the PostSave event sends the following:
{"id":0,"alias":"blockList","value":""}
After deleting an item in a Block List, save the page and reload the browser.
_This item has been added to our backlog AB#8939_
Whoa. That's... weird! I can reproduce on vLatest. I'll have a look.
Thank you for a very detailed bug report โญ
Well.. this isn't exactly simple. The error is periodic. I think @nielslyngsoe should get in on this.
Fixed & merged into v8/dev an upcoming 8.10.x release
Then cherry-picked into v8/8.7 abc42b5438dd64a4b5856d0a190787d1abc18d9d and is due for 8.8.1
Most helpful comment
Fixed & merged into v8/dev an upcoming 8.10.x release
Then cherry-picked into v8/8.7 abc42b5438dd64a4b5856d0a190787d1abc18d9d and is due for 8.8.1