My client is running with Courier 2.7.11 for Umbraco 4, on a 4.11.1 Umbraco solution.
They've got a staging (for internal pre-viewing) and production environment.
Exporting from staging seems to go fine, at least from the outside, at least no errors are shown, and the changes actually seems to be reflected on the production server.
Here comes the strange part though.
Earlier on we had the following sub structure in the tree... Document A ... Document B ... Document C ... ... Document D
Document B was, on stage, moved to Document C and some text changed, so the structure was: Document A ... Document C ... ... Document D ... ... Document B
It looked fine and was reflecting on the actual webpages.
Now, on production after export from stage by courier, the tree structure correctly reflects this structure.
But on the actual website, it is still showing the old data and structure.
At first I believed it was just the xml cache which wasn't updated, or missing publish.
But I've tried. Republishing all the elements on production, resaving and republishing, tried it from a node higher up in the structure. I've done Republish Entire Site to waste the cache. I've done an iisreset Stopped/Started the website Restarted the app pool.
Nothing works, does anyone have an idea what's wrong and what I can do?
You have my sympathy, Courier has become the "elephant in the room" for most who needed a staging server!
I'm positive somebody has posted exactly your problem, but after a quick dig through I couldn't find it. I would suggest you try digging through the Courier forum yourself.
We use Courier 2.7.3b4 on one of our Umbraco 4 projects and that doesnt seem to mess up order in any way. We've also tested 2.7.4b80 with enough success to warrant using it. Once you go past 2.7.4b80 things get very, very dicey and unless anyone else can recommend a version i'd leave the others well alone!
Rather strangely on the 13th September 2.7.8b17 appeared but I have no idea if it was posted by the core team (who are supposed to be in control now) or Per Plough who has been retired from the project to concentrate on Belle (U7).
If you want more info. on the recent decisions made about Courier 2's future go here...
Reading through your post, so just make sure, the content in the tree, in the backoffice, is deployed and looks right, but the actual website cache is out of sync and refuses to sync afterwards?
.17 appeared on the build server because I was doing some commits on a rather experimental dependency handling, which loosens the chains of the dependencies, but it is in no way tested and also why there is no mention of it anywhere.
Courier corrupting data?
Hello,
My client is running with Courier 2.7.11 for Umbraco 4, on a 4.11.1 Umbraco solution.
They've got a staging (for internal pre-viewing) and production environment.
Exporting from staging seems to go fine, at least from the outside, at least no errors are shown, and the changes actually seems to be reflected on the production server.
Here comes the strange part though.
Earlier on we had the following sub structure in the tree...
Document A
... Document B
... Document C
... ... Document D
Document B was, on stage, moved to Document C and some text changed, so the structure was:
Document A
... Document C
... ... Document D
... ... Document B
It looked fine and was reflecting on the actual webpages.
Now, on production after export from stage by courier, the tree structure correctly reflects this structure.
But on the actual website, it is still showing the old data and structure.
At first I believed it was just the xml cache which wasn't updated, or missing publish.
But I've tried.
Republishing all the elements on production, resaving and republishing, tried it from a node higher up in the structure.
I've done Republish Entire Site to waste the cache.
I've done an iisreset
Stopped/Started the website
Restarted the app pool.
Nothing works, does anyone have an idea what's wrong and what I can do?
Best regards,
Poul
Hi Poul
You have my sympathy, Courier has become the "elephant in the room" for most who needed a staging server!
I'm positive somebody has posted exactly your problem, but after a quick dig through I couldn't find it. I would suggest you try digging through the Courier forum yourself.
We use Courier 2.7.3b4 on one of our Umbraco 4 projects and that doesnt seem to mess up order in any way. We've also tested 2.7.4b80 with enough success to warrant using it. Once you go past 2.7.4b80 things get very, very dicey and unless anyone else can recommend a version i'd leave the others well alone!
Nightlies can be found here...
http://nightly.umbraco.org/UmbracoCourier/
Rather strangely on the 13th September 2.7.8b17 appeared but I have no idea if it was posted by the core team (who are supposed to be in control now) or Per Plough who has been retired from the project to concentrate on Belle (U7).
If you want more info. on the recent decisions made about Courier 2's future go here...
http://our.umbraco.org/forum/umbraco-pro/courier/41759-LOBBY-THE-UMBRACO-TEAM!!!-COURIER-IS-LETTING-UMBRACO-DOWN!!
Hi Paul
Reading through your post, so just make sure, the content in the tree, in the backoffice, is deployed and looks right, but the actual website cache is out of sync and refuses to sync afterwards?
.17 appeared on the build server because I was doing some commits on a rather experimental dependency handling, which loosens the chains of the dependencies, but it is in no way tested and also why there is no mention of it anywhere.
Latest version to use is 2.7.8.14
is working on a reply...