Hey everyone, we had an unusual case here related to promote and content migration.
We have some banner blocks on the store’s home page, registered through a native banner app in a workspace in production mode. When installing a new version of the code — not a major version change — the content was lost. We re-registered everything and then ran the promote. After the promote, the content simply disappeared from the site-editor, but the same banners were still showing up on the master in the front end — it only disappeared in the site-editor. When trying to add new banners in that version after running the promote, the platform simply reset all the banners on the page, not just the block we edited.
Has anyone seen this scenario before? Is it a known issue? Is there any way to work around it going forward? I ask because registering content in the workspace in production mode was pointless, since after the promote the content was lost anyway.
Hey @mica-quality, how’s it going?
We had a similar issue here in the past and discussed it in this topic: VTEX IO: qual o motivo do meu workspace mudar após outro workspace ser promovido para master?
Check if it’s the same as your case.
Hope it helps.
Cheers,
Estevão.
The problem is similar. However, there was no promote before that — just a new version published to master in the middle of the period. After the publication to master, the workspace in production mode with the new content was reset. We re-registered it and when we ran the promote, it even showed up on the front end, but it became impossible to edit in the site-editor. When editing a banner, it reset all the other blocks. Very strange behavior.
Hey @mica-quality, I see. Really strange indeed.
In any case, did you happen to have any app that changed the dependencies or the major version?
If so, did you use the mutation?
This is necessary when there’s a change in the major version in order to also migrate the content. Check it out here Migrating CMS settings after a major theme update
If you followed everything correctly, it might be worth opening a support ticket with VTEX so they can dig deeper into the issue.
Or @KarinaMota or @georgebrindeiro might be able to help here if they have any additional information.
Cheers,
Estevão.
Hey mica-quality, how’s it going?
I may not have fully understood the situation, but in the meantime, did any changes happen to those banners inside the Site Editor itself?
If so, this might be helpful:
Whenever we go to change content in the Site Editor (on the first edit) — whether it’s a banner, text, etc. — we always create a new version. Because down the line, when we do a release to master, if that changed content doesn’t have a new version, it can get lost and the release content may end up overwriting it.
Hope that helps!
Cheers.