[Digitaleo]

Hello,

First, we have been running our support website for more than a month now and the team is very pleased with it. We have a few things we wish could be improved, so if you would like to hear our thoughts let me know who to contact.

Second, we are now starting our multilingual project. For that I am doing tests with the Polylang plugin on our development site, it is working as expected, except for the “nice_options”, the nice options links that remain in the original language, and the info boxes are not translatable. As well, we need the social media links to be different in the Spanish version.

Can you please point to me what is possible to do and what is not? We purchased Flatbase hoping the translation would be a smooth project based on reviews mentioning it worked well. Please let me know what to do to make sure we can have the best from Flatbase and Polylang working together.

Thank you in advance.

Aziliz

[Juanfra Aldasoro]

Hi Aziliz,

Thank you for writing and for your kind words.

Please feel free to send your feedback to support@nicethemes.com or here directly.

Regarding the options translations, have you tried to follow the steps described here: https://polylang.pro/doc/strings-translation/

The theme is WPML optimized, so it already has the wpml-config.xml file since version 1.0.8 (http://updates.nicethemes.com/themes/flatbase/changelog.txt)

Best,
Juan.

[Digitaleo]

Hi Juan,

Thank you for your quick reply as always. We will send an email soon.

I filled the string translation as described for every option, but they are not showing on the spanish page, only what I translated with Poedit shows in spanish.

I am going to try it out on our live website, but what will remain untranslated are the infoboxes?
Is there a way to create language specific infoboxes?

[Digitaleo]

This reply has been marked as private.

[Juanfra Aldasoro]

Hi Aziliz,

Thanks for the follow-up.

Ok, and have you contacted the polylang team asking them that the options translations don’t appear to work even when adding the wpml-config.xml file?

Best,
Juan.

[Digitaleo]

Hi Juan,

I left a message on the community forum but got no response yet.

The good thing is that we have one string that worked on the production website: the placeholder on the question field, but the others are still in the original language.

Do you have an idea on how to make it work for the infoboxes?

Thank you,
Aziliz

[Juanfra Aldasoro]

Hi Aziliz,

Thanks for the follow-up.

Info Boxes are a custom post type, you will need to enable the translations in the Polylang settings. You can read more about that in their documentation: https://polylang.pro/doc/multilingual-custom-post-types-and-taxonomies/

Best,
Juan.

[Juanfra Aldasoro]

This reply has been marked as private.

[Digitaleo]

Hi Juan,

The problem is that the info boxes are not showing in the settings, just articles and FAQ.

Do you want access to our backend to see if there would be something wrong with our install?

Thank you,
Aziliz

[Juanfra Aldasoro]

Hi Aziliz,

Thanks for the follow-up.

Yes, please.

Best,
Juan.

[Digitaleo]

This reply has been marked as private.

[Juanfra Aldasoro]

Hi Azi,

Thank you for sharing your details.

This is a polylang thing. When the custom post type is not public (Infoboxes shouldn’t be public, they don’t need to have an individual page for each one) they are not added to the polylang settings. You can check more about somebody who created an issue on their GitHub repository https://github.com/polylang/polylang/issues/11

You can try adding the following code to your theme (or child theme) functions.php file:

Best,
Juan.

[Digitaleo]

Hi Juan,

Thank you very much for this, I tested it with our test version and it works perfect!

Remains the issue with the options translation, do you have an idea for what is causing that?

Thank you,
Aziliz

[Juanfra Aldasoro]

Hi Aziliz,

Thank you for the follow-up.

I’m happy it worked. No, I’m not sure what could be happening. It is a plugin thing. We have tested the theme with WPML and ensured that it is fully compatible by including the strings to be translated in the file wpml-config.xml. The guys at polylang say that by including that file the theme is compatible. So, perhaps you can ask them why is that some strings are not already translatable.

Best,
Juan.