1. The templates don't seem to show the translation in the front-end. I've added the template 'CTA passende oplossing nodig' to the translation que and finished the translation with the advanced translation editor. But when I go to the front-end and look at the english version the translation doesn't come through, it just shows the original dutch language.
2. I've also exported and imported some translation jobs to let a translation agency translate those. Once I import them back I see that the headings are translation in the .xliff files but it also doesn't come through when I import them and look at the english pages
I see I already picked up the separate ticket about the second issue you describe, so I'll handle that in the other thread.
Regarding the issue with translating the WP Bakery template, I can see the template in the back end, I can see that it has been translated 100% into EN and DE, but I can't see where it is used on the front end.
Translations are currently disabled if your not logged-in. See the private message in the other ticket for the login credentials.
Then you will be able to go the homepage and switch to a different language in the top right corner. So for example if you switch to EN and scroll down on the homepage you will see a orange block that says: "Een passende oplossing nodig?" and on the bottom of the page above the footer you will see a contact form with text next to it.
Those two blocks are the templates that are fully translated, but doesn't show up on the front-end.
I looked into the problem of the translated templatera templates not showing on the front end as expected.
Looking at what is saved in the page content (that you cannot normally see because it is overlayed with the WPBakery UI), the templatera templates are inserted via shortcode, e.g. [templatera id="123"].
You need to add custom XML to tell WPML about these templatera shortcodes, and that the id should be automatically modified when displaying translated pages to update the id to that of the translated template.
On my own test site I did that by adding the following XML to the Custom XML tab at WPML > Settings:
