How to renew a single Webpage without unpublishing the site for the work?

How do you renew single webpages in Revo? The problem is very often that we need the OK of our customers before we can publish a new version of a webpage but if we setup a completely new page for the time of renewal the id changes and all links on the website will be wrong after replacing the old page by the new one...

Quote from: Letti at Jan 26, 2011, 09:39 AM

How do you renew single webpages in Revo? The problem is very often that we need the OK of our customers before we can publish a new version of a webpage but if we setup a completely new page for the time of renewal the id changes and all links on the website will be wrong after replacing the old page by the new one...

You just edit the existing pages. There is currently no built-in workflow support for previewing changes to existing pages before publishing, if that’s what you are looking for.

If you’re going to consistently need a preview system, then you might as well provision the existing site into a staging MODX install, and do the changes on there before ’promoting’ to live.

A little unsatisfactory, but it does mean you always have a ’live’ backup/fallback.

Maybe you can do with Contexts?
But I will definitely say Revolution needs a native publishing-workflow feature as well as sth like the VersionX in core!

Contexts wouldn’t really save you any time, as the OP is worried about preserving URLs and ids. While you could simply drag and drop across from staging context to live, it wouldn’t help where it’s an edit to an existing page.

Other CMS systems I’ve used that used the two-context approach form a link between the two resources (staging and live) with extra functionality on the staging context (save, save and publish). It would involve some kind of on-save event to create the staging resource, then the live resource, and then store the link between the two. Then you’d need to be disciplined to only ever update the staging resource, and use the ’save and publish’ feature to promote to live. Hmm....

That’s all assuming that you don’t also want to ’stage’ chunks/snippets/TVs/Templates.... Workflow/publishing systems are complex, messy beasts for a reason.

Simpler, slower, less risky, to have two separate systems, in my view.

I thought of (mis)using the Babel plugin with contexts and have some more comfort in your described actions...

Not used Babel myself, but the principle is the same, yes. Just instead of ’English’ and ’French’ you’ve got ’Staging’ and ’Live’. Now, if only I didn’t have a shedload of work to do, I could sit around and play with that idea.....