Nested multiple embedded content save inconsistently

[willphdavies]

http://screencast.com/t/5nF1FkdaBhj

[pajtai]

Will, can you describe this in words? I'm not getting it from looking at the screencast.
Also, might be helpful to open dev console for the screencast.

[willphdavies]

I created 4 nested items within a content type, clicked save which executed successfully, then refreshed the page and the items were not saved.

This happened a number of times until I could get it to save correctly

[pajtai]

It probably has to do with loss of focus. I believe you can see in the data being sent to the api, that the data being sent does not include the updates. This may be related / similar to a wysiwyg error that is similar.

[willphdavies]

I have no rich text fields in this object

…

On 27 December 2016 at 14:34, Peter Ajtai ***@***.***> wrote: It probably has to do with loss of focus. I believe you can see in the data being sent to the api, that the data being sent does not include the updates. This may be related to a wysiwyg error that is similar. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#45 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHip5_uYpNKfQ9V1W8V5Jy9e8Ihie2Ksks5rMZJxgaJpZM4LWhKR> .

[Duder-onomy]

My suspition is that this is the old, 'changing content title (content keypaths)' do not update recursively. This would be an issue with core. Someone was working on it then they quit. It was never completed. this is the file: https://github.com/Solid-Interactive/grasshopper-core-nodejs/blob/master/lib/middleware/contentTypes/update.js
Simple recursion.

Databinding works through keypath observation, if the keypath is incorrect, then binding will not work.
Backbone Models save using model sync. You could easily throw a debugger into that method and see what the model thinks of itself and its corresponding keypaths.
If the model is not correct, then you can look at the keypaths as described by the nested content types and ensure that each backbone plugin view is getting the right value. When we debugged issues like this in the past it was almost always an issue with what the content thinks its keypath's are and what the content type thinks they should be.

The reason that some plugins, like the WYSIWYG editor, do not work well is that they do not bind their current state. They work through 'on change' callbacks. The binding needs to be manually updated in that case. The WYSIWYG one is weird in that it will not update as you type, nor will it reliably call its own 'on update' method when you blur. There are MANY better supported WYSIWYG editors that would be a near trivial swap.