This is the first of the Courier releases, which are split into 2 versions, to support the different database schemas between v4 and v6, however, the only real diffferences between the 2, are the different Persistence and eventhandler dlls.
Changes:
Support for V6 schema
Refactored the way it handles published/unpublished/draft content
Re-added the dependency dialog, altho moved to the second step of the dialog, by default it includes all dependencies.
Fixed a faulty media look-up so media properties failed
Since the initial fix in 2.7.3, the 0-byte file issue has not reappared
Downloads are available on the courier 2 project page, or on nightly.umbraco.org. This release is labeled 2.7.5.89
In regards to future developement, branches with work in progress will be labeled "WIP" (Thanks to Martin for the suggestion) nightly builds will still be highly untested builds, so you could get unexpected results.
I've hammered build 89 today with my 4.11.5 umbraco build and i'm very pleased (and relieved) to say that it works remarkably well!
I still have to tweak the courier.config but transfers work as expected. I have noticed on an empty site I get a cache error, but re-publishing seems to sort it out. The problem doesnt seem to continue after that.
I'll test later today in my Umbraco 6.0.2 build. Fingers crossed this product is finally making significant steps forward!
I am keen to upgrade to Umbraco 4.11 but at this time we are running Courier 2.7.1 which I believe is not supported on 4.11. I was therefore pleased to see this new release as I stayed away from 2.7.3.39 due to the 0 byte issue. However, we have a custom data resolver I am having issues with 2.7.5.89 which I downloaded today - I've had it working with 2.7.1 and earlier versions of Courier.
A summary of the issue I am having is that basically on the PackagingEvent for a document/media item I am adding the access.config or mediaaccess.config as a resource for a Protected Item:
item.Resources.Add("/App_Data/access.config");
I am then processsing the resource and changing the contents, IDs to Guids etc using the Umbraco helper methods
However I am finding once I've manipulated the file, it is not being added to the package and does not appear in the Packaged list, therefore it never hits the ExtractingResource event which is where I do the protection/unprotecting if necessary. However if I do NOT manipulate the file, it seems to be added no problem. Please note I am also changing the name and extract path as I don't want to the file overwriting the destination config.
Just in case you are wondering why I am doing this at the Item packaging level rather than for the entire deplpoyment, I am modifying the resource so it relates to the security ONLY for the item currently processed, then when I extract I only protect the node(s) been updated and not the entire security where changes may not be wanted to deployed at this stage.
However, somewhere between 2.7.1 and 2.7.5 (though I recall when I looked at 2.7.3.39 it was a problem for me but thought it possibly may be to do with the 0 byte issue) something has changed, I'm not sure if its a bug but the documentation (all be it quite old) now shows how you can replace Resource Contents in this manner so I don't believe I am doing anything out of the ordinary but I'm may be wrong :-)
Just to get an idea on how you approach this, could you post the code, if there are sensitive things in it, you can also send it directly to the suppor ticket you have opened.
If there a way to disable the new cach on publish logic, or a handeler i can use localy when a item is deployed remotly.
We currently have a bit in the DocumentItemProvider.Instance().Packaged() event that records the last deploy date of a document. I then use this on another dashboard to display all items that have published changes latter then their lsat deploy date. This isn't working now with the new versions becoue the Packaged action triggeres right after the document is published, not when a user deploys is.
Another problem. We used to remove pages from production by the following:
Unpublish the page on staging. Deploy the unpublished page. Delete the page on staging.
The deploying of the unpublished page would deploy just fine and there was code on the production side to see the unpublished document and just delete it compleatly. Now however the unpublished document just comes back and says No Changes Found when i try to deploy it. Even if I try to "Deploy Anyway" it still won't go...
Is there a way to force this page to be seen as changed and deploy even when the only change was it becomming unpublished.
Already see an issue. created a test page on our staging server (was having issues with empty files (files with size 0kb)), and added a new media item (an image). Everything copied over, but the html in my document was changed.
Staging
<p><img title="a test for courier can delete" src="/media/260659/brigbox.png" alt="a test for courier can delete" width="250" height="398" /></p>
Live
<p><img src="/media/260659/brigbox_250x398.jpg" alt="a test for courier can delete" width="250" height="398" /></p>
The img src has gained "_*width*x*height*" on it, and the ".png" was changed to a ".jpg"
Courier 2.7.5
This is the first of the Courier releases, which are split into 2 versions, to support the different database schemas between v4 and v6, however, the only real diffferences between the 2, are the different Persistence and eventhandler dlls.
Changes:
Morning Courier fans
I've hammered build 89 today with my 4.11.5 umbraco build and i'm very pleased (and relieved) to say that it works remarkably well!
I still have to tweak the courier.config but transfers work as expected. I have noticed on an empty site I get a cache error, but re-publishing seems to sort it out. The problem doesnt seem to continue after that.
I'll test later today in my Umbraco 6.0.2 build. Fingers crossed this product is finally making significant steps forward!
My confidence, hopefully restored. :-)
Congrats Per!
Martin
Hi Per
I am keen to upgrade to Umbraco 4.11 but at this time we are running Courier 2.7.1 which I believe is not supported on 4.11. I was therefore pleased to see this new release as I stayed away from 2.7.3.39 due to the 0 byte issue. However, we have a custom data resolver I am having issues with 2.7.5.89 which I downloaded today - I've had it working with 2.7.1 and earlier versions of Courier.
A summary of the issue I am having is that basically on the PackagingEvent for a document/media item I am adding the access.config or mediaaccess.config as a resource for a Protected Item:
item.Resources.Add("/App_Data/access.config");
I am then processsing the resource and changing the contents, IDs to Guids etc using the Umbraco helper methods
resource.ResourceContents = Umbraco.Courier.Core.Settings.Encoding.GetBytes(newContent);
However I am finding once I've manipulated the file, it is not being added to the package and does not appear in the Packaged list, therefore it never hits the ExtractingResource event which is where I do the protection/unprotecting if necessary. However if I do NOT manipulate the file, it seems to be added no problem. Please note I am also changing the name and extract path as I don't want to the file overwriting the destination config.
Just in case you are wondering why I am doing this at the Item packaging level rather than for the entire deplpoyment, I am modifying the resource so it relates to the security ONLY for the item currently processed, then when I extract I only protect the node(s) been updated and not the entire security where changes may not be wanted to deployed at this stage.
However, somewhere between 2.7.1 and 2.7.5 (though I recall when I looked at 2.7.3.39 it was a problem for me but thought it possibly may be to do with the 0 byte issue) something has changed, I'm not sure if its a bug but the documentation (all be it quite old) now shows how you can replace Resource Contents in this manner so I don't believe I am doing anything out of the ordinary but I'm may be wrong :-)
Any help/advice appreciated
Marie
Hi Marie
Just to get an idea on how you approach this, could you post the code, if there are sensitive things in it, you can also send it directly to the suppor ticket you have opened.
/Per
If there a way to disable the new cach on publish logic, or a handeler i can use localy when a item is deployed remotly.
We currently have a bit in the DocumentItemProvider.Instance().Packaged() event that records the last deploy date of a document. I then use this on another dashboard to display all items that have published changes latter then their lsat deploy date. This isn't working now with the new versions becoue the Packaged action triggeres right after the document is published, not when a user deploys is.
Another problem. We used to remove pages from production by the following:
Unpublish the page on staging.
Deploy the unpublished page.
Delete the page on staging.
The deploying of the unpublished page would deploy just fine and there was code on the production side to see the unpublished document and just delete it compleatly. Now however the unpublished document just comes back and says No Changes Found when i try to deploy it. Even if I try to "Deploy Anyway" it still won't go...
Is there a way to force this page to be seen as changed and deploy even when the only change was it becomming unpublished.
Hi Per,
Have just upgraded from 2.7.3 to 2.7.5.1 .
Already see an issue. created a test page on our staging server (was having issues with empty files (files with size 0kb)), and added a new media item (an image). Everything copied over, but the html in my document was changed.
Staging
<p><img title="a test for courier can delete" src="/media/260659/brigbox.png" alt="a test for courier can delete" width="250" height="398" /></p>
Live
<p><img src="/media/260659/brigbox_250x398.jpg" alt="a test for courier can delete" width="250" height="398" /></p>
The img src has gained "_*width*x*height*" on it, and the ".png" was changed to a ".jpg"
/Keith
is working on a reply...