Is this when you're right clicking the content node and transferring, or when you create an Courier package to deploy?

Rich

Hi Mitch

Yeah, Courier will transfer the parents as well, as the page you are transfering needs them to function, so it will always do that, as the alternative is that might transfer a page that ends up nowhere as it's parent page is not present. 

If you use the right-click deploy option, you can choose advanced and tell it to not overwrite existing dependencies, so in case they are already there, it will not overwrite them

/Per

We need to include some dependancies, such as images and templates.

I think I have a solution figured out though.  I created an event handler that cancels Dependancy Documents.  It seem to be working well, it leaves non-document dependancies and children documents when selected.  What do you guys think?  Is this going to break anything?

Umbraco.Courier.Core.ExtractionManager.Instance.ExtractingItem += new EventHandler<Umbraco.Courier.Core.ItemEventArgs>(Instance_ExtractingItem);

        void Instance_ExtractingItem(object sender, Umbraco.Courier.Core.ItemEventArgs e)
        {
            if (e.Item.ItemType.ToString() == "Dependency" && e.Item.GetType().ToString() == "Umbraco.Courier.ItemProviders.Document")
            {
                e.Cancel = true;
            }
            else
            {
                
            }
        }

Any word if this works?

We are rather disapointed with this core functionality, simple users are mistakenly pushing testing content and features live and we would very much like to disable the dependancy feature.

I'm not sure if it's bug free, but it definitely works.

is working on a reply...