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
Hi,
It seems what ever we do we can't seem to force Courier to copy the relations.
Staging and Production site.
Default Relation Types: relateDocumentOnCopy
Content created/Updated/Published > Copy > Relate to original > Destination in another language > Updated/Published.
Relation created in the table on Staging.
Couriered the first one (original) Couriered the second one
Content is fine on Production, relation is not created on Production, there is not entry in the Relations table.
In courier.config the setting is as follows:
<relations> <add>relateOnCopy</add> <add>relateDocumentOnCopy</add> </relations>
The first one is there by default, we've added the second one.
The log files doesn't show any exceptions or anything unusual. Debugging is enabled.
Steps tried till now:
clientDependency version increment (files deleted and re-created)
Internal index deleted Multiple scenarios of different document types created and couriered
Updated Courier to 2.51.5 (it was 2.51.4 originally)
Tried pulling content from Production (using Update on Courier)
Checked and re-checked permissions (it's full trust for files and db_owner for database)
Much appreciated if you can help out.
Regards,
Zoran
We have the same issue with the very latest version of Courier (3.0.5) and Umbraco 7.5.6, the relations are simply not transferred. Both parent and child nodes are presented in the target database.
We have both types in courier.config
<relations> <add>relateDocumentOnCopy</add> <add>relateOnCopy</add> </relations>
By examining courier revisions folder, I can see that the relations were included into the revision file:
<Relations> <Relation> <ItemType>Item</ItemType> <RelationTypeAlias>relateDocumentOnCopy</RelationTypeAlias> <ChildId>c5e41726-6fb8-4ac2-ae18-d9e831ce6b71</ChildId> <ParentId>fbd15b4d-4a54-41c4-b992-348a76e359a6</ParentId> <DateTime>2017-02-26T14:48:18</DateTime> </Relation> <Relation> <ItemType>Item</ItemType> <RelationTypeAlias>relateDocumentOnCopy</RelationTypeAlias> <ChildId>7acbe58a-d48d-4b4f-baa6-e9331d834074</ChildId> <ParentId>fbd15b4d-4a54-41c4-b992-348a76e359a6</ParentId> <DateTime>2017-02-26T14:48:19</DateTime> </Relation> </Relations>
Any ideas?
is working on a reply...
Write your reply to:
Upload image
Image will be uploaded when post is submitted
Relations not transferred - Umbraco 7.2.8 & Courier 2.51.5
Hi,
It seems what ever we do we can't seem to force Courier to copy the relations.
Staging and Production site.
Default Relation Types: relateDocumentOnCopy
Content created/Updated/Published > Copy > Relate to original > Destination in another language > Updated/Published.
Relation created in the table on Staging.
Couriered the first one (original) Couriered the second one
Content is fine on Production, relation is not created on Production, there is not entry in the Relations table.
In courier.config the setting is as follows:
The first one is there by default, we've added the second one.
The log files doesn't show any exceptions or anything unusual. Debugging is enabled.
Steps tried till now:
clientDependency version increment (files deleted and re-created)
Internal index deleted Multiple scenarios of different document types created and couriered
Updated Courier to 2.51.5 (it was 2.51.4 originally)
Tried pulling content from Production (using Update on Courier)
Checked and re-checked permissions (it's full trust for files and
db_owner for database)
Much appreciated if you can help out.
Regards,
Zoran
We have the same issue with the very latest version of Courier (3.0.5) and Umbraco 7.5.6, the relations are simply not transferred. Both parent and child nodes are presented in the target database.
We have both types in courier.config
By examining courier revisions folder, I can see that the relations were included into the revision file:
Any ideas?
is working on a reply...