We have set some content on Site A to publish in the future, say a day away, but when we transfer it with Courier to site B, it publishes right away on site B. Is that something Courier is not able to handle, or a bug? Anyone tried this?
It should normally respect this, since it transfers the publishing time, and should do a check before any content is published (in the same way umbraco does it normally)
On site b, can you see the publishing time transfered? and is it simply marked as published in the backoffice, or also put into the site cache?
Finally, what version are you using, so I can log the bug
Does Courier respect publishing times?
We have set some content on Site A to publish in the future, say a day away, but when we transfer it with Courier to site B, it publishes right away on site B. Is that something Courier is not able to handle, or a bug? Anyone tried this?
Thanks!
It should normally respect this, since it transfers the publishing time, and should do a check before any content is published (in the same way umbraco does it normally)
On site b, can you see the publishing time transfered? and is it simply marked as published in the backoffice, or also put into the site cache?
Finally, what version are you using, so I can log the bug
Hi Per,
We needed to publish a new press release on the site, so the node had not yet been created and needed to publish at 3AM EST.
After some process testing, here is what we have learned:
1. Fully publish the node on the staging site. Use the umbracoNaviHide Property to keep it out of the normal navigation of the site if necessary.
2. Courier that to the production site.
3. Unpublish the node on staging, set the publishing time and courier again to the production site (uncheck hide from Nav if needed).
4. Profit. That series of steps worked for us and the node published at the correct time!
Thanks,
Ben
is working on a reply...