Problem: You are developing a site and using the PTC translation feature but face issues with the capitalization of all words in headlines and the literal translation of German figures of speech. Solution: We have adjusted the capitalization settings for your website. To apply these changes, please resend the pages with capitalized titles to auto-translation, ensuring that the option to overwrite existing translations is checked. After doing so, inform us about the number of pages or words you had to retranslate, so we can refund the credits you used.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your current situation, we recommend opening a new support ticket. 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is unable to see the updated footer in the German and French versions of their website. The footer, which is a global Divi element, displays an outdated version with a light background instead of the new dark background version that appears on the English page. Solution: If you're experiencing issues with global Divi elements not updating on translated pages, we recommend translating these elements from the WPML > Translation Dashboard. Here's how you can do it: 1. Navigate to WPML > Translation Dashboard. 2. Select the global elements such as the footer and send them to translation. 3. Choose "Translate myself" and then proceed to WPML > Translations to complete the translations. This approach should ensure that all global elements display correctly in all languages.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are using WPML and encountering an issue where non-translated posts are appearing on the translated Spanish archive page. Solution: If you're experiencing this, we recommend checking the WPML settings. Specifically, navigate to WPML → Settings → Post Types Translation and set it to
Translatable - only show translated items
. This setting ensures that only translated posts appear on the translated archive pages. Additionally, if the issue persists, check if the post has been duplicated. You can do this by going to Posts → All posts, switching to the secondary language, and deleting any duplicate posts.
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 problem continues, please open a new support ticket at WPML support forum.
Problem: The client experienced issues with their QA site (qa.instron.com) displaying the same credit balance as the production site after cloning and attempting to manage sitekeys and credits through WPML. Despite unregistering and re-registering the sitekey for the QA site, the credit balance remained unchanged, and the QA site disappeared from the WPML account's manage credits page. Solution: We recommended a complete refresh of the registration process to ensure proper synchronization between the QA site and the WPML account. The steps included: 1. Removing any existing QA site registrations from the WPML account. 2. Unregistering WPML from the QA site via the WordPress dashboard. 3. Generating a new site key for the QA site and registering it without assigning specific credits. 4. Verifying the credit display and site listing on the WPML account. Despite these steps, the issue persisted, indicating a deeper synchronization problem possibly related to how WPML handled the site as a 'copy' during the registration process. We then explored details of the migration wizard settings used during the process.
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 at the WPML support forum.
Problem: If you're experiencing issues with deleted templates still appearing in the 'Site Templates' list in WPML and reappearing in the WordPress backend after syncing with ATE, it's likely due to entries still present in your database. Solution: We recommend checking your database for any remaining entries related to these templates. Specifically, look for entries in
wp_posts
with titles corresponding to the deleted templates. These entries need to be manually removed from your database to ensure they no longer appear in WPML or your WordPress backend. This issue arises because WPML reflects the content available for translation based on what is present in your database, not what is currently active or visible in your WordPress backend.
Please note that this solution might be outdated or not applicable to your specific situation. If this is the case, or if you need further assistance, 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 problem persists, please open a new support ticket at WPML support forum.
Problem: You are experiencing issues with WPML translation on your site, where after translation, pages and Gutenberg blocks fall apart in the admin, and many elements like links are not saved. Solution: First, ensure that the homepage in the default language is working correctly. We have registered the missing blocks and updated the homepage in the default language, then re-translated it. We recommend you check this guide on how to make custom Gutenberg blocks translatable: https://wpml.org/documentation/support/language-configuration-files/make-custom-gutenberg-blocks-translatable/.
If this solution does not resolve your issue or seems outdated, please 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, you can contact us directly through our support forum.
Problem: The client reported an issue where user types in the dropdown menu of the registration form were not appearing in languages other than the default one. This problem occurred after an update or change, despite previously functioning correctly. Solution: We resolved the issue by restoring the translations for the admin options, which should not have been translated. This adjustment ensured that the user type selections appeared correctly in all specified languages on the registration form. If you're experiencing a similar issue, we recommend checking if any recent updates or changes might have affected the translation settings. Additionally, ensure that the translations for admin options are correctly configured and not mistakenly translated.
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 at WPML support forum for further assistance.
Problem: You are experiencing an issue where image URLs change after using WPML's automatic and manual translation features. Specifically, the year and month folder part of the URL is removed in the translated versions. Solution: This problem was due to using an outdated version of the SVG Support plugin. Updating to version 2.5.9 or higher, as confirmed by the plugin author, resolves this issue for new uploads. For images uploaded before the update, you need to re-upload them to regenerate the correct metadata. Alternatively, you can apply a specific code fix available at WPML Errata. After adding the code, update the page and its translations. If issues persist, especially with PNG images used as translations for SVGs, re-upload the original SVG and the PNG in translations.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly recommend checking related known issues at WPML 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: The client is using the Directories Pro plugin and is facing an issue where the open/close badge is only visible in the main language (Swedish) on their site, but not in Norwegian and English. Solution: We asked the client to explain how the open/close badge is set up in the main language and to provide screenshots to better understand the configuration. This information is crucial for us to diagnose the issue and provide a specific solution. However, the client later updated that with the latest update of the Directories Pro plugin, the issue was resolved, and the open/close badge started appearing correctly in all languages.
If you're experiencing a similar issue, we recommend checking if you have the latest updates for your plugins and themes. Sometimes, updates can resolve translation-related issues. If the problem persists, please visit our support forum for further assistance. 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.
Problem: If you're experiencing issues with opening the French translation editor on your website, where WPML displays an error message stating it tried to translate the page three times and failed, we can help you resolve this. Solution: 1. Open the default language Home page in Edit mode. 2. Make a small change, such as adding a space or a plus sign in your page title. 3. Update the page by pressing the “Update” button. 4. Remove the small change you made in step 2. 5. Update the page again. 6. Try to open the translated French language page in WPML Translation Editor and ensure the translation is 100% complete, then press the Complete Translation button.
If the problem persists, follow these steps: 1. Ensure you have a backup of your site. 2. Increase the WP Memory Limit to at least 128MB by adding the following line to your wp-config.php file:
3. Update WPML to the latest version, currently 4.8.5. 4. Go to WPML >> Support > Troubleshooting page and press the following buttons: - Clear the cache in WPML - Synchronize posts taxonomies - Remove ghost entries from the translation tables - Synchronize local job ids with ATE jobs - Synchronize translators and translation managers with ATE - Assign translation status to duplicated content - Fix post type assignment for translations - Set language information
If these steps do not resolve the issue, please visit the known issues page, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem still persists, we recommend opening a new support ticket. For further assistance, you can also visit our support forum.
Problem: The client was unable to translate the headline 'KONTAKT' to 'CONTACT' on the English version of their page. Solution: We discovered that the issue was related to using outdated classic elements on the contact page, which might have caused compatibility issues. Here’s how we resolved it: 1. We retained the 'Kontakt' element but removed the HTML inside it from your Classic Custom Headline. 2. We replaced the Classic Gap with a new Gap. 3. We saved the changes. 4. We completed the translations.
If this solution does not resolve your issue, or if it seems outdated, we recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: You are trying to use credits purchased for WPML, but you cannot because the WPML dashboard indicates that your website is inactive, even though the plugin on your website shows it is registered. Solution: We have resolved this issue from our end. You should now be able to use your credits. Please verify by checking if the WPML dashboard now reflects the active status of your website.
If this solution does not resolve your issue or seems outdated, we recommend checking the related 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: You are trying to add a language switcher to the menu on your website, but the switcher icon does not appear in the menu. Solution: We have identified that the issue might be due to the Avada Header (Header setro 2 – Home page – cs) not being translated into English. To resolve this, please translate the header into English by navigating to Avada > Layout Sections, and clicking the plus sign to add a translation to English.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. 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. For further assistance, please visit our support forum at WPML support forum.
Problem: The client has a site with custom post types and ACF fields, interconnected through relationship fields and displayed in grids filtered by WP Grid Builder facets. After running a bulk auto-translation for three languages, all non-ACF content translated well, but the ACF data did not appear in the translations. The fields showed 'Original: original value' but lacked actual data. Solution: We suggested that the client slightly modify a post and rerun the translator, as this approach resolved the issue when they tried it before contacting us. This indicates that the initial translation process might not have completed properly. If you're experiencing this issue, we recommend trying this step first. If the problem persists, please provide us with WordPress credentials so we can investigate directly. Ensure to follow our privacy and security guidelines when providing debug information: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/
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, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is setting up WPML for an English ecommerce store and experiencing issues when running the German translation on a separate domain. After configuring the domain to domain-name.de, products fail with a 'domain-name redirected you too many times.' error, and product categories trigger a 404 page with a strange URL. The product category structure is not correctly translated, and there is an unexpected '/e' added in the URL. Solution: We recommended deactivating all plugins except WPML, WPML Multilingual & Multicurrency for WooCommerce, and checking if the issue persists. This problem might be related to a known issue with WooCommerce Multilingual which causes too many redirects when using shop base with category permalinks. We advised the client to ensure they are using the latest version of WPML Multilingual & Multicurrency for WooCommerce, which includes a fix for this issue.
The client checked the .htaccess file and found the rewrite rules that triggered the redirect loop.
If this solution does not resolve the 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 problems persist, please open a new support ticket.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
