Thank you so much for that feedback :)

if you want to give testing another go, the final tweaks on locallinks and macro discovery has been pushed to the build server and is available as 2.7.0.30 

http://nightly.umbraco.org/UmbracoCourier/2.7/nightly%20builds/

If testing on this goes as planned, it is the last build before final 2.7 release

/per

Hi Per,

I have to say that this (2.7.0.29) is by far the most successful courier version that I have tried yet (& have extensively tested over the last week or so).  We have come across a number of bugs (especially with regards to the selective packaging of items) but have managed to put workarounds in place for these.

We also had issues with locallinks but hopefully that will be sorted in 2.7.0.30.  I believe these bugs have been emailed to you.

Is there any chance of getting the packaging bugs sorted in this release? 

Thanks!!

2.7.0.30 has bombed out on us, during an attempted deploy, following comparison, during the actual installation stage:

(String folderName, String path, Revision& revision) at Umbraco.Courier.Core.Storage.RevisionStorage.GetFromDirectory(String name, String directory, Boolean lazyLoad) at Umbraco.Courier.Core.Storage.RevisionStorage.GetFromDirectory(String name, String directory) at Umbraco.Courier.RepositoryProviders.Local.GetRevision(String alias) in c:\Program Files (x86)\teamcity\buildAgent\work\b6e7862632b3bd64\Contrib\Providers\Umbraco.Courier.RepositoryProviders\Local\Local.cs:line 327 at Umbraco.Courier.Core.RepositoryProvider.GetRevision(String alias, String folder, Boolean lazyLoad) at Umbraco.Courier.Core.RepositoryProvider.GetRevision(String alias, Boolean lazyLoad) at Umbraco.Courier.Core.Extraction.RevisionExtraction.get_Revision() at Umbraco.Courier.Core.Extraction.RevisionExtraction.”[1]() at Umbraco.Courier.Core.Extraction.RevisionExtraction.PopulateGraph() at Umbraco.Courier.Core.Tasks.ExtractionTask.Run() at Umbraco.Courier.Core.TaskManager.[1](IRevisionTask value) 6/28/2012 2:18:06 PM

It also appears that 2.7.0.30 may not be outputting debug logs for us. We have <debugMode>true</debugMode>, but no log output from our attempted deployment.

Speed remains stellar, but this is a show stopper. Let me know if you need a Confidence ticket submitted. We are excited to see this working.

During a second attempted deployment of the same package, Courier completed the full operation. Quite confusing.

When navigating between packages, I have also sporadically received the following message in the right hand pane:

Index was outside the bounds of the array.

Error details

System.IndexOutOfRangeException: Index was outside the bounds of the array. 

at System.Collections.Generic.List`1.Enumerator.MoveNext() 

at Umbraco.Courier.Core.Storage.RevisionStorage.(String folderName, String path, Revision& revision) 

at Umbraco.Courier.Core.Storage.RevisionStorage.GetFromDirectory(String name, String directory, Boolean lazyLoad) 

at Umbraco.Courier.Core.Storage.RevisionStorage.GetFromDirectory(String name, String directory) 

at Umbraco.Courier.UI.Pages.ViewRevisionDetails.Page_Load(Object sender, EventArgs e) 

at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) 

at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) 

at System.EventHandler.Invoke(Object sender, EventArgs e) 

at System.Web.UI.Control.OnLoad(EventArgs e) 

at umbraco.BasePages.BasePage.OnLoad(EventArgs e) 

at Umbraco.Courier.UI.Pages.CourierBasePage.OnLoad(EventArgs e) 

at Umbraco.Courier.UI.Pages.CourierBaseLicensedPage.OnLoad(EventArgs e) 

at System.Web.UI.Control.LoadRecursive() 

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Please let us know if there are any useful details we can provide you with.

thanks for the input, been looking into the sporadic issues but nothing yet, however, guessing this also caused the failure on your initial deployment

2.7.0.30 is performing wonderfully for us.

Is it possible that a file lock might cause the above issue? We are pushing packages with ~300+ items. When quickly switching between packages, we seem to come across it most often.

Right now we have chosen to switch to 2.7.0.30 for Production deployments, following our continued testing. All of the improvements are a great accomplishment. You have made many people happy and removed a great of regular work week stress and frustration from our lives. Thanks.

Per

Eagerly awaiting this release, any news on when it will go final yet?

Si

Hi Simon

If everything goes according to plan I will push it out today or tomorrow

/Per

is working on a reply...