Problem: The client was experiencing issues with content not displaying correctly after translation using WPML on their website. Specifically, a block in Blocksy content blocks was not showing correctly, and the Fluent Forms form submit button was missing from string translations. Solution: 1. We recommended checking the WPML String Translation section in the WordPress dashboard to search for any untranslated strings related to the problematic content. 2. If the strings were not listed, we suggested using the Debug info to ensure all settings were correct and that the strings were properly registered for translation. 3. For the Fluent Forms submit button, we advised ensuring that the button's string was correctly scanned and available in the String Translation interface. If not, rescanning the plugin files might be necessary.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Please also check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can contact us directly through our support forum.
Problem: You are trying to translate buttons in Elementor that link to a custom post type or other pages, using post IDs for linking. While some buttons correctly update to the translated URL, others do not, and occasionally the URL field is missing in the translation editor. Solution: Firstly, ensure that system fields like
_elementor_data
are not modified as they should remain in their default state to avoid issues. For buttons, using type="link" in Elementor should automatically direct internal links to the translated versions of the posts/pages. If these fields are set correctly, they won't appear in the Translation Editor because they are automatically configured to point to the correct translation. If the URL field does not appear in the Translation Editor, you can locate the URLs by following the steps outlined here: https://wpml.org/faq/how-to-translate-links/#translating-external-links Additionally, you can find the necessary XML for any widget automatically through this link: https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/
If this solution does not resolve your issue or seems outdated, we 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 problems persist, please open a new support ticket with us for further assistance.
Problem: If you have fully translated a page in WPML but the gear icon still appears indicating 'Translation assigned to local translator', even though the translation is 100%, this might be due to server configuration limits. Solution: First, check the 'MaxInputVars' PHP configuration on your server. It should be set to at least 1218, but your current setting is 1000. Contact your hosting provider to increase this value to at least 2000. Additionally, increase the WP MEMORY LIMIT to enhance performance. You can do this by editing the
wp-config.php
file located in your WordPress root directory. Add the following line:
define('WP_MEMORY_LIMIT', '256M');
Place it just before the comment:
// That's all, stop editing! Happy blogging.
If you're unable to make these changes yourself, we recommend contacting your hosting provider to adjust these settings.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, do not hesitate to open a new support ticket with us for further assistance.
