Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
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:
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.
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.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted