Problem: You are trying to change the default/original language for Crocoblock from English to Slovak, as some strings appear in English in Crocoblock while they are in Slovak in string translation. Solution: It is not possible to change the language of an entire plugin directly. However, you can change the source language of specific strings from the String Translation interface. To do this, follow the steps outlined in our guide on how to change the source language of strings: https://wpml.org/documentation/getting-started-guide/string-translation/how-to-change-the-source-language-of-strings/
If this solution does not apply to your case, or if it 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: https://wpml.org/forums/forum/english-support/
still exists in their database with 18M rows, even though they are using the latest version of WPML, which should not use this table. Solution: If you're experiencing this issue, we recommend that you safely remove the
icl_string_pages
table from your database as it is no longer in use. However, it is crucial to take a full site backup before proceeding with the deletion. Additionally, you can optimize database tables related to string translation through WPML>>Support>>Troubleshooting, specifically using the 'Cleanup and optimize string tables' action. For more details, please refer to our documentation on WPML Troubleshooting Options.
Please note that this solution might be irrelevant if it's 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 at WPML support forum.
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 open a new support ticket at WPML Support Forum.
Problem: You need to translate the login button on your website, but the current translation is incorrect. Solution: We recommend checking the WPML -> String Translation section to locate the button. If you cannot find it there, you may need to register the string first. For detailed instructions on how to do this, please visit our documentation: Registering strings for translation.
If this solution does not apply to your case, or if it seems outdated, 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 WPML Support Forum.
Problem: Unable to translate WooCommerce strings and the contact form on the Contact page. Solution: For translating WooCommerce strings, first, ensure you have attempted translation via WPML>>String Translation. If the strings are recognized but not available for translation, navigate to WPML>>String Translation and click on the Translate texts in admin screens » link at the bottom. Search for the missing strings in the Admin Texts Translation screen, add them for translation, and then translate. For detailed guidance, visit this documentation.
To translate Contact Form 7 forms, follow the steps in this documentation after ensuring you have backed up your site.
If this solution does not apply to your case, or if it 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 using the ATE translator to translate a blog post, but the percentage counter is stuck at 96%, even though all fields appear translated and saved. Solution: First, ensure that all fields in your translation show a green color, indicating they are fully saved and recognized. If they show a blue line, it might indicate unsaved changes. Next, check if there are any missing HTML tags in the translated sections, as these can affect the completion percentage. If the issue persists, we recommend opening a new support ticket. For further assistance, please visit our support forum at WPML Support Forum. Additionally, 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.
Problem: If you're experiencing issues with featured images not transferring when translating posts and recipes using WPML, particularly from Danish to English, and you're using the WPRM plugin. Solution: First, ensure that the Media post type is set to 'Translatable' in WPML -> Settings -> Post Types Translation. This setting should be configured to 'only show translated items'. If this setting is incorrect, it could prevent featured images from being correctly associated with translated posts. Additionally, consider installing the WPML Media Translation add-on if it's not already part of your setup, as this can help manage media elements across different languages.
If these steps do not resolve your issue, or if the solution seems outdated or not applicable to your specific case, we recommend opening a new support ticket. It's also advisable to 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, please contact us through our support forum at WPML support forum.
Problem: If you're experiencing issues when switching your website to English, such as missing parts of blocks on your homepage or changes in the menu width, it might be due to how certain fields are handled in your theme's code. Specifically, the
$person_image
field in the
wp-content/themes/hostal/pages/home.php
file may not be correctly set up for translations, leading to errors. Solution: We recommend the following steps to address this issue: 1. Adjust the Advanced Custom Fields (ACF) to ensure the field returns an image array for translations. This might require updating the translations. 2. Remove improperly set integer values in translations via SQL:
SELECT * FROM `wp_postmeta` WHERE `post_id` IN (512,459,513,456) AND `meta_key` = 'person_image';
3. Improve handling in your theme by adding code to manage different types of
If these steps do not resolve your issue, or if your theme has other similar issues, we highly recommend consulting with a professional developer. You can find qualified contractors who are familiar with WPML at https://wpml.org/contractors/.
Please note that this solution might be irrelevant if it's outdated or not applicable 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. If the issue persists, please open a new support ticket for further assistance.
Problem: The client was experiencing an issue where Elementor template stylings were only visible in the main language (German) and not in other languages (English). This problem occurred when the WPML String Translations plugin was activated, causing the stylings to not be applied in the English version of the site. Solution: The problem was identified in the way HTML code was added to the shortcode widget in the Newsletter popup at the site footer. After translating the popup template with the Advanced Translation Editor, it didn't display correctly in the frontend. We fixed the issue by replacing the shortcode widget with an HTML code widget and re-translating the popup template. This adjustment ensured that the styling in the English language matched that of the German language.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing display problems with WPML on both production and staging servers hosted on Hostinger. They are concerned about whether Hostinger is compatible with WPML and what settings or requirements are necessary to optimize WPML's performance on Hostinger. Solution: We have reviewed the WPML debug information and confirmed that the current configuration should be sufficient for WPML to function effectively on the client's site. There are no specific adjustments needed for WPML to run on Hostinger, as many users successfully use WPML on this platform without issues. It is recommended to ensure that all server settings are optimized for overall performance, which can be checked with Hostinger support. If issues such as changes not appearing on the frontend occur, it is often due to caching, and clearing Hostinger's caches usually resolves these problems. For detailed requirements for running WPML, please refer to the minimum requirements.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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. If further assistance is needed, please feel free to open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where updating the categories of a post triggers the automatic translation feature in WPML, causing already translated text to be re-translated and consuming additional credits unnecessarily. Solution: 1. Ensure that the translation memory in WPML's Advanced Translation Editor (ATE) is functioning correctly, as it should prevent re-translation of unchanged content. 2. Monitor your credit usage by navigating to WPML > Translation Management > Tools tab > Automatic translation usage reports. For more details, visit how WPML keeps track of your translations. 3. Conduct a test case: - Create a post with sample content and translate it automatically. - Capture the current used credits in WPML > Translation Management > Tools tab. - Edit the post, assign a translated category, and update the post to trigger the translation update. - Check the used credits again in WPML > Translation Management > Tools tab. 4. If the issue persists, it may be due to changes in the HTML structure of the post, which requires re-translation in ATE.
If this solution does not resolve your issue or seems irrelevant due to being 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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: The client is unable to activate the 'pay as you go' option because the 'Tools' and 'Automatic Translations' tabs are missing in the Translation Management section of the WPML dashboard. Solution: We recommend checking if the Advanced Translation Editor is active in your WPML > Settings. If the Classic Translation Editor is currently active, this could be the reason why the 'Tools' tab is not visible in WPML > Translation Management. Switching to the Advanced Translation Editor should resolve this issue.
If this solution does not apply to your situation, or if it seems outdated, please visit our known issues page and verify that you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket with us for further assistance.
Problem: The client is unable to translate a JetEngine custom post type meta field that is a subfield of another field. Despite setting the field to translate in WPML, the translations do not appear in the frontend, especially after deleting a specific field from the post type custom fields. Solution: 1. To translate the field label, navigate to WPML > String Translation. 2. To ensure the field appears in the frontend in the translated language, edit the post in the Norwegian language, select the field options, and save. This action should make the translation field visible in the frontend. 3. If a field is deleted from the post type settings, re-update the post to fix any issues in the frontend. 4. Set the field preference to "Translate" if the field needs to be translated. Manually select the field in the Norwegian language to translate it. If the field value is the same across languages, ensure the items are checked to display in the second language. 5. Alternatively, set the field preference to "Copy" to copy all checked items into the second languages, but maintain the same field value in all languages and only translate the field label.
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 the problem persists, please open a new support ticket.
Problem: The client needs to translate the login button on their website but found that the button is not translated. Solution: If you're experiencing this issue, it's important to note that there is already an open ticket regarding this problem. We recommend that you follow the existing ticket for updates and solutions here: https://wpml.org/forums/topic/need-to-translate-login-button/. Please avoid opening multiple tickets for the same issue as it can affect the processing time of your original ticket.
If the solution provided in the existing ticket does not resolve your issue or if it becomes 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 these steps not address your problem, please open a new support ticket for further assistance. You can do so here: WPML Support Forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive