Problem: The client is managing media settings in WPML and noticed that the 'duplicate media' feature seemed enabled despite their intention to have it disabled. They observed that after deleting images in the English version of their site, these images remained in the Spanish version. They were unsure if this was due to a local cache issue and asked about safely disabling media translation options and handling duplicate images without breaking the site. Solution: We explained that WPML does not automatically translate media files; it only duplicates them in the database for synchronization purposes when the Media Translation plugin is active. To stop this duplication, the client can disable the media duplication options in WPML by navigating to WPML>>Settings>>Media Translation. For more details, they can refer to our documentation here: Media Translation Guide. Furthermore, disabling the duplication options will only affect newly uploaded media; it will not remove existing entries in secondary languages. There is no automatic option to delete media files from secondary languages once they are created. However, the client can follow a workaround suggested in another support ticket after ensuring a full site backup. This workaround can help in manually removing media files from secondary languages. More details can be found here: Forum Post on Cleaning Media Translation.
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 further assistance is needed, please open a new support ticket at WPML Support Forum.
Problem: If you're experiencing issues where your translated pages keep redirecting to the original language on your Indonesian site, it might be due to a 302 redirect setup. This setup can prevent content from being permanently reachable, affecting both user access and SEO. Solution: We recommend taking the following steps to diagnose and potentially resolve the issue: 1) Ensure you take a full backup of your site and database. 2) Deactivate all plugins except for WPML. 3) Switch to a standard theme, such as Twenty Twenty-Four. 4) Clear all caches and check if the redirection issue persists. 5) Reactivate your plugins one by one, checking for the issue after each activation to identify any conflicts. 6) If the issue resolves with all plugins activated, switch back to your original theme to check if it is the source of the problem.
If these steps do not resolve your issue, or if the solution provided here becomes outdated or 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. Additionally, please feel free to open a new support ticket with us for further assistance at WPML support forum.
Problem: You have translations that are stuck in 'In progress mode' and are not visible on your website despite being 100% ready. The original language is English with translations into Estonian and Russian. Solution: We recommend applying the workaround from our errata page. Specifically, you can try the solution provided here: https://wpml.org/errata/divi-php-8-2-fatal-error-uncaught-typeerror-htmlspecialchars_decode/. After applying this workaround, please check if the translations are now visible.
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 with us for further assistance.
Problem:
Client is getting following PHP error with WPML Sticky Links plugin, on PHP 8.x:
PHP Deprecated: Automatic conversion of false to array is deprecated in .../wp-content/plugins/wpml-sticky-links/classes/class-wpml-sticky-links.php on line 19.
If this does not resolve the issue or if the solution 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. If needed, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues where links associated with certain translated strings are not working, such as 'my account', 'wishlist', and 'my products list' on your WooCommerce site, the problem might be with custom links added through the Customize My Account for WooCommerce plugin. Solution: We recommend following these steps to ensure that your translated links work correctly: 1. Copy the problematic link from the 'My Account' page that is not displaying correctly in the desired language. 2. Navigate to 'WPML > String Translation'. 3. Enter the problematic link into the search box and click the 'Search' button. 4. Once the link appears in the search results, add the translation for the link by clicking the '+' icon. For the English translation, enter the link to the English page. 5. Click outside the box to save the translation.
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 for further assistance.
Problem: In a WooCommerce shop with multiple languages, the 'product-category' slug was translated for different languages. However, for the German language, setting the slug to 'produkte' results in a 404 error when visiting the page. The backend shows the Dutch translation instead.
Solution: We analyzed the issue and determined it is not directly related to WPML or WooCommerce, but rather to the permalink structure used. WordPress uses specific rules to determine what content to display based on the URL visited. If both single products and product categories share a similar permalink base (e.g., site.com/products/), WordPress may struggle to differentiate between product requests and product category archive requests, leading to errors like the one experienced. We recommend changing the permalink structure so that products and product categories do not use the same base. For example, use 'products' for the product category base and '/product/%product_cat%/' for the custom product base. This adjustment should resolve the issue.
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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues where Spanish translations are not retaining formatting information such as line breaks compared to the original English posts, this might be due to a known issue with the Advanced Translation Editor. Solution: We recommend trying the workaround provided in our documentation. You can find detailed steps on how to address this issue by visiting https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/. Alternatively, using the previous version of the Advanced Translation Editor might also resolve this problem.
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 noticed that all Spanish translations of their blog posts were redirecting to the homepage instead of the individual blog posts. Solution: We recommended checking if the translated posts were visible on the frontend when logged in as an admin. If visible, the issue might be that the posts are in Draft mode. The client should edit these posts and publish them to see if this resolves the issue.
If this solution does not apply or is 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: The client is unable to edit image fields in the Spanish version of their site when they are part of a flexible content field. After changing the ACF translation settings from 'copy' to 'copy once', the images also became uneditable on the English side, and reverting the settings did not resolve the issue. Solution: We recommend setting the field preference to 'Copy Once' and using the WordPress editor to manually update the custom field in the translation post. This should allow for editing the image fields in both the English and Spanish versions of the site.
If this solution does not apply to your case, or if it 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. We highly recommend opening a new support ticket if further assistance is needed. You can do so at WPML support forum.
Problem: The client is unable to find the Footer Logo on their website and is unsure if there is a specific setting that needs to be checked. Solution: We recommended that the client provide temporary access (wp-admin and FTP) so we can examine the issue more closely. Before providing access, it is crucial to back up the site files and database. We will check various settings in the backend to identify and resolve the issue. We ensure privacy and security during this process, as outlined in our Privacy and Security Policy.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You have Automatic Translation enabled on your site and want to prevent a specific page from being translated automatically after duplicating the content in Translation Management. Solution: We recommend switching to the "Translate What You Choose" mode from WPML > Settings > Translation mode. This allows you to manually select which pages to send for automatic translation. You can find detailed instructions on how to send individual pages for translation in our documentation: Translating Individual Pages, Posts, and Other Content Automatically.
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 for further assistance.
Problem: The client is experiencing issues with WPML on their site. Specifically, the translated values of custom fields are not showing in the default WordPress editor, despite being set to translate in the settings. Additionally, registered shortcodes in WPML > Settings > Custom XML Configuration are not automatically translated. Solution: For the custom fields issue, we recommend the following steps: 1. Navigate to WPML > Translations. 2. Select all posts checkboxes. 3. From the Bulk Actions dropdown menu, select "Approve translation reviews". 4. Apply this action to all posts. After these steps, the translated fields should be visible in the WordPress editor for secondary languages. It is crucial to use only one editor consistently; if you have used WPML's translation editor, avoid editing directly using the WordPress editor and vice versa. For the shortcode translation issue, we have created a separate support ticket to address this specifically. You can follow the progress and find solutions here: https://wpml.org/forums/topic/split-taxonomy-translations/edit/
Please note that the solution provided 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 a 404 error on their multilingual blog when accessing it in a language other than the default. Solution: If you're encountering a similar issue with your multilingual blog showing a 404 error in another language, we recommend checking if the issue still persists. Sometimes, issues may resolve on their own or might have been fixed during other updates. If the problem continues, please provide more details about the error and any steps you've already tried. This information will help us understand and address the issue more effectively. Additionally, uploading screenshots can be very helpful in illustrating the issue more clearly.
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 https://wpml.org/forums/forum/english-support/.
Problem: The client needed help with customizing the font, size, and color of the language switcher text in different parts of their website, including changes when the header is fixed. They also needed guidance on targeting the switcher in the sidebar after switching from a footer to a widget-based switcher. Solution: 1. To change the color of the language switcher in the top header, we advised adding custom CSS in the site's backend under Appearance > Customizer > Custom CSS. Here is the code to use:
.wpml-ls-legacy-list-horizontal a {<br /> color: red !important;<br />}
The 'color' value can be changed to any desired color or hexadecimal code. More information on CSS color properties can be found at:
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 this does not resolve your issue, please open a new support ticket 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
