Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Roger Dunbar 9 posts 170 karma points
    Jan 04, 2017 @ 16:57
    Roger Dunbar

    Courier 3 failing with existing Document Types

    Hi Guys,

    We have recently installed the latest version of Courier (v3 I believe) and we are experiencing some strange behaviour when attempting to transfer content from once instance to another.

    Basically, if the Document Type already exists on both instances, and has not been created by Courier, when you attempt to transfer the content for a new or existing page it will always advise that it needs to create the document type, despite already existing.

    If you subsequently attempt to deploy without unticking the document types to deploy, then the Courier slide out panel simply goes blank and the deployment fails - no error message is written out to the log file regardless of whether debug mode is on or off.

    If the document type does NOT already exist on the Target instance, then once it has been created by Courier, it works as expected, i.e. it does NOT identify the need to create the document type.

    Another example is:

    1. Create new document type on Source
    2. Export document type from Source
    3. Import document type into Target
    4. Create new page using new document type on Source
    5. Right click on new page and select Courier and request to deploy to Target
    6. Courier advises that it needs to create the new document type on the Target despite already existing (it was imported in step 3 above) - and will fail if the deployment is requested.

    N.B. the same occurs if the document types are manually created OR are created using uSync.

    Apologies for the essay but has anyone seen this issue or aware of any way around this, e.g. configuring Courier so that it doesn't attempt to compare or transfer document types (because we are using uSync for that option).

    We are pretty sure this issue does NOT occur in Courier 2.5.



  • Roger Dunbar 9 posts 170 karma points
    Jan 05, 2017 @ 11:08
    Roger Dunbar

    Had some feedback from the Dev team on this and caution is most certainly required.

    Courier 3 uses the unique IDs to compare document types rather than the document type alias. Therefore any manual creation of the document types, or the use of uSync, appears to be incompatible.

    My most recent test using Courier 3 unfortunately resulted in duplicate document types, so just something to be wary of.

Please Sign in or register to post replies

Write your reply to: