Problem: You need to prevent languages from being displayed in the menu on your site, as you plan to go online with only the first language and add translations later. Solution: We recommend hiding the languages temporarily in WPML. You can do this by navigating to WPML > Languages > Hide languages. For more details, visit this documentation. Additionally, as an admin, you can enable the option "Display hidden languages" in your WordPress user profile. This setting allows you as the admin to see the translations on the frontend while keeping them hidden from other users.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where courses can be published without filling in all required fields when WPML is enabled. This problem does not occur when WPML is disabled. Solution: We recommend updating Advanced Custom Fields (ACF) to the latest version as a similar issue with field validation was resolved in that update. You can find more information on this update here: Advanced Custom Fields conflicts with field validation on AJAX requests. Additionally, it is not necessary to translate custom fields groups with ACFML. Therefore, you can set ACF custom fields to be not-translatable in WPML->Settings->Post types translations, which allows you to manage fields from one place rather than two. For more details on managing ACF with WPML, visit: Translate sites built with ACF.
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 open a new support ticket at WPML support forum.
Problem: If you're experiencing an error message 'jobs cannot be loaded' when trying to access page 2 of the Translation Queue or when increasing the number of items per page, it might be due to a specific item on that page causing a failure. Solution: We recommend accessing your database and running the following SQL query:
UPDATE `{wpdbPrefix}_icl_translation_status` SET `status` = 1 WHERE `status` = 2;
Make sure to replace {wpdbPrefix} with your table prefix. It's crucial to back up your database and website before proceeding. If you're unsure how to run the SQL query, please contact your hosting support for assistance.
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.
Problem: You are experiencing an issue where a popup window displays 'Review not available' when trying to accept automatically translated pages using the Traveler Theme. Solution: This problem usually occurs if the post cannot be previewed properly. To resolve this, please follow these steps: 1. Navigate to WPML → Translations. 2. Locate the post you wish to approve. 3. Approve the translation directly from there. For detailed guidance on approving translations, visit how to review automatic translations.
If this solution does not apply to your case, or if it seems outdated, 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: You have installed WPML on your website and are using FacetWP for filtering posts by 'Type of School' (Private, Public), which are ACF custom fields. Although these school types are translated in other areas, they are not appearing translated in the facet filters on the front-end. Solution: We recommend trying the workaround provided on the WPML errata page. You can find the specific instructions by visiting this page.
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 an issue where the layout of the product archive displays differently in different languages. In Dutch, only selected products (animal pictures) are displayed, while in English, all products are displayed without an option to select which ones to show. Solution: We recommended editing the product query in both the primary and secondary languages to ensure consistency across different language versions of the site. Additionally, we identified that the English language product was still in draft mode. After publishing the product, the correct items displayed on the site. We suggest checking the frontend to confirm that it displays the correct products.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please do not hesitate 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, you can visit our support forum at WPML Support Forum.
Problem: You are trying to copy custom fields created by Pods to translations for a custom post type. Despite setting the custom fields as 'Copy' and Pod Groups as 'Not translatable', the fields are not being copied to translations. Additionally, there is an error when accessing the translated post type where the link to the pdf attachment is used. Solution: First, ensure that the WPML settings for custom post types are set as 'not translatable'. If you previously set these fields as 'translatable', you need to delete all created custom fields and their groups, then recreate them with the correct WPML settings before they are created. This approach was confirmed to resolve the issue when tested. Also, check if the video URL field has been copied correctly by accessing your posts and custom post type settings in WPML.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. Additionally, it's 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 visit our support forum at WPML support forum.
Problem: You are using the Traveler theme with WPML and have encountered an issue where automatic translation stops after translating 10 pages. Additionally, you are unable to preview the translated pages. Solution: For the issue of automatic translation stopping, it appears that the translation credits available on your site might not be sufficient to translate all the content. We recommend adding more credits to your site and observing if the automatic translation resumes effectively. You can also consider using the Pay As You Go subscription, which allows you to pay for the credits used after translation without the need to preload credits. For detailed guidance, please follow the documentation on Automatic Translation Pricing.
If this solution does not resolve your issues 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 open a new support ticket at WPML Support Forum.
Problem: The client is experiencing an issue with missing credits after migrating their site. They are unable to find previously purchased credits for their website and have concerns about credit allocation across multiple sites. Solution: 1. We advised the client to create a new sitekey and activate it for the migrated site. This is necessary due to the site migration or restoration from a backup. 2. To allocate or share credits between sites, the client should follow the documentation on how to manage automatic translation credits across multiple sites:
3. If the client wishes to move credits back to their WPML.org account, they can do so by accessing the admin area of the connected sites or by deleting sitekeys from their WPML account page. 4. After moving the site instance, the client should recheck their credits in the WPML > Translation Management > Tools tab and ensure the site is registered with a new sitekey.
If these steps do not resolve the issue or if the information provided here is 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 open a new support ticket at WPML support forum.
Problem: The client is unable to translate the footer designed with Divi Theme Builder using WPML. The footer appears untranslated in the English version even after attempting direct translation in the Divi Theme Builder and using WPML's translation tools. Solution: 1. Open the Footer template for editing by navigating to the specific post in the WordPress admin area. 2. Make a minor change in the template to refresh the translation settings. 3. Update the template. 4. Update the translation using the WPML Advanced Translation Editor. 5. Visit the English homepage to see the changes.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific 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: If you're experiencing issues where Polish language filter titles appear on the English version of your site, as seen here: https://romanskanieruchomosci.com/en/properties/, this might be due to untranslated placeholders in Elementor. Solution: We recommend that you edit the English archive template using Elementor and manually translate the placeholders. This should resolve the issue of language discrepancies on your multilingual site.
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 persists, please open a new support ticket.
Problem: You are experiencing an issue where non-English dashboards (My Account page) lose the side menu on your WooCommerce site, using Flatsome theme, after setting up new languages with WPML.
Solution: We recommend the following steps to resolve this issue: 1. Open the 'my-account' page in the default language for editing. 2. From the sidebar, select the page template to "WooCommerce - My Account". 3. Save the changes. 4. Clear the caches and check the frontend.
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 these steps not resolve the issue, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to enable automatic translation for products in WooCommerce using WPML, but you can't select the product for automatic translation. Solution: First, check if the WPML Translation Editor is selected in the language metabox of the product editor when editing the product. If this does not resolve the issue, it might be due to an ACF field group with specific preferences that are preventing it from being enabled. In this case, edit the ACF field group and set the translation preferences to "expert".
If the solution provided here is outdated or does not apply 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 open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with WPML's multi-currency settings and the Yoast plugin displaying abnormally on your product page, it might be due to a compatibility issue. Solution: We recommend following these steps to resolve the issue: 1) Visit the WPML>>Languages>>Language switcher options in your site's admin area. 2) Add the following CSS code to the *Additional CSS* field:
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 for further assistance.
Problem: The client is experiencing issues with some strings in the footer not being translated into English, despite being correctly translated in the backend. Solution: We have translated the footer options and pointed them to the correct template ID. We recommend checking the updated translations by visiting the WPML String Translation page at WPML String Translation.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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, you can also contact our support team directly at WPML Support Forum.
Questa pagina include i ticket di assistenza risolti e documentati. Stai cercando dei biglietti che sono “in corso”? Visita l’archivio completo dei biglietti di assistenza
