Problem:
Translations not showing in Jet engine CPT admin column.
Solution:
When creating a CPT make sure to enable relevant setting for admin columns and then make sure to turn it on from Screen Options in CPTs listing screen.
1- Go to WPML-> Theme and plugins localization, select your theme/plugin, and scan
2- Go to WPML-> String Translation
3- Scroll down and click on the "Translate texts in admin screens »" link
4- Search for the needed strings
5- Select the strings
6- Click on the "Add to String Translation" button
7- Then click on the "« Return to String Translation" link
8- Translate the strings, clear the cache, and check the front end
Problem: After removing a custom language (UK) from the site, attempting to open the translation interface for translating English (EN) posts into German (DE) results in a 500 error with a message indicating an issue with an 'InvalidArgumentException' in the WPML plugin. Solution: 1. Check if you are using the Advanced Custom Fields (ACF) plugin, as the issue might be related to a known problem with WPML. If so, follow the workaround provided in the WPML errata page: WPML Errata. Remember to backup your database before making any changes. 2. If the issue persists, it may be due to the configuration of language pairs with the custom language that no longer exists. To fix this, go to WPML → Translation Management → Translators and remove the translator. Then, add the translator back again.
If this solution does not seem relevant to your issue, please open a new support ticket with us for further assistance.
Problem: In a WooCommerce project, when the client places an order in Arabic language and then goes to the 'my-account' section to view the order details, the date is not translated into Arabic. Solution: We recommend translating the date format by following our documentation on Translating Your Site’s Date Format Using WPML.
If the correct string for the date format is not found, you should check for additional date format strings. This might be necessary if your theme has its own options for date and time formats. In such cases, the date format might not change on the front-end when you try to change it using the usual steps. To find these strings, go to WPML → String Translation and select your theme from the 'In domain' dropdown.
Problem:
I have a from that I can submit in EN but not in ES and FR. I mean that in EN, the form response is stored in the DB and I receive a notification. With the other languages, nothing happen when I submit the form.
here is the link to the contact form in EN: https://staging2.notionb2b.com/contact/
You can swith to another language in the same page.
Solution:
You need to use the drop down to switch to French and then you will see the French entries.
Problem: You want to make your client's site ADA compliant and are inquiring how WPML handles ADA compliance, particularly if WPML can automatically translate pages, media, forms, etc., for ADA, or if you need to manage English and Spanish pages separately. Solution: If the plugins you're using for ADA compliance are compatible with WPML, or if their strings are registered with WPML String Translation, then you can use WPML's 'translate everything' feature to automatically translate the strings. This applies to page content as well. For forms and widgets, the translation will depend on your site's setup. We recommend checking the compatibility of your ADA plugins/widgets with WPML on our tested compatible plugins list. If you need further assistance, please provide screenshots of your backend or information about specific plugins, and we will be happy to help.
Problem: If you're experiencing issues with disconnecting translations from the default language page or post after updating to WPML version 4.6.7, where the entry of the disconnected element is not removed from the
Solution: We recommend updating to the latest WPML version (4.6.8), which should resolve this issue. Please ensure you have a full backup of your site before proceeding with the update. If this solution does not seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
Problem:
Trying to translate content does not show changes on frontend.
Solution:
When you are using Theme Builder layouts and make changes using Divi builder, make sure to translate the templates included in the layout via WPML -> Translation Management or Divi -> Divi Library.
Problem: The client is manually translating a site that uses Elementor and wants to ensure that their method of translating pages using WPML manual translation and then editing with Elementor does not cause any issues. Solution: We confirmed that the client's approach to manual translation is appropriate. It is important to translate each page independently to prevent the translated pages from syncing with the default language page, which would result in manual translations being overwritten by any updates to the default page. We provided a link to the documentation for translating pages independently: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/#:~:text=Translate%20independently. Additionally, we advised the client to consistently use the same method for translation to avoid any potential issues.
Problem:
Client is unable to add products to the automatic translation queue on their WooCommerce site, which is being translated from Dutch to English using WPML's automatic translations with pay-as-you-go. The issue was specifically was with product post type belongs to WooCommerce.
Despite running the first batch of automatic translations, WPML indicates 'No translations in the queue', and the products remain untranslated as indicated by the '+' symbols in the English column on the WooCommerce page.
Solution:
We recommend the following steps to resolve the issue:
1. Navigate to WPML -> Support -> Troubleshooting.
2. Run the troubleshooting functions one by one. For guidance, refer to this screenshot: https://prnt.sc/a1Ol7gTCRHc9.
3. Update the default product.
4. Update the translation.
If the issue persists:
1. Go to WPML => Translation Management.
2. Filter the list by the "product" post type.
3. Select multiple products.
4. Choose the "Translate automatically" option.
5. Click on the "Start translating" button.
For more information on automatically translating multiple translation jobs in bulk, visit these documentation pages:
Problem:
This client mentioned that his WooCommerce emails weren't translated even if followed our documentation.
Solution:
In fact the client translated correctly the emails, and they were working correctly too. So no issue here.
But he was using a preview plugin and in order to see the preview in the secondary language, you need to switch your profile language first.
"The preview email plugin that you're using base the preview on your profile language. If my profile is set to English I'll see the English version of the email. However if I switch my profile to Croatian, I will get the Croatian preview."
Problem: The client is experiencing redirects to the WordPress plugins manager page and is unable to change settings in Elementor for the Czech version of their site after changing the language URL format to "different language per domain". Solution: We recognize this as a Cross-Domain (CORS) issue, which occurs because Elementor and other page builders restrict access to their interface from different domains unless logged in to that specific domain. To resolve this, the client needs to log in to the wp-admin on the domain where they are trying to use Elementor. Additionally, we recommend enabling the "Auto sign-in and sign-out users from all domains" option in WPML under WPML --> Languages > Language URL format. Here is a step-by-step guide: 1. Log in to the wp-admin of the domain where Elementor needs to be accessed. 2. Go to WPML --> Languages > Language URL format. 3. Activate the "Auto sign-in and sign-out users from all domains" option. For more details, please refer to our documentation: How to use WPML with different domains per language. If this solution does not resolve the issue, we invite the client to open a new support ticket for further assistance: Contact WPML Support.
Problem: The client is experiencing an issue where translations disappear in the Advanced Translation Editor (ATE) when trying to edit the translated version of a page that was modified in the original language. This issue does not occur when translating new pages, only with pages that were translated a long time ago. The workaround of inserting
in the wp-config.php file did not resolve the problem. Solution: We recommend manually copying the translations from the native WordPress editor and saving them in ATE. This is necessary because the translations were likely added using the native WordPress editor, and ATE does not automatically synchronize with it.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive