Problem: You are trying to generate a sitemap for your website using WPML, but the sitemap_index.xml file is only available in the original language ("pt") and not in the translated languages ("en" and "fr"). Solution: If you're experiencing this issue, it's important to note that your site uses different directories per language as the language URL structure. In this scenario, you will have one sitemap that includes all languages. You can only have a separate sitemap per language if your site uses a different domain per language. For example:
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.
Problem:
I have two questions:
1 - I translated a page created with Porto template builder with automatic translation, but there are fields that were not translated. I had to manually translate them myself.
2 - I was charged $0.92 for the translation of a single page, which is too expensive. I need to automatically translate about 200 identical pages, but I don't want to pay around $180. I need help optimizing the translations to reduce the cost.
Solution:
1- To fix the untranslated fields, you need to register the custom fields in the XML configuration file. You can follow the step-by-step guide provided in this documentation: [link to documentation]
2- For the pricing issue, I recommend changing the translation engine from DeepL to Microsoft Translation Engine, as it costs only 1 credit per word compared to 2 credits per word. You can do this by going to WPML -> Translation Management -> Tools tab and turning off the engines you don't want to use.
