A critical vulnerability was discovered in React Server Components (Next.js). Our Systems Remain Fully Protected. Learn More.
AI OnAI Off
proper way to backtrack published changes done in bulk
Vote:
On a site with about 100 pages and 1000+ blocks, using 10+ language branches.
Last week it was reported that multiple pages and blocks were changed (and published), from one language to another on a single language branch. This with content did not match the language branch in question (not relevant, perhaps). This happened on 50-80 blocks and pages within three minutes.
According to the version history, it was the same user that made the changes and the user supposedly was in a meeting and did not do these changes. We had to manually rollback these pages, by comparing versions on the specific language branch and re-publish them.
My suspicion was that editor in question either translated a full node (does not align fully with the version history of non-affected content) or by mistake published a Project with old content.
Either way, the editor is not so knowledgeable to work with Project in a proper way so does not quite adds up here either.
The question is if it is possible to backtrack if translation using Language module was used or publishing using Project what happened? I also tried using Reports but it does not list all pages and blocks that were affected.
CMS 12.32.4
Aug 11, 2025 11:23
Maybe not relevant, but David Knipe had a nice solution for reverting back to the previous changes for a project by taking a backup project that can then be republished to revert the changes: https://www.david-tec.com/2020/04/unpublish-content-changed-when-using-episerver-projects/.
Aug 14, 2025 17:22
