Problem:
I'm using different domains per language and the sitemap of Yoast SEO not working correctly. The first domain appears in the second language sitemap and vice versa. Solution:
This issue is related to the transient caching of Divi builder which is compatible with Yoast SEO. Please follow the workaround below to fix the issue:
- IMPORTANT: Please backup your database and website before proceeding.
- Edit the file /wp-content/plugins/wp-seo-multilingual/classes/class-wpml-wpseo-xml-sitemaps-filter.php
Problem: The client was unable to use the automatic translation or manually translate pages. Additionally, the settings and support tabs were missing from the plugin menu, preventing access to debug information. Solution: We identified that some page records were not being correctly retrieved from the database. To fix this, we: 1. Navigated to WPML => Support. 2. Clicked on "Troubleshooting". 3. Performed the necessary actions on the Troubleshooting page. After these steps, the homepage should now be visible in the translated language.
For the issue with posts not showing, it was found that they were in the trash. We advised the client to: 1. Go to Posts. 2. Check the trash for the English language posts and review them.
Regarding the forms issue, we suggested that it might require a separate support thread as we aim to focus on one issue per thread.
If this solution doesn't seem relevant to your situation, please don't hesitate to open a new support ticket with us.
Problem: The client is experiencing an error after setting up the WPML plugin, indicating that the WPML String Translation is unable to write .mo files to the /wp-content/languages folder because it is not writable, even after changing the permissions to 755. Solution: In this case the issue was solved by changing the permission of folders /wp-content/language and its existing subfolder to 777.
1. We recommend using File Manager or FTP access to ensure that the /wp-content/languages folder and any subfolders are marked as "Writable". 2. If the issue persists, contact the hosting support to check if there are any server-side limitations regarding file permissions. More about file permissions in WordPress can be found here: WordPress File Permissions Documentation. 3. Create a subfolder named /wp-content/languages/wpml on the server, as WPML uses this for custom .mo files. 4. After creating the subfolder, generate the custom language files via the dialog at the top section of the WPML > Theme & Plugin-Localization page.
If these steps do not resolve the issue or if the solution does not seem relevant, please open a new support ticket with us for further assistance.
Problem: The client was facing a problem where changes made directly in the WordPress Editor to ACF fields marked as 'Don't translate' were being overwritten after updating the original content and re-translating it using WPML's Advanced Translation Editor (ATE).
Solution: We recommend sticking to one translation method to avoid this issue. If you're using the WPML Translation Editor, you should avoid manually editing translations in the WordPress Editor, as the WPML Translation Editor cannot recognize those changes and will overwrite them upon re-translation. For fields that you want to manage manually, you should use the ACF Field Group Option 'Different fields in different languages' and translate the content only with the WordPress Editor.
If this solution doesn't seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
Problem: The client is unable to enable WPML's Translation Editor when trying to translate content on Elementor and receives the message 'This action is not allowed'. Solution: 1. We recommend checking for any errors that might be displayed and uploading additional screenshots to provide more context. 2. We suggest deactivating all non-WPML-related plugins temporarily to see if there is a conflict causing the issue. It's important to ensure that a database backup is created before making any changes. If this solution doesn't seem relevant to your issue, please open a new support ticket with us.
Problem: 1. The client is unable to connect the WPML plugin to wpml.org, which is necessary for checking new releases and security updates. 2. The client is unable to enable WPML's Translation Editor for use with Elementor, receiving a message that the action is not allowed. Solution: For the first issue, we recommend following the troubleshooting steps in our documentation. Please ensure to whitelist the following domains: wpml.org, cdn.wpml.org, api.wpml.org, api.toolset.com, and cloudfront.net. You can find detailed instructions here: https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/.
Problem: The client was experiencing an issue with the message "This site has moved to a new location" after migrating their website and using WPML version 4.6.7 on a test copy of the site. The problem was occurring within Lando, used for local development, particularly with the Pantheon recipe.
Solution: If you're experiencing this issue with WPML and Lando for local development, here are the steps to resolve it: 1. Perform a search and replace from your production site URL to your local Lando URL using the following command:
lando wp search-replace '://www.mysite.com' '://my.lndo.site'
2. Flush or rebuild your cache with:
lando wp cache flush
3. Delete specific WPML settings from your database with the command:
lando wp db query "DELETE from pantheon.wp_options WHERE option_name = 'WPML_SITE_ID:ate' OR option_name = 'WPML_TM_AMS' OR option_name = 'otgs_wpml_tm_ate_cloned_site_lock'"
Additionally, we have released a fix in WPML 4.6.7 which includes a new button "Force-enable WPML’s Advanced Translation Editor" on the Troubleshooting page. For more details, you can refer to our documentation:
Problem: After launching a new site, switching from English to French with BuddyPress activated causes a 404 error or a blank page. The issue is related to object caching with Redis. Solution: We recommend the following workaround: 1. Ensure you have a complete backup of your site. 2. Access your site's files. 3. Navigate to the
/wp-content/
folder and create a
mu-plugins
folder if it doesn't exist. 4. Inside the
mu-plugins
folder, create a PHP file named
wpml-non-persistent-cache.php
(or any name you prefer). 5. Insert the following code into that file:
Problem: The client has a WooCommerce store and wants products that have not been translated to appear in the product list in additional languages. Despite having the 'translatable' option activated in WPML settings, a product with an 'orange' attribute is not appearing when filtered in the Spanish version of the store.
Solution: We found that the issue was related to the filter not showing the product in the translated pages. To resolve this, we: 1. Enabled a specific option in the WPML settings that allows products to be displayed in the original language when they are not translated. 2. Asked the client to set up the filter and test if the product with the variation now appears on the translated product pages.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is experiencing fatal errors like
Uncaught TypeError: Illegal offset type in isset or empty in /wp-content/plugins/sitepress-multilingual-cms/classes/core-abstract-classes/class-wpml-element-translation.php:259
on their English version pages after enabling media translation and clicking 'start' for the media translation in WPML.
Solution: 1. We identified that the issue might be related to the Advanced Custom Fields (ACF) plugin, where the theme is calling for an ACF field that contains the ID of an image, which WPML tries to translate. 2. We suggested disabling any caching plugins and server-related cache as a first step to resolve the issue.
Problem:
The Woodmart theme shows horizontal lines in widgets when we display language specific widgets/block elements using “Display on languages” option.
Solution:
The issue is solved by adding the below CSS:
Problem: The client is experiencing an issue where user profile languages are not being saved.
Solution: 1. We explained that the "Set admin language as editing language" option is stored in a browser cookie, which causes the dashboard to load in the language of the last logged-in user if they are using the same browser. 2. To see the dashboard in the site's default language or in a different user's selected language, we recommended logging in through a private browsing window. 3. We clarified that WPML controls the language of the dashboard text but does not control the content language displayed to the user. Each user can select their preferred dashboard language using the admin language switcher.
Problem: The client is trying to align the language switcher (DE, IT, EN) horizontally in the mobile menu. Solution: We recommend adding the following custom CSS to the theme's custom CSS section to override the default style provided by the theme and align the language switcher horizontally on the mobile menu:
.edgtf-mobile-nav .menu-item.wpml-ls-item a,
.edgtf-mobile-nav .menu-item.wpml-ls-item {
display: inline-block !important;
}
This should resolve the issue and make the language switcher appear as desired on the mobile version of the site.
Problem: If you have installed WPML and notice that Elementor stops working when you activate WPML String Translation, displaying a continuous loading or "spinning" effect, and your debug.log shows a PHP fatal error due to memory exhaustion, you are likely facing a memory limit issue. Solution: First, we recommend enabling the debug mode to identify the exact problem. To do this, add the following lines to your wp-config.php file:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
This will save the errors to a debug.log file in your /wp-content/ directory. For detailed instructions, please visit our documentation on debugging WPML.
After enabling debug mode, if you confirm that the issue is due to reaching the memory limit, you should increase the Memory Limit and WP Memory Limit on your server. You can find guidance on how to do this in our documentation. If you are unable to change these settings yourself, please contact your hosting provider for assistance.
If this solution does not seem relevant to your issue, please open a new support ticket in our support forum.
Problem: The client needed help translating an archive title and was experiencing issues with the language of the Yoast SEO title not updating. Solution: We recommend translating the strings through the WPML String Translation page. Here are the steps to follow: 1. Go to the WPML String Translation page in your WordPress dashboard. 2. Use the search function to find the specific strings you want to translate. For example, to translate the "Kopen" string, search for 'Kopen'. 3. To translate the "Bernax Race Simulators" string, search for 'Bernax Race Simulators'.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
