Since 2.7.5 the dependency handler has been updated to be less strict. Especcially around check documents connection with property data, and around allowing more details configuration of the different providers dependency settings.
Do you have some more information on "related images" ? What exactly does that cover? is it images in the rich text editor, is it media items? is it assets in the templates? it could mean alot of things
"related images" - I try and transfer a media item across.. it transfers the media item but not the associated image/file
"related images" - I try and transfer some rich text with an image associated.. it doesn't transfer the image
With regards to the related content - We transfer a node which has a single document type and template.. it then brings up uBlogsy in our list of dependencies or some random template which has nothing to do with the node
What we would ideally like is the old Courier back - i.e. it just pushes the document itself and images inside it cleanly, with no dependencies, parents etc! Our client / customers find the new interface far too confusing and complicated to feel confident using it (and we don't feel confident letting them use it). Everything other than content and media is deemed "code" which we as the developers would like to control. Doc types are tightly linked to views which we definitely do not want our customers accidentally promoting between environments.
This is why the old Courier was perfect as it was - if the docTypes were out of sync it would error out - great! We control doc types and the average marketing person who wants to create a page should not need to have to understand how they work.
BUG! Courier will not transfer related dependencies OR transfers completely unrelated dependencies
We're running 2.7.5.89.v6
We've had no end of problems and our clients are not happy to say the least.
Courier won't transfer related images etc but when transfering some simple items it'll add a whole bunch of completely unrelated dependencies.
It'd be nice to get some support on this considering it's a paid addon.
Thanks..
Hi Tom
Since 2.7.5 the dependency handler has been updated to be less strict. Especcially around check documents connection with property data, and around allowing more details configuration of the different providers dependency settings.
Info on the settings are here:
https://github.com/umbraco/Courier/blob/master/Documentation/Architecture/Provider-Configuration.md
And a list of the common issues, as well as general version upgrade info here:
https://github.com/umbraco/Courier/blob/master/Documentation/CommonIssues.md
Do you have some more information on "related images" ? What exactly does that cover? is it images in the rich text editor, is it media items? is it assets in the templates? it could mean alot of things
/per
Hi Per,
Thanks for the reply to address your questions
"related images" - I try and transfer a media item across.. it transfers the media item but not the associated image/file
"related images" - I try and transfer some rich text with an image associated.. it doesn't transfer the image
With regards to the related content - We transfer a node which has a single document type and template.. it then brings up uBlogsy in our list of dependencies or some random template which has nothing to do with the node
Cheers
What we would ideally like is the old Courier back - i.e. it just pushes the document itself and images inside it cleanly, with no dependencies, parents etc! Our client / customers find the new interface far too confusing and complicated to feel confident using it (and we don't feel confident letting them use it). Everything other than content and media is deemed "code" which we as the developers would like to control. Doc types are tightly linked to views which we definitely do not want our customers accidentally promoting between environments.
This is why the old Courier was perfect as it was - if the docTypes were out of sync it would error out - great! We control doc types and the average marketing person who wants to create a page should not need to have to understand how they work.
Would it be possible to get the old Courier back?
You're not the only one with Courier problems. Take a look here: LOBBY-THE-UMBRACO-TEAM!!!-COURIER-IS-LETTING-UMBRACO-DOWN!!
is working on a reply...