The properties CPT are set to ‘Translate automatically’ in WPML -> Settings. The properties were imported using WP All Import. Nevertheless, nothing happened. The properties were not automatically translated.
Solution:
Imported posts (any post type) can not get automatically translated. This is expected behavior. To get the imported posts translated automatically, you need to go to Translation Management and send the imported posts to translation.
Problem: The client is trying to synchronize the French version of their website with the English version but is encountering issues. Specifically, there are extra social media icons in the footer, a generic header message that won't update, and a news page that is not reflecting changes. Additionally, the Page Title Bar is not supposed to show up in the French version, but it does. Solution: We recommended following the steps in our documentation to ensure that the Header and Footer are translated correctly when using the Avada theme. The documentation can be found here: Translating Avada Layout Sections.
If the client is not using an Avada layout for the header, the issue might be related to setting different global options with WPML, as described in the following documentation: How to Set Different Global Options with WPML.
If these solutions do not resolve the issue, we asked the client to provide more details on how they configured the sections causing trouble, and to ensure they have a backup of their website before providing us with access to their WordPress dashboard.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we 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. If necessary, do not hesitate to open a new support ticket for further assistance: WPML Support Forum.
Problem:
We defined the language and were almost done, but we noticed that we made a mistake with the code of the language. We need to change it so that the permalink goes from this ../pt-br/ to .../pt/.
Please advise how can we correct this.
Solution:
To change the slug of the Portuguese language, we'll need to apply a workaround, which is to create a custom language with the code 'pt'. To do it, please follow these steps:
- Go to WPML -> Languages -> Site languages - > Edit Languages
- Click on the button "Add New Language"
- Add a custom language and make sure that the 'code' is set to 'pt' since this is what shows in the URL. Also, use a different default locale from pt_PT as this is already taken (you can use just pt. Screenshot: https://cdn.wpml.org/wp-content/uploads/2018/02/1516916-Screen_Shot_2018_02_13_at_3.23.21_PM_1.png)
Once the language is added, if you have already created your Portuguese content (pages/posts./etc.), you will need to go to WPML -> Translation Management to duplicate them from the original PT language to your new PT language:
- In the WPML -> Translation Management dashboard, make sure to switch the language to Portuguese, and select content that you want to duplicate
- In "2. Select translation options" duplicate them into the new PT language
After this, you can remove the old PT language in WPML -> Languages -> Site Languages -> Add / Remove languages.
Is there a way I can simplify language name e.g. EN?
Solution:
You can edit the name for each language by going to WPML → Languages and clicking on the Edit languages link. There you can change the translation of language and set what you need, for example only EN.
Problem: The client is trying to export the entire site content for external translation using XLIFF but is unable to find an option to create the package without activating a listed translator, as they are using a different one not listed. Solution: We recommend that if you're the admin of the site, you should assign yourself as both a translation manager and translator. Then, you can send translation jobs to yourself and export the XLIFF files, which you can then import back after translation. Here are the steps to follow: 1. Go to WPML > Translation Management > Translators, add yourself as a translation manager by choosing "Select an existing user and set as Translator", and then do the same to Add a Translator. 2. Send the job to translation. 3. Go to WPML > Translations and download all jobs, which will include the XLIFF files. For more detailed instructions, please refer to our article on configuring XLIFF file options.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If this doesn't resolve your issue, we 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. If you still need assistance, please don't hesitate to open a new support ticket in our support forum.
Problem: The client reported a WordPress database error related to invalid data in some tables, specifically mentioning an issue with a Jetpack plugin error message that persisted even after uninstallation. Solution: We identified that the error message contained an emoji, which might have contributed to the database issue. We removed the specific message from the database, and the error did not reappear. We recommend checking your site to confirm that the error message no longer displays. If you're experiencing similar issues, we suggest removing any special characters or emojis from database entries that could potentially cause errors.
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.
Problem: The client was unable to see the translated versions of their pages using the language switcher. The expected translations were not appearing on the website.
Solution: We recommended the client to check the following steps: 1. Ensure the language is not hidden in WPML->Languages. 2. Verify that the translation is not in the trash. 3. Confirm that the translation is published and not set as a draft. 4. Make sure the translation is 100% complete, indicated by a pencil icon next to the default language page.
Upon further investigation, we discovered that the client was using the Blog license of WPML, which does not support Translation Management and the 'translations' tab. These features are only available with the CMS version of WPML. We advised the client that to use the translation editor, which their contractor was using, they would need to upgrade to the CMS version. The link to the purchase page is https://wpml.org/purchase/.
As a temporary solution, we suggested that the client could go directly to Pages or Posts and add the translation manually, but they would not be able to use the translation editor without upgrading their license.
Please note that this solution might be irrelevant if it's outdated or not applicable to your 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 you still need assistance, please open a new support ticket at our support forum.
Problem: The client was experiencing an issue where color and image swatches were not synchronizing in the second language, and they had to add the colors and image swatches in English as well. Solution: We recommended the following steps to resolve the issue: 1. Navigate to WPML -> Settings -> Custom Term Meta Translation section. 2. Set the fields (color, image, and not_dropdown) to copy. 3. Update the attribute to copy the values. 4. Check the translated product. We also provided a video to demonstrate the steps (https://files.fm/f/63eahyjht). These steps were applied to a sandbox site and resolved the issue. We asked the client to check the product on the sandbox site to confirm if the solution works correctly (https://rare-furruco.sandbox.otgs.work/el/product/henectus-tincidunt/).
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related known issues (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 for further assistance.
Problem: The client wanted to know how to keep product titles the same across all languages without translating them when adding new products. Solution: We recommend duplicating the full product page, which will keep the product title the same in all languages. However, this approach will also duplicate the entire content of the product page, not just the title. To duplicate content, you can follow the instructions provided in our documentation: Displaying Untranslated Content on Pages in Secondary Languages.
Please note that this solution might not be relevant if it's outdated or not applicable to your case. If this doesn't solve your issue, we highly 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 you still need assistance, please open a new support ticket in the WPML support forum.
Problem: The client is experiencing an issue where the main language is Latvian, and while translating forms into English and Russian using WPML, the Gravity Form is being overwritten to English. Solution: We recommend the following steps to resolve this issue: 1. Edit the file at
$st_context = $this->get_st_context( $form['id'] );
// Cache.
$current_lang = $sitepress->get_current_language();
if ( isset( $this->current_forms[ $form['id'] ][ $current_lang ] ) ) {
return $this->current_forms[ $form['id'] ][ $current_lang ];
}
$snh = new GFML_String_Name_Helper();
$check = new \WPML\Utils\DebugBackTrace();//add this
if ( $check->is_class_function_in_call_stack( 'GFFormDisplay', 'process_form' ) ) { //add this
return $form;//add this
}//add this
$form = $this->populate_translated_values( $form, $st_context );
3. Update the form and try to reproduce the issue.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem:
The client was experiencing two issues on the WooCommerce checkout page with WPML:
1) The product title on the order-pay endpoint page was not translating to the current page language but remained in the language the order was made in.
2) On the order-received page, the permalink slug for certain variable products with multiple attributes was in the wrong language.
Solution:
We recommended the following steps:
1) Go to WooCommerce > WooCommerce Multilingual > Status and complete any missing steps.
2) Navigate to WooCommerce > WooCommerce Multilingual > Store URLs and ensure that:
- Slugs are unique and not repeated across translations.
- Translations do not have the same slug as the original language.
If these steps are completed and the issue persists, we provided a code snippet to temporarily change the order language to English, retrieve the product information, and then revert the language back to the original. The client should add this snippet to their functions.php file. (fond here: https://wpml.org/forums/topic/woocommerce-product-title-etc-on-pay-order-checkout-page-in-wrong-language/page/2/#post-10513689 )
Please note that this solution might be outdated or not applicable to your 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 necessary, please open a new support ticket with us."}
Problem: 1) The client is experiencing an issue with joining segments in translations, which requires redoing the joins every time an edit is made in the original language. 2) The client wants to preserve the URL slug in the original language for translations, but the slug is being automatically generated based on the translated title.
Solution: 1) We acknowledge the inconvenience caused by the joining segments issue and confirm that our development team is currently working on a solution. 2) To ensure the URL slug is copied from the original language, please follow these steps: - Go to WPML -> Settings -> Translated documents options -> Page URL - Select
Copy from original language if translation language uses encoded URLs
- Navigate to WPML -> Languages -> Edit languages - Set
Encode URLs
to
Yes
- Test this configuration by creating a new page and translating it to see if the issue is resolved.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your 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. Should you need further assistance, please do not hesitate to open a new support ticket. You can reach out to us through the WPML support forum.
Problem:
If you're experiencing an issue where an Elementor button points to a page and does not switch to the respective language when changing languages, staying directed at the default English language instead.
Solution:
First, ensure that the template containing the button is translated. Follow these steps:
1. Navigate to Templates -> All -> Header in your WordPress dashboard.
2. Use the translation editor to translate the header template.
After translating the header template, the button should correctly point to the translated post. For further guidance, we recommend checking our guide on translating Elementor templates.
If the button still does not work correctly after these steps, or if you encounter additional issues such as with the query loop, we suggest opening a new support ticket for each separate issue.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. We highly recommend checking related known issues on the WPML known issues page, 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.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant 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 necessary, please open a new support ticket at WPML support forum for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
