Revert published content

Support
1

Hi, at the end of each month I have all our new synced content published into new content views and synced to all proxies (we have 4) ready for patching the next month

Is there a way to revert the published content that has been synced? Could I promote the older content views again to overwrite the latest or will that not work?

thanks

2

I am going to assume that with “older content views” you mean “older content view versions”. If so, then the ability to promote older versions into a lifecycle environment to achieve a roll back, is more or less the entire point of keeping old content view versions about.

In other words: Yes. You can promote any CV version (older or newer) into any lifecycle environment at any time.

3

thanks so is it best practice to promote an older content view version or to remove the current content view version from all environments? I just found that option and wonder if best and will it automatically promote the previous version

4

I would argue it depends on the reason for going back. I would always promote the older version first as it is fast and allows to analyze and test the other version, but is there a failure in the content view version you will never go back to it, so delete it. Is there some content you are just not ready to update to, but will do it later, keep it and promote it when ready.

1 Like
5

its the latter. Some machines still need to receive the older content. i will try promoting the old version today, sync, and check the machines are picking it up. If any problems, I’ll update here and consider removing latest version instead

6

this seems to have worked (at least on 1 content view)

Now in the process of syncing to all proxies which is taking a very long time but probably lots of shuffling around to do