Problem: On the Hungarian version of the website, the "Contact" form, triggered by the "web akadálymentesség" button, does not respect the site's language settings upon submission. Despite all strings and pages being translated via WPML, the form behavior defaults to English, redirecting users to an English thank-you page and sending confirmation emails in English. Solution: We resolved this issue by updating the translations for the pop-up templates and ensuring that the redirect links were also translated. This adjustment now correctly reflects the Hungarian language settings on the staging site for each slide on the Hungarian homepage.
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: When an order is placed for a product with variations, different variations appear for the customer and the shop admin. For example, a customer orders a product with the color 'Medium', but the shop admin sees 'Light', and the variation ID is different. Solution: The cause for this problem appeared to be that those products were earlier translated with the Classic Translation Editor and the order of the attributes was not repsected when creating the translation. 1) Set the translation method to Classic Translation Editor at WPML > Settings. 2) Update the product's translation using the Classic Translation Editor. 3) Switch the translation method back to Advanced Translation Editor. 4) If the issue persists, repeat the process by updating the translation in the Classic Translation Editor and then editing the original product and translating it with the Advanced Translation Editor.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client migrated their website and encountered issues with missing translations and incorrect URL settings. They also faced problems with bulk marking pages as translated and accessing translation credits. Solution: 1. We merged the old site settings with the new one, enabling the client to see available translation credits and ensuring the translation memory functions correctly. 2. To address the issue with the Advanced Translation Editor not displaying old translations, we recommended cancelling current ongoing jobs at WPML > Translation Dashboard > Jobs, then re-sending the content for translation from WPML > Translation Dashboard, assigning the job to themselves, and accessing the translation at WPML > Translations. 3. For bulk marking translations as complete, we clarified that this option is only available under the "Translate Everything Automatically" mode and suggested sending those jobs for translation from the Translation Dashboard, using automatic translation if credits are available, or translating them manually.
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.
Problem: The client was unable to assign credits to their website, but the issue resolved itself as the website was eventually added to the list. Solution: WPML must be re-registered after every website migration or after changing the domain or domain provider.
2) If the site URL is already registered, delete it from the list.
3) Now enter the site URL again. This will create a new site key.
4) Click on "Show key" and copy it.
5) Enter the key under Plugins > Add New > Commercial (tab) to re-register WPML. If WPML is still registered here, unregister it first.
We confirmed that the client successfully assigned 10,000 credits to the site on the same day they reached out. We recommended checking the credits by navigating to WPML > Translation Dashboard > Payments & Maintenance to verify their presence.
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, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, please do not hesitate to open a new support ticket.
Problem: You are experiencing issues with triplicated media files and duplicated, unlinked pages after installing WPML on your WordPress site. This occurs because WPML is currently disabled, causing all language versions to appear mixed together. Solution: To resolve the duplication issues, follow these steps: 1. Reactivate WPML to restore language-specific views for your media files and pages. 2. To remove duplicate media files or pages: - Navigate to Media → Library or Pages → All Pages. - Filter the items by language. - Delete the unwanted duplicates in bulk. For a complete removal of a language and its translations, follow this guide: How to completely remove a language from your site. If you decide to reset WPML, use the steps provided in this documentation: Deleting languages and plugin data by doing a WPML reset. Always ensure to back up your database before making changes.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. 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, please visit our support forum at WPML Support Forum.
Problem: The client wants to access the old method of translating pages by duplicating them and manually adding translations, instead of using the current Page translation interface. Solution: If you're experiencing this and wish to revert to the old way of manually handling translations, we recommend you first cancel any ongoing WPML translation jobs. To do this, navigate to WPML → Translation Dashboard and click on the Translation Jobs tab. Here, locate the specific job (page) you want to cancel and click the trash icon. Please note, you can only cancel jobs that are in the "In progress" or "pending" state; completed jobs cannot be removed as they are kept for historical tracking.
If this solution does not apply to your situation, 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 WPML support forum.
Problem: The client was experiencing a persistent error message stating 'WPML is missing some records in the languages tables' even after trying several fixes such as resetting languages, removing ghost entries, adding missing language information, fixing table collation, and updating the domain in the language switcher. Solution: We accessed the client's database and performed the following steps to resolve the issue: 1. Ran a SQL query to identify the problematic records:
SELECT * FROM `wp_options` WHERE `option_name` LIKE '%icl_admin_messages%' LIMIT 50;
2. Deleted the identified key from the database. 3. Cleared the cache and refreshed the dashboard, which removed the error notice.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 is working on translating content from the SA Slider plugin using WPML and has encountered an issue where the frontend still displays the English version of the slider, regardless of the selected language. This issue arises because the shortcode generated for each language version of the slider is different, and the correct translated version isn’t being dynamically picked up. Solution: To ensure that the correct language version of the SA Slider is displayed, the client has several options: 1) Translate the shortcode itself using the WPML Translation Editor. This involves searching for and replacing the shortcode per language and adding XML code to make this shortcode compatible. Relevant documentation can be found here: Translate custom shortcodes with WPML, Numeric value translation, How to translate links. 2) Manually edit the translated page and adjust the shortcode manually. 3) Create custom code that loads the correct slider per language, for example, a list of slider numbers and their translation pairs.
If these solutions do not resolve the issue or if the SA Slider plugin is not officially compatible with WPML, we recommend opening 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: The client is experiencing color discrepancies across different language versions of their site using the Avada Theme. In Polish and Romanian, the colors appear as blue and green instead of the intended red and yellow. Solution: We recommend setting the same theme options across all languages. To do this, navigate to the theme options screen, switch the language in the top admin bar to "All languages", and save the theme options. For detailed guidance, visit Using WPML with the Avada Theme.
Additionally, it's important to ensure that your server meets the minimum requirements for running WPML effectively. You need to increase the WordPress memory limit to at least 256 MB. You can do this by editing the
wp-config.php
file and adding the following code just before the comment '// That's all, stop editing! Happy blogging.':
define ('WP_MEMORY_LIMIT', '256M');
If your hosting provider restricts these settings, please contact them to make this change.
After making these adjustments, edit the original content, save it, and update the translations again. If the issue persists, please visit our support forum and open a new ticket for further assistance: WPML Support Forum. 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: The client subscribed to WPML to resolve an issue with their existing Polylang plugin but still faces the problem and wishes to cancel their subscription and get a refund. Solution: We advised the client to request a refund by visiting https://wpml.org/purchase/refunds/.
If this solution is not relevant due to being outdated or not applicable to your case, we recommend opening 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/forum/english-support/.
Problem: The client noticed a discrepancy in the mobile view between the English and Spanish versions of their website, specifically when viewed on actual smartphones. The Spanish version appeared to be forcing a desktop view. Solution: 1. We initially suggested clearing all site caches, which did not resolve the issue. 2. We then recommended switching to a default WordPress theme temporarily to isolate the issue, which the client could not implement due to the site being live. 3. After creating a staging site, we discovered that the page had a duplicated meta viewport declaration, which WPML translated incorrectly, causing display issues in the Spanish version. 4. We disabled the raw HTML setting in WPML > Settings and asked the client to resend the content for translation, which resolved the problem.
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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client noticed that the currency for pay-as-you-go translation services is displayed in Euros, whereas they expected it to be in Canadian dollars. Solution: We explained that WPML's pay-as-you-go translation services are currently charged in Euros, as detailed in our documentation. This is a standard practice and not an error. We also clarified that previously, the pricing was in USD, which might have caused the confusion if the client had used the service before. For more information, please refer to our documentation on automatic translation pricing: https://wpml.org/documentation/automatic-translation/automatic-translation-pricing/
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: The client set a new homepage using SiteOrigin Premium and configured it as a static page in WordPress settings. However, the new homepage does not display the layout built with SiteOrigin, showing instead the layout of the old homepage without a sidebar. Solution: We determined that the issue is not related to WPML. Here are the steps we took to diagnose the problem: 1. Temporarily deactivated WPML to ensure the issue was not related to the translation plugin. 2. Set the new homepage as a static page in the original language under Settings → Reading. 3. Found that the homepage still did not display the SiteOrigin layout, even with WPML deactivated. Since the problem persists without WPML, it suggests that the issue is related to either the theme or SiteOrigin itself. We recommend contacting SiteOrigin support for further assistance.
If this solution does not resolve your issue or seems irrelevant, we highly recommend checking 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 with us.
Problem: The client reported that the translation is showing outdated content instead of the current version, which was accurate until recently. Solution: We conducted several tests but could not replicate the issue. Here are the steps we followed: 1. Selected a product as a test case. 2. Made a minor change to the product title, updated it, and then reverted the change. This action should set the translation status to 'needs update'. 3. Opened the translation in the editor, made an update, and saved it. 4. Checked that the translations were correctly reflected on the frontend. If you're experiencing this issue, we recommend trying the above steps to see if it resolves the problem. If the issue persists, please provide the exact steps you are following so we can investigate further.
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 problem continues, please open a new support ticket at our support forum.
Problem: The client reported an urgent issue with Gravity Forms on their website, where fields that should display in English were showing Dutch translations, despite being correctly translated in the Advanced Translation Editor. Solution: 1. We first ensured that all WPML related plugins were up to date. 2. We then checked the specific fields in the Gravity Form that were displaying incorrect translations. 3. We increased the WordPress memory limit by adding the following line to the wp-config.php file:
4. We instructed the client to delete incorrectly registered strings in the WPML String Translation, re-save the form in the original language, and resend it for translation. 5. We provided steps to manually adjust the strings if needed: - Navigate to WPML -> String Translation. - Search and delete the incorrect strings. - Edit the form and add a space at the end of each string to refresh the database entry. - Use the WPML Translation Dashboard to re-translate the form.
If this solution does not resolve the 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive