Ok, now i'm sort if a bind.

I had upgraded to 2.7.3.9 recently as with the 2.7.2.x version when publishing content that called macro's and passed in contentPicker of MediaCurrent parameters then would not work.  That problem was fixed but now on the 2.7.3.9 If i try to deploy templates they just seam to hang, and futher more some of the dependent images get overwritten on the destination with 0 byte files.

So I updated to the RC today but I have found a feature missing.  I used to be able to selet the dependency level to deploy.  For example when I am reploying a page I don't want to have to deploy the template with it as that template bay have unapproved changes in it.  Also if I try to reploy template with links to other pages it is trying to reploy everything.  Basicly it is doing a "Deploy and all dependencies" not and the option is gone to just deploy with only directly dependent resources(images).  I don't seeany way ton controll this in the config or bring the option back but in out system its a required function.

Or alternatly if there is some version before the RC that will properly translate marco parameters and properties that point to content items...

Accutly the problem on 2.7.3.9 is more serious.  After deploying css or template files then dont update and get io-locked by the .net process.  This was working before I'm sure of it....

Thanks for the input jeremy, will make sure you can toggle the dependency level setting in a build early next week

for clearification, does the RC also lock files, or was this only on the 2.7.3.9 ? 

Yes but I think it might be related to some other problem as it happens on many different builds.

I send a few bug submission on the courier contact page yesterday as well.  I'm not sure if there is some other problem on my end though As I am getting some odd proglems with teplates.  I reverted the RC becosue of the other issue  as for the file lockup, it seams that the courier process that is processing and transfering it doesn't let it go right away, but after a minute or so then I can write to it just fine.  

(The problems I am having appere to be with the template comparison/uniqueID lookups when the file is couriered.  This was working at some point on some release so thus I mention that I'm not sure if the problem is something in my local database? or something hanging in the courier process.  That I am guessing is the cause of the file IO problem.)

Latest Nightly of 2.7.3 contains an updated log4net.dll which is needed for Umbraco 4.10, so no changes besides that, but if you wish to run courier on 4.10, then you need the Nightly 2.7.3.26 release:

http://nightly.umbraco.org/UmbracoCourier/2.7.3/nightly%20builds/Courier_2.7.3_2.7.3.26_hotfix.zip

http://nightly.umbraco.org/UmbracoCourier/2.7.3/nightly%20builds/Courier_2.7.3_2.7.3.26.zip

@jeremym thanks for the info, will look into that file locking

Hi Per,

Will Courier 2.7.3 also fix the issue with DAMP ?

greetings,

Anthony

Hi Per,

Is there updated Courier API documentation that we can use ?

Most of the examples on the support page use depricated functions (ExtractionManger ...)

We need to implement some event handling on the live site because of published data that is not showing.

Regards,

Olaf

Any idea when the RC will be updated to being Stable? Also, is there an RSS feed I can subscribe to to get notifications on Courier updates?

Hi Per,

Same question as Sam, and also wondering if this release is fully compatible with Umbraco v4.10 ?

Thanks,

Lennart

According to this, http://umbraco.codeplex.com/releases/view/91737, it looks like this release of courier is supposed to be compatible.

I installed 2.7.3.25 and the hotfix. on my Umbraco 4.10.0 website. Got an YSOD complaining about log4net.dll

After copying log4net.dll from umbraco.core the YSOD was fixed, but I'm not able to transfer data from my test to my staging server. I get the following error:

error:Umbraco.Courier.Core.ProviderException: No provider with id 'e0472598-e73b-11df-9492-0800200c9a67' found at Umbraco.Courier.Core.ProviderCollection`1.GetProvider(Guid id) at Umbraco.Courier.Core.ProviderModel.RepositoryProviderCollection.get_Default() at Umbraco.Courier.Core.Packaging.RevisionPackaging..ctor(String revision) at Umbraco.Courier.Core.Tasks.PackagingTask.Run() at Umbraco.Courier.Core.TaskManager.#Lb(IRevisionTask value) 9/11/2012 15:16:53

The Courier version on my staging server is not updated to Courier 2.7.3 rc.

Should both versions be the same?

greetings,
Anthony

@Anthony, had the same issue, its build/hotfix 26 you need (you can also find a link in this thread)

Grtz

L

@Lennart Oh I see. I think, I'll wait to upgrade my Umbraco 4.9.1 website to 4.10.0 untill this Courier issue is fixed.

thanks,

Anthony

just upgraded with build/hotfix 26

now I get this error message when trying to transfer an update

System.NullReferenceException: Object reference not set to an instance of an object. 
at Umbraco.Courier.Core.Repository.get_Provider() 
at Umbraco.Courier.Core.Repository.#ad(XmlNode settingsXml) 
at Umbraco.Courier.Core.Storage.RepositoryStorage.GetAll() 
at Umbraco.Courier.UI.Dialogs.CommitItem.OnInit(EventArgs e) 
at System.Web.UI.Control.InitRecursive(Control namingContainer) 
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

greetings,

Anthony

is working on a reply...