Hey @petervandoorn,
I will look into this one. It probably needs me to add some wrapper code here so that qTranslate knows to add the translation interface on these settings. I will try to get something together for this before the next release.
Thanks for the report, and if you find any other qTranslate-less things, let me know,
Loushou
According to the documentation, to get the fields translatable on the back end, all you need to do is add a class to the textarea or input of either i18n-multilingual or i18n-multilingual-curly. See here: https://qtranslatexteam.wordpress.com/integration/
Cheers.
Hey @petervandoorn,
This was updated in the last release, 2.2.2. It was a little more complicated than the documentation makes it out to be, but that was mainly due to the fact that we are using the WooCommerce settings page api for our settings pages, which does not play as nicely as it seems it should. In any event, the relevant fields have all been given the translation ability using qtranslate. Any of our settings pages that contain a field that can be translated on it (a couple of the pages), will have the qtranslate language switcher buttons on it.
Loushou
Ah, well in that case I have to report that it’s not working for me.
But then the settings page is a little broken as it doesn’t appear in the sidebar, but I can access it directly by its url. Maybe there’s something deeper wrong here.
I also have a problem with the settings page on my other site – it’s in the menu but the colours tab doesn’t display anything. It’s never bothered me before as I don’t use it, but thought I’d mention it since you’re saying the WC options api has issues!
Cheers
Peter
