@leo-liao, we have made minor adjustments in the patch and that resolves the issue mentioned in #3. In case, if you face such issue again, feel free to create a new ticket with detailed steps, Acquia ContentHub module and Library versions.
@rodetrev, we tried reproducing the issue on 4 diff environments through multiple permutation and combinations. However, we were unable to replicate it. This appears to be a rare intermittent issue. Therefore, closing this ticket. In case if you face this issue again, feel free to create a new ticket with detailed steps and Drupal, Drush, PHP, Acquia ContentHub and ContentHub Library versions.
@leo-liao, We have gone through the description of the issue. Could you kindly clarify, what you mean by
at the subscriber site, it will break all other languages
.
We have also gone through the patch that you have shared. On analysing that patch and running multiple combinations, we found that on the subscriber side after the import, forward revisions were created for the translations of the node. Please follow the below mentioned steps to replicate the issue.
- Create a node in en language on publisher and export it.
- On subscriber import the node and translate it to fr language.
- On publisher edit the same node and again export it.
- On subscriber after importing the node, for the fr translation forward revisions were created. Although they were not set as
current revision
After applying the patch, this issue goes away. Please confirm if the intention of the patch was to address the same issue.
In 3.5.x we have excluded D11 jobs and in acquia_contenthub 3.6.x version we have already implemented the improved RCAT template and later versions will have the same implementation. Therefore, closing this ticket.