Problem: You are translating your website using ACF for custom post types and have encountered an issue where the system automatically appends "-2" to the slug of a translated post. Solution: First, try copying the slug settings to avoid automatic changes. Navigate to WPML → Settings, scroll to Translated documents options, and select "Copy from original language if translation language uses encoded URLs". Then, go to WPML → Languages → Edit languages and enable "Encode URL for the language". It's recommended that this be tested with a new post. If you prefer to manually translate the slug in the Advanced Translation Editor (ATE), ensure you select "Translate" which includes the slug in the translation. Afterward, edit the page, make a minor change to the content, save these changes, and update the translation in ATE. For more detailed guidance, visit Translating Page Slugs documentation.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client was experiencing a blank page when attempting to update a translation on their website. Solution: We identified that the issue was related to a browser extension. If you're experiencing this issue, we recommend disabling the DuckDuckGo Privacy Essentials extension. You can find this extension here: https://addons.mozilla.org/en-US/firefox/addon/duckduckgo-for-firefox/.
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 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 at WPML support forum.
Problem: The client was unable to see the WPML menu in the WordPress admin sidebar after installing and activating WPML plugins on a WordPress multisite staging environment. This issue persisted despite the client's attempts to reinstall and clear caches. Solution: 1. We recommended adding a code snippet to reset WPML capabilities in the theme's functions.php file:
function wpmlsupp_1706_reset_wpml_capabilities() {
if (function_exists('icl_enable_capabilities')) {
icl_enable_capabilities();
}
}
add_action('shutdown', 'wpmlsupp_1706_reset_wpml_capabilities');
After adding this snippet, the client needed to visit the front page and then remove the snippet. 2. We identified that the WPML plugin was not enabled at the network level for the multisite installation. We provided instructions to activate it for each subsite separately through the network admin panel. 3. For the issue of the admin interface language, we guided the client to set their user profile to English to keep the backend in English while using German and French for the site content.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance. You can do so here: WPML support forum.
Problem: You are trying to use automatic translations in WPML, but the translations aren't showing, and the language switcher only displays English. You've been using the Classic Translation Editor, where fields for Spanish were blank and selecting 'Copy all fields from original' didn't resolve the issue. Solution: If you're experiencing this, we recommend switching from the Classic Translation Editor to the Advanced Translation Editor for automatic translations. Here are the steps to set this up: 1. Navigate to WPML->Settings-> Translation Mode and set it to 'Translate what you Choose' or 'translate everything automatically'. 2. Ensure the Automatic translation is set to your desired option. 3. Go to Translation Editor -> Editor for new translations and select 'Advanced Translation Editor (recommended)'. 4. For translations previously created using the Classic Translation Editor, change the editor to Advanced Translation Editor.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues where the domain in the URL was frequently changing, causing them to be logged out repeatedly. This issue was particularly problematic when trying to edit pages with Elementor, and it seemed related to domain changes. Solution: We adjusted the settings in WPML > Language > Language URL Format to stabilize the URL behavior. We recommended the client to try accessing their site using a different browser to check if the issue persists. It was found that using Chrome resolved the issue, whereas Safari continued to present problems. We suggested continuing with Chrome until future updates might address the issue in Safari.
If this solution does not resolve your issue, or if it seems outdated, we recommend opening a new support ticket. We also advise 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 are trying to translate button URLs and Gravity Forms on your site using WPML, but you are facing issues where you can't translate the button URL and only 11 out of 13 Gravity Forms are available for translation. Solution: To make all your Gravity Forms available for translation in WPML, please follow these steps: 1. Navigate to the list of Gravity Forms. 2. Find the form that is not showing in WPML > Translation Management. 3. Enter the form and make a small change. 4. Save the form to publish it again. 5. Return to the Translation Management page, and you should now see the form listed for translation.
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: You are unable to add credits to your account because your site is not listed under Tools in the Admin site. You also cannot see your connected site in Tools, which is necessary for managing credits. Solution: First, ensure that your website is registered with WPML, as only registered sites will appear in the Tools section. If your site is not registered or if you are unsure, you can follow the steps outlined in this documentation to register or re-register your site: WPML Registration Guide.
If the issue persists after following these steps, it might be due to an outdated solution or a different problem not covered here. 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 you still need help, please open a new support ticket at WPML Support Forum.
Problem: If you're experiencing an issue where the search input field on an ACF relationship field is disabled in translated posts, this might be due to a change introduced in version 2.1.0 of the Advanced Custom Fields Multilingual (ACFML) plugin. This problem persists in version 2.1.3. Solution: We recommend modifying a line of code in the ACFML plugin. In the file
This change might resolve the issue. However, please note that this solution could become outdated or might not apply 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 is unable to create a fully-functioning staging site replica of their production site using 'subdomain-like' URLs to distinguish languages without changing their hosting subscription. Solution: We recommend using the free version of the Duplicator plugin to clone the production site to a staging environment. After importing the site into the staging environment, the client should change the Language URL format to ensure it functions correctly. This approach avoids the need to upgrade the hosting plan.
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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're using the 'Don't update translation' button in WPML and expecting changes in the original language to automatically update in other languages, but find that this isn't happening, you might be misunderstanding the function of this button. The 'Don't update translation' button is designed not to update translations when changes are made to the original language. Solution: We recommend checking the functionality of the 'Don't update translation' button by following these steps: 1. Make changes to your page in the original language. 2. Click the 'Don't update translation' button in the language sidebar. 3. Verify if the translations remain unchanged, as this is the expected behavior. If you need to see the changes reflected in other languages, you should not use the 'Don't update translation' button. For further assistance, please provide screenshots of your process, including the use of the 'Minor Edit' button and the resulting status of translations. Additionally, enable and provide debug information by following the instructions here: http://wpml.org/faq/provide-debug-information-faster-support/
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: In the Home EN page, there is a row containing Edge Portfolio with tags 'Upsells' consisting of 6 items, all translated into French. However, in the Dashboard - Edge Portfolio, two of the six items ('Expositions' and 'Event management') display a cross instead of a pencil in the French flag column, indicating an issue with the translation status.
Solution: We recommend running some troubleshooting options available in WPML. Specifically, you can access these options by navigating to the WPML > Troubleshooting page in your WordPress dashboard. Here is a link to the troubleshooting guide: WPML Troubleshooting Guide. After applying the necessary troubleshooting steps, please check if the issue with the translations of 'Expositions' and 'Event management' is resolved and that they correctly display in the French version of the page.
If this solution does not resolve the issue or seems outdated, or if it does not apply 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. Should the problem persist, please do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: The client is experiencing issues with WooCommerce Multilingual & Multicurrency where the CAD price displays correctly, but the EUR price does not reflect the custom price set by the client. Instead, it shows a converted rate or incorrect values when using currency switchers. Solution: First, we recommend deactivating the WooPayments plugin as it is not compatible with our products and may cause conflicts. You can do this by following the instructions on https://woocommerce.com/document/woopayments/currencies/multi-currency-setup/. Next, increase the PHP memory limit to ensure our plugins function correctly. Add the following code to your
wp-config.php
file, above the 'That's all, stop editing! Happy blogging.' line:
If this solution does not resolve your issue or 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client's inquiry form displays correctly in English but incorrectly in French and Spanish on their website. Solution: We identified that the issue was related to a known problem where line breaks are ignored when using the Advanced Translation Editor. We applied the workaround mentioned in the related errata page. We recommend checking if the forms now display correctly in French and Spanish. If you're experiencing this issue, we suggest applying the same workaround as described on the WPML errata page.
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.
Problem: The client enabled a previous version of ATE, but encountered an issue with the (details button) on the product page. Solution: We resolved the issue by following the steps outlined on the WPML errata page. We recommend checking your English product page to ensure the problem is fixed.
If this solution does not apply because it might be outdated or not relevant 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 issue persists, please open a new support ticket.
Problem: The client reported that nearly all images were broken after installing WPML, affecting even untranslated pages. Solution: We suggested checking if the issue persists when WPML and its add-ons are deactivated. This step helps determine if WPML is causing the issue or if another factor might be involved. To do this: 1. Navigate to Plugins in your WordPress dashboard. 2. Deactivate WPML and all its related add-ons. 3. Refresh your page to see if the media are displaying correctly.
If the images are still not showing correctly after following these steps, or if this solution does not apply due to updates or differences in your setup, we recommend opening a new support ticket. Additionally, it's advisable to check the related 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.
Esta página incluye los tickets de soporte resueltos y documentados. ¿Buscas tickets que estén «en curso»? Visita el archivo completo de tickets de soporte
