Problem: You have installed a plugin to translate your German website into English, but the product category is missing on the English translation page. Solution: We recommend checking the English language portfolios to see if the custom field "id_field" exists. This issue might be due to the "Order By" custom field condition not working correctly on the English language page. If the field is missing, adding it should resolve the problem.
Please note that this solution might be outdated or not applicable to your specific case. 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. If the issue persists, please open a new support ticket.
Problem: The client is experiencing issues with a 3rd party plugin widget not translating correctly. Specifically, the titles on product filters and the 'Search Products...' placeholder are not appearing in the correct language. Additionally, the client mentioned that posts set to publish when the original is published are being published prematurely. Solution: For the translation issues with the widget, we recommend duplicating the category filter and assigning the appropriate language to each duplicate. This method should help ensure that the widget displays correctly in each language. For the issue of posts being published prematurely, ensure that the 'Publish the translated post when the original is also published' option is correctly configured to match your scheduling needs.
If these solutions do not resolve your issues or if they seem 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 further assistance be needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to translate customized fields using WPML but encounters an issue where the translations do not appear on the frontend. The client used a custom hook and registered labels to WPML, translating them successfully. However, despite following documentation and using code examples, the translations are not visible on the frontend. Solution: 1. Ensure the text domain is correct. According to WordPress documentation, the text domain must use dashes, be lowercase, and have no spaces. 2. When using variables in translated strings, use the
printf()
function instead of echoing the variable directly. For example, change:
<p id="popup-title"><?= $popuptitle ?></p>
to:
<p id="popup-title"><?php echo __('Subscribe Now, Save 10%', 'storefront') ?></p>
After making these changes, re-scan the strings in the child theme, translate the string, and check if the translation displays on the frontend. 3. If using a custom text domain like "popup", register it with the following function in your theme's
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also highly suggest 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. For further assistance, please visit our support forum.
Problem: You are experiencing an issue where WPML is not translating the WPBakery Page Builder templates correctly, and the translations are not appearing on the live website despite following the documentation at https://wpml.org/documentation/plugins-compatibility/how-to-build-multilingual-sites-with-wpbakery-page-builder-and-wpml/. Solution: 1. Ensure that you are using the WPML Translation Editor to translate your content. Post types such as pages, posts, and page builder content cannot be translated directly at WPML > String Translation. 2. Go to WPML > Settings > Post Type Translation and set the WPBakery Templates to "Translatable - only show translated items". 3. Translate the templates using the WPML Translation Editor, similar to how you would translate pages and posts. If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client wants to change the URL structure to include the category slug, but only for the Norwegian language on their multilingual site. They are using WPML and currently have a different structure for Danish. Solution: We have determined that it is not possible to have different URL structures for each language when using WPML, as the content needs to be linked properly across languages. Additionally, attempting to force this change through code modifications is likely to cause issues and is not recommended.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we encourage you to open a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/.
Problem: You are trying to get the sitemaps working for all languages on your website using the WPML SEO plugin and Yoast Premium. However, sitemaps are only working for the primary language and not for other languages. Solution: We recommend checking if you are using different language domains, as this functionality is primarily available in such setups. You can find more details on this in our documentation: Using WordPress SEO with WPML. Please note that sitemap generation is managed by Yoast, not by us. If you need separate sitemaps for each language and are not using different domains, you might need to implement a custom solution, as this falls outside the standard behavior.
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. If you still need assistance, please open a new support ticket at our support forum.
