A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.
Thats pretty old version almost 5+ years back. But I do remember seeing that issue once when was testing how Service API works, although I was not using rest API but was using zip file import from service API. But I was just trying to see how it works never really digged further on that. But with the new version we have been using with Commerce 13, we do not have any such issue.
~ Sujit
Thank you, Sujit! Yes, we are on a quite old version.
It does seem like we were able to remove this unwanted behaviour by adding to test environment appsettings:
<add key="DisableVersionSync" value="true" />
However, I haven't been able to fully understand what implications setting DisableVersionSync to true.
What does this setting actually do?
After updating a product with no versions via the Service API, when viewing the product in the UI all fields are empty, except the field(s) that was changed in the PUT request to /entries/{code}.
When the product has prior versions (and exists in table ecfVersion), everything works as expected.
I tried searching through the bug list, but couldn't find anything that seemed related.
Have anyone else experienced this, or have an idea of what I might be doing wrong?