Hey,
You should see these options in the polylang string translation section. See here: https://polylang.pro/doc/strings-translation/
Let me know if that helps!
Ben
Hey Ben,
Thanks for the hint, I missed this previously, but unfortunately these elements don’t show in there. I only get blog name, blog description and a couple of widgets.
Daniel
Hi,
Can you send me a screen shot? Do you have the items setup in the customizer?
Here is a screen shot of what I see for example:
https://share.getcloudapp.com/llu9jLOp
Ben
Hi Ben,
I don’t see kadence in the string translation area and the items are setup in customizer (please see screenshots below):
https://monosnap.com/file/MlqHjWJfesvSd53zGxN720e34yysTc
https://monosnap.com/file/VUPpwHZn1D79H5I8JjCoS8yForlEF8
https://monosnap.com/file/VUPpwHZn1D79H5I8JjCoS8yForlEF8
This is my first kadence implementation so I might be missing something, but I’ve searched in the documentation and couldn’t find anything specific to this.
Thanks.
Daniel
I can’t recreate what you are seeing. Perhaps there is something not correct in the polylang settings? Have you reached out to their support?
Ben
Hi @dsecareanu,
Did you sort out the problem? I have the same issue. I am not able to choose kadence in String translation in Polylang. It simply doesn’t exist.
Jerzy
-
This reply was modified 3 years, 4 months ago by
jkozakpl.
+1 I do not see Kadence in the string translation area either.
I was able to solve this in a different way. The answer depends on the type of setting you’re trying to customize for the language.
For buttons/text in the Kadence header/footer, I used the plugin Add Polylang support for Customizer.
For Kadence Elements, I had to enable translation for the Elements content type in Polylang settings. Then I made translated versions of my Kadence Elements. Because I was using the element in the footer by placing a widget with a shortcode, the string translation area showed a widget group and I updated the Element ID in the shortcode for each language.
@k3ob and @jkozakpl
Have you made sure to assign something custom to the strings in the customizer?
can you tell me exactly what string you can’t translate?
Are you using a child theme? If so you need to add your own WPML config file because your child theme will use it’s own database entry for all customizer settings. (I would generally tell you not to use a child theme https://kadence-theme.com/knowledge-base/advanced/what-is-a-child-theme-should-i-install-one-if-so-how/)
@britner what do you mean by “assign something custom to the strings in the customizer?”
Yes, I’m using a child theme. But even when I use Kadence without child theme I can’t see Kadence in Polylang string translation. I have few elements to translate in header/footer to be translated (button text an similar).
@britner can I use original wpml config file from Kadence theme in my child theme? I tried that, but still no luck in having kadence in Polylang string translations 🙁
@k3ob will try it: Add Polylang support for Customizer, thanks.
Hey,
1. If you for example add a header button there is default “button” text and until you add custom text there the option to translate that will not show in the polylang string translations.
2. When you switch to the parent theme your customizer settings will be blank this is because theme mods are based on the theme you are using and a child theme is a different theme. If you just switch to the parent and do no set anything in the customizer that would then need to be translated you won’t see any option to translate in the string translation. This is what I mean about making sure you’ve actually set text in the customizer.
3. No you can not because the original file is based on the theme mods which are theme_mods_kadence. If you use a child theme then the theme mods change to theme_mods_{child_theme_slug} and you would need to make those changes in your WPML config file.
I hope that further clarifies.
Ben
actually, i need to show diferent header for each language, to customise the menú, the links, colors, etc
