You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.
On a page containing a collection and its children, if the content of the collection is updated and saved, only the first children remains visible after the save. The problem can be seen on video: https://saucelabs.com/tests/34a7d31654834f52a0fd8a790477f38f
That same issue is the reason for not returning the collections on put in createphp. Since this no longer happens this should work with current createphp master. But until now it is still unclear what goes wrong on the client side (I tried to explain this in more detail in the createphp PR ...)
@bergie can you elaborate on this maybe? or is it something that has been fixed meanwhile? or is the approach by createphp the right one, to not return anything when putting a collection?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On a page containing a collection and its children, if the content of the collection is updated and saved, only the first children remains visible after the save. The problem can be seen on video: https://saucelabs.com/tests/34a7d31654834f52a0fd8a790477f38f
The interesting part of the html contained in the http://cmf.lo/app_dev.php/en/news URL can be found here: https://gist.github.com/4556030.
The request sent to the backend URL:
The response of the backend:
It seems that only the first element of the "hasPart" attribute is rendered in the page after the "midgardstoragesavedentity" event.
CC @dbu
The text was updated successfully, but these errors were encountered: