TranslatePress issue

Hi there, I’ve used this plugin on numerous sites and it’s always been brilliant. but I’ve just created a copy of a site where it works perfectly and installed TranslatePress (the new site will be a translated and adapted version for Turkish language and market.)
At present, the default language is English, the same as the original site, and the secondary language is Turkish. Right now, as I am working with a translation proofreader alongside me, we use the switcher function to change to Turkish but once done, there will be no switcher, the site will just use Turkish, the switcher won’t be available (they’ll go to the English site instead) and it will always be in Turkish.
So here is my problem. when DVforE is activated, with the switcher active, the English (default language) version loads perfectly but as soon as I switch to Turkish I just get a completely blank site – zero, zilch nada. Deactivate DVforE and eveyrthing is fine.
What I need to know is if there is a known issue – and specifically is DVforE reacting to the language being switched (ie a conflict with the TranslatePress switcher functionality code) OR is it specifically Turkish that is the problem (eg different character set or something)?
if it’s the first then maybe it will work when Turkish becomes the default and there is no switcher. If it’s TranslatePress itself or the Turkish language then is there a fix?
I can show you the feature working fine on the English site – see here Villa Star – Queen Villas Turkey the little features list with icons (air conditioning, washing machine etc.). What is happening there is that each of those items references a term from a taxonomy created with jetengine. The same tax’s and terms that are used for the sites filters. About 35 items with the name and icon (buttons in fact but not linked) exist on the template and DVforE shows/hides them according to whether the cpt post has the taxonomy term.
So really I am asking if you have any insight into why it’s not working and therefore whether it might work once we switch to Turkish as the Default language and get rid of the switcher functionality. Or maybe directly rename the taxonomies and terms into Turkish. I’m a bit desperate, I really want to keep this feature, but can’t do the default change until we are fully translated. And I can’t get JetEngine’s own Dynamic Visibility to reproduce the same effect.