How do you all handle updates to several pages that are not meant to go live yet. IE existing pages that contain press releases, new product information, company news etc. We want to have these pages ready to go live but not live when we hit ’save.
Note: these are existing published pages that are due to be updated.
-
MODX Staff
- 10,725 Posts
Duplicating the Resource (or a sub-tree of Resources) into a temporary location is a typical workflow, then you can unpublish the existing Resources and replace with the new ones when ready by moving it into place and publishing it. Not optimal, but until we have versioning and more workflow options in the core, that is likely your best approach. That or working on a local or staging server and reproducing the changes to go live.
That seems like a reasonable work around but if we duplicate a number of resources, make the changes to those pages and ’replace’ the ’old’ resources, wont we have to do quite a bit of relinking where current pages are linking to the [~oldpages~] which are no longer in use?
When you mention working on a staging server, are you talking of having 2 ModX installs. 1 LIVE and 1 STAGE. Do you then somehow synchronise the databases or whats the setup? Sounds interesting.
