Problem: The client was experiencing issues with custom image links not redirecting to the correct language-specific pages on their multilingual site using WPML and Elementor. The links were always redirecting to the default language page instead of the intended language-specific pages.
Solution: We advised the client to ensure that the pages are properly linked as translations in WPML to maintain the integrity of the URLs across different languages. Here’s a step-by-step guide on how to achieve this: 1. Edit each translated page in WordPress. 2. In the right sidebar, expand the Language section. 3. Set the correct language for each version if not already set. 4. Click Switch to WordPress Editor and then click Apply in the popup. 5. Click Connect with translations and link the pages across languages. 6. Copy the direct URL of each translated page and use it for the image links in Elementor.
We also recommended using full URLs (including the language prefix) for manual links and double-checking the WPML translation relationships to prevent issues with links not working or being overwritten.
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. If further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are using WPML with WP-Event Manager Plugin and its Registrations Addon to set a Registration Limit. The site's default language is German, with an English translation. You've encountered an issue where the Registration Limit does not copy for the English translation. After applying a fix from WPML's errata page, it incorrectly combines all different registrations of all events into one in the English translation, causing the registration count to decrease incorrectly.
Solution: We recommend applying a specific workaround from the WPML errata page for the WP-Event Manager Registrations Addon issue with registration limit not being synchronized between languages. You can find the workaround here.
For the code replacements at lines 497 and 595, use the following custom functions:
If this solution does not resolve your issue or seems outdated, please 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. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: The client launched their store in two languages using WPML and performed a 301 redirect from a previous domain. Despite being indexed by Google, the site is not visible on google.pl under its proper name 'kavotti'. The client questioned if WPML could be causing the visibility issue on Google and why the site is not visible on google.pl despite being indexed. Solution: We reviewed the client's website configuration and sitemap, confirming that everything appears correct from the WPML side. We recommend that the client double-checks their sitemap for accuracy and initiates a new indexing request through Google Search Console. It's important to note that WPML does not influence Google's ranking decisions or indexing outside of providing multilingual support.
If this solution does not resolve the 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 the problem persists, please open a new support ticket.
Problem: You are experiencing an issue where the Dutch homepage of your website is incorrectly redirecting to a product page instead of the expected homepage. Solution: We recommend you try clearing your browser cache as a first step to resolve this issue. If the problem persists, it might be due to a temporary glitch. In such cases, we suggest checking for any specific settings or plugins that might be causing this redirection.
If these steps do not resolve the issue, the solution might be 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client would like to lower the amount of HTTP requests, due to each language flag being loaded as an individual SVG file. This results in multiple HTTP requests, which increase Time To First Byte (TTFB) and initial rendering time, particularly affecting visitors on slower networks.
Solution: We have forwarded a feature request to load SVGs programatically instead of using SVG files, which is currently under revision. You can find a custom solution approach for the issue inside the comments of this ticket.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: When WPML is enabled, previously uploaded images are not visible in the media library and are replaced by random images in posts. This issue does not occur when WPML is disabled. The problem affects specific posts created on August 23 and involves around 313 images. Solution: 1. Disable WPML and delete the old 313 images that are affected and possibly corrupted. 2. Re-enable WPML and upload new images. 3. Manually set these new images to the respective posts. 4. If the default language image still appears incorrect, upload the correct images again in the default language, ensuring they are properly set. 5. Optionally, translate the post into German (DE) if needed, using the WPML Media Addon to ensure images display correctly when WPML is enabled.
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 is experiencing an issue where Swedish product category URLs on their WooCommerce site are incorrectly using the English category base '/collections/' instead of the Swedish '/product-category/' base after updating the WooCommerce Shop page. This resulted in 404 errors for Swedish URLs while English URLs under '/en/collections/' were unaffected. Solution: We recommended that the client updates their WPML Multilingual CMS to the latest version along with all its add-ons, particularly WPML Multilingual & Multicurrency for WooCommerce, and also update WooCommerce itself. This can be done via the WPML admin panel by navigating to wp-admin/plugin-install.php?tab=commercial, clicking on "Check for updates", and following the update prompts. After updating, the client should remove any .htaccess workarounds, resave permalinks, and clear the site cache to see if the issue persists.
If this solution does not resolve the 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 the problem continues, please open a new support ticket at our support forum.
Problem: On an Albanian website, WooCommerce elements like checkout and basket are not automatically displaying in Albanian when set as the default language, unlike a similar setup on a Bulgarian site. Solution: 1. Ensure the default locale is set to "sq" instead of "sq_AL" in WPML > Languages > Edit languages, to match WooCommerce's language files. 2. Rescan WooCommerce for new strings at WPML > Theme & Plugin Localization. 3. In WPML > String Translation, locate and open the translation dialog for untranslated strings. If necessary, delete the registered string so WPML can automatically register it again when visiting the frontend. 4. Enable the option to auto-register strings at WPML > Translation Dashboard > Other texts (Strings) > Detect untranslated strings for testing. 5. Manually translate strings that are not automatically translated by creating a translation job in WPML > Translation Dashboard or using the Advanced Translation Editor.
If this solution does not resolve your issue or seems outdated, please 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. If the problem persists, we recommend opening a new support ticket at WPML support forum.
Problem: If you're experiencing issues with the stock status not being translated in WooCommerce when using WPML, it might be due to the strings being custom coded without a registered text domain. Solution: We recommend asking your developer to add text domains to these strings. Once that's done, you can use WPML's String Translation to translate them. For more details on how to register strings with a text domain, please visit https://wpml.org/documentation/support/how-to-use-gettext/ To learn how to use WPML's String Translation, check out https://wpml.org/documentation/getting-started-guide/string-translation/
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: You are trying to display translated membership levels and user field values from the Ultimate Membership Pro (IHC) plugin on the front end using WPML String Translation. Despite translating these strings under the domain admin_texts_ihc_levels and marking them as complete, the translated values are not displayed on the front end. Instead, the default language version continues to appear, even when switching the site language.
Solution: The issue occurred because the shortcode
[ihc-list-user-levels]
was displaying the membership plan labels from the plugin’s custom table instead of the translated values stored in WordPress options (wp_options). We updated the plugin so that it first checks the translated labels from wp_options. Here’s how we modified the code in
This modification ensures that the translated labels are displayed correctly. We recommend contacting the plugin author to integrate this fix permanently.
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 is experiencing issues with WooCommerce pages (Account, Cart, Checkout) not displaying in selected languages and the mobile language switcher behaving abnormally (opening sideways, hiding options). Solution: 1. Verify and translate WooCommerce pages: - Navigate to Pages in WordPress admin. - Locate the Cart, Checkout, and My Account pages. - Ensure there is a translation for each language using the plus (+) icon to add translations if missing. 2. Translate Cart and Checkout strings: - Go to WPML → Translation Dashboard. - Under Other texts (Strings), select your theme or WooCommerce domain from the All domains dropdown. - Translate any missing Cart/Checkout/account-related strings. 3. Adjust menus and links: - Ensure WordPress menus for each language link to the correct translated pages. - Update any hard-coded links to use WooCommerce functions like
wc_get_page_id('cart')
for WPML to switch URLs automatically. 4. Fix mobile language switcher: - Navigate to WPML → Languages → Language switcher options. - Try a different style (dropdown vs. list) if using a menu language switcher. - Consider using the built-in WPML switcher if using a widget or custom switcher. - Adjust theme CSS if it affects the switcher dropdown visibility. 5. Disable language redirect notices: - Check theme and plugin settings for any language redirect options and disable them.
If these steps do not resolve the issues, or if new issues arise, 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 unable to transfer Auto translation credits from a development site that is no longer accessible to their production site. Despite deleting the site key as instructed, the credits still do not appear in their account. Solution: First, ensure that Automatic Translation is enabled on your production site. If it is not visible in our system, the credits cannot be assigned. Once confirmed, we can manually transfer the credits to your live site. Please check your account now to see if the credits are showing as assigned to the live site.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. It's also 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: Some pages display as 100% auto-translated in the backend, but when viewed in the Arabic version, they still appear in English. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Edit the pages in the original language. 2. Make a small change to the content. 3. Save the changes. 4. Go to WPML -> Translation Management, select the content, and send it for translation. 5. Double-check if the content was correctly translated.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the permalink structure for brand URLs on their multilingual site. The URLs are not consistently displaying in the correct language format, showing /th/brand/[brand-name] in the English version and /en/brand/[brand-name] in the Thai version, despite settings and cache being correctly configured. Solution: 1. We recommended checking the erratum related to translating product brand slugs, which can lead to 404 errors. This is detailed at https://wpml.org/errata/translating-product-brand-slug-can-lead-to-404s/. 2. We identified that the default site language setting was causing the URLs to display incorrectly. To resolve this, the client should: - Navigate to WPML -> Languages -> Site Languages. - Click on 'Change default language' to set the appropriate default language.
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.
Problem: The client is preparing to replace their current live site with a new version and is concerned about managing WPML site registrations and avoiding translation conflicts after the domain switch. They asked if they should delete the current site registration from WPML before launching the new site. Solution: 1. Create a copy of both the old and new sites. 2. Delete the old site. 3. Remove the old domain from WPML account sites. 4. Restore the new site on the production domain. 5. Run the migration banner and select the 'Move' option. 6. After the migration is complete, update the site registration from development to production at WPML account sites. We recommend checking the guide on Using Advanced Translation Editor when you move or use a copy of your site for detailed steps.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also 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. For further assistance, you can contact us directly at WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
