qTranslate support

They seem to have made some changes since the last time I checked it. I have to look into this, and make it work again. But not a lot of time for that at the moment, at least not today.

You are using this one, right?

Yes, I am using the latest version of both plugins.

And yes, I tried using the newest way they have for translating:
[:en]Text[:fr]text[:]

I also tried with the HTML comment <!–:en–> …

I tried putting those directly in the input for the label in the map configuration, but when saved all the extra would just be wiped out.

There isn’t a toggle button for the language in the page either, which is the usual behaviour of qTranslateX.

I thought of doing the translation .pot file as explained for WPML in the website: https://wpstorelocator.co/document/translations/
but don’t think the same will apply for qTranslateX – or at least don’t know how it would!(?)

What I remember from the last time I used qTranslateX is that it was compatible with the WPML API and read / imported the wpml-config.xml file so you could translate the setting fields. But this now seems to require a JSON file, which isn’t there.

I have to look into why it breaks and how to get it work, but I have to take care of other issues first.

You could indeed try to make different .pot translations files yourself for each language, and see if that works. You can quickly test it by only translating one word that’s used on the front-end.