Problem your going to run into is that courier is replicating identicaly the state of content. That is if you have a document that is sent toe publication and then approved on the staging system when it is pushed to production with Courier it will be published on production. I suppose you could NOT puclish the changes on staging and push that to production the then the problem is viewing the Stagin site will not show you a staging version or the site. IE you wouldn't be seeing all the approved changes on staging but rather the original version of the site. If changes are never publihed on staging they will never show up when trying to review the site, you would literaly have to go to every page in umbraco and do a Preview to view them and links would not work. Furthermore you can push the published/approved changes from production back to staging becouse then you will start overwritting new work/changes with approvals from previouse edits. Items are not merged on a deplyment but replaced.
It would be possible to edit, set for approval, and have approver deploy the cahnges without publishing and then finnaly publish the changes on staging. But the risk of that happening in the oppisit order would be a problem as well.
3 stage Courier publishing workflow
Hi,
I'm currently prototyping some functionality using courier and I'm trying to work out how the following process will work.
There are 3 user types and 3 content stages:
Content Staging server Users 1 and 2
User 1 - Content add/edit functionality with Send to Publish functionality
User 2 - Receives notification (email) and choses whether this content should be published
Courier is then used to push the content from Content Staging to the Live Server in an unpublished state
Live Production server
User 3 - Receives a notification of content add/edit and finally signs off the content and publishes so it is now visible on the Live Server
Please could someone explain the process of configuring Umbraco/Courier to allow for this workflow.
Cheers
Problem your going to run into is that courier is replicating identicaly the state of content. That is if you have a document that is sent toe publication and then approved on the staging system when it is pushed to production with Courier it will be published on production. I suppose you could NOT puclish the changes on staging and push that to production the then the problem is viewing the Stagin site will not show you a staging version or the site. IE you wouldn't be seeing all the approved changes on staging but rather the original version of the site. If changes are never publihed on staging they will never show up when trying to review the site, you would literaly have to go to every page in umbraco and do a Preview to view them and links would not work. Furthermore you can push the published/approved changes from production back to staging becouse then you will start overwritting new work/changes with approvals from previouse edits. Items are not merged on a deplyment but replaced.
It would be possible to edit, set for approval, and have approver deploy the cahnges without publishing and then finnaly publish the changes on staging. But the risk of that happening in the oppisit order would be a problem as well.
is working on a reply...