Problem: The client was experiencing an issue with a custom post type 'project' on their German website using WPML for English translations. While one post displayed the English translation correctly, the other resulted in a blank page, and any new posts of this type also did not show content in English. Solution: We recommended the client to directly edit the English language page of the problematic post and then resave it by clicking on the update button. This action resolved the issue, and the English translation displayed correctly.
If you're experiencing a similar issue with custom post types and translations resulting in a blank page, we recommend you try the following steps: 1. Navigate to the problematic post in the WordPress admin area. 2. Switch to the English version of the post. 3. Click on the 'Update' button to resave the post.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we highly recommend checking related 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. You can reach our support forum here.
Problem: The client is experiencing issues with the WPML plugin where the gallery content is not being duplicated correctly when creating translations for new languages. Specifically, the gallery content is not pulled through when using the 'Copy Content from English' feature for Arabic and French translations, although it previously worked for Spanish.
Solution: We recommend ensuring that the 'duplicate media' checkboxes are checked when translating pages. Instead of using the 'copy' option, it is better to use the 'duplicate' option for media items. This will create new entries in the database for the translated image captions, titles, meta text, and other information, which is necessary for the translations to work correctly.
If you're experiencing this issue, we suggest you: 1. Check the 'duplicate media' checkboxes in the Media attachment section on the edit page screnn. 2. Use the 'duplicate' option when translating pages to ensure all media content is properly duplicated.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking the related 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: The client's WPML Language Switcher is not displaying the dropdown languages, even though they have selected about 8 languages. Only the English option is showing. Solution: We recommend that the client ensures that they have translated their pages into the other languages. For the language switcher to display a language option in the dropdown, the corresponding pages must exist in those languages. The client should look for the pencil icon next to the languages, which indicates that the page has been translated. For more information on how to translate content, the client can visit the following documentation:
If the provided solution does not apply or is outdated, or if the client is still experiencing issues, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that they have installed the latest versions of themes and plugins. If the problem persists, the client should open a new support ticket for further assistance. WPML Support Forum
Problem: The client is unsure about the best setup for language URL options in WPML, as the descriptions provided are unclear. Solution: We recommend using the language per-directory option, which will structure URLs by appending the language code after your domain (e.g., domain.com/en for English). This is the most common setup and is preferred by most websites. For more information on the different language URL options, including using different domains or adding the language as a parameter, we suggest reviewing our documentation:
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 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 need further assistance, please contact us in the WPML support forum.
Problem: The client was experiencing a crash when trying to create a normal post in a custom post type, specifically when there were no posts in the custom post type.
Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /wp-content/plugins/sitepress-multilingual-cms/menu/post-menus/wpml-posts-listing-page.class.php:26
Solution: We recommend adding a conditional check to the relevant file to prevent the crash. Insert the following code to the file
This code ensures that if there are no posts, the function will return early and prevent the crash.
Please note that this solution might be outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking the related 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.
Problem: If you're experiencing a PHP warning message in the WordPress Admin when viewing any admin screen in a secondary language, and it only occurs with certain Kadence plugins activated (Kadence Pro, Kadence Blocks, Kadence Blocks Pro), we can help you address this issue.
Solution: First, we recommend creating a staging site to safely investigate the issue without affecting your live site. You can use your hosting service or a plugin like WP Staging for this purpose. Once the staging site is ready, replicate the problem there by activating WPML + String Translation with all other plugins disabled and a default theme like Twenty Twenty-Four.
If the problem disappears, gradually activate your theme and plugins one by one to isolate the cause. If the issue persists with just WPML + String Translation and Kadence plugins, it indicates a specific conflict between Kadence Pro and String Translation.
To resolve the issue: 1. Navigate to WPML > String Translation. 2. Filter by domain: "Text Domain". 3. Select and delete all the strings in that domain using the "Delete all selected strings" option.
This should remove the PHP warning. The issue arises from incorrect registration of dynamic strings by the Kadence plugin, and we are reaching out to them for a fix.
Please note that this solution might be outdated or not applicable to your case. If the problem persists, we highly recommend checking related 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.
Problem: The client was trying to set up WPML on a development website but encountered an error stating 'Unable to register: Site key not matching'. This issue persisted even after unregistering the site, generating a new site key, and following the instructions provided by Hostinger.
Solution: 1. We recommended creating a full website backup. 2. We suggested translating and following the recommendations from a related support ticket involving Hostinger, which could be done using Google Chrome's translate feature. 3. We asked the client to go to WPML > Support > Installer Support and click the 'check now' button a few times, then share a screenshot of the page. 4. We requested temporary access to the client's site to investigate the issue further. 5. Upon investigation, we discovered that the site key was not matching because the domain set in the database was different from the one used to generate the WPML key. The domain in the General settings of WordPress should match the domain used for the WPML key.
If you're experiencing a similar issue, we recommend following these steps and ensuring that the domain in your WordPress General settings matches the domain used to generate your WPML key. If the solution provided here is not relevant to your case, possibly because it's outdated or not applicable, we encourage you to open a new support ticket. We also highly recommend checking related 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 contact us through the WPML support forum.
Problem: The client wanted to place the language switcher flags next to the menu items in the header instead of the footer and also had issues translating PDF documents located in the footer. Solution: For the language switcher issue, we recommended following the documentation on adding a language switcher to a menu. This involves navigating to WPML > Languages, finding the "Menu language switcher" section, and adding a language switcher to the desired menu. Documentation link: https://wpml.org/documentation/getting-started-guide/language-setup/language-switcher-options/
Regarding the PDF translation issue, since it was a separate problem, we opened a new support ticket specifically for that issue and provided the client with the link to the new ticket.
Please note that the solution provided here might be outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking the 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 in our forum: https://wpml.org/forums/forum/english-support/
Problem: The client is experiencing 404 errors on their website when switching between categories in the English translation using the WPML plugin. The issue does not occur on the source version of the website, and the server logs indicate that the page cannot be found. The client suspects a problem with the .htaccess file.
If the solution provided here is irrelevant, either because 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 do not hesitate to open a new support ticket with us.
Problem: The client wants to prevent WPML from translating the titles of Elementor widgets in edit mode, as they prefer to use the English language interface even though their native language is Turkish. Solution: 1. We acknowledge that the behavior the client is experiencing is expected when using WPML with Elementor. 2. We suggest reviewing the following tickets for potential solutions or workarounds:
3. We explain that Elementor is a front-end editor and there are limitations to keeping the Elementor Module labels in the default language due to potential increased loading times, which could negatively affect the user experience.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the issue persists, 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 our support forum.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 necessary, please open a new support ticket for further assistance.
Problem: The client is attempting to create a new language with the code "EU" in WPML but receives an error message stating "The Language code already exists". This issue persists even after deleting an old language with a similar code and clearing the cache.
Solution: We have identified that the code "EU" is already in use for the Basque language in the WPML database. To prevent this issue, we recommend checking the
wp_icl_languages
table in the database to view all 70 preset languages and their codes, ensuring that the new language code does not duplicate any existing ones.
If you're experiencing this issue, we recommend you: 1. Access your website's database. 2. Locate the
wp_icl_languages
table. 3. Review the list of preset languages and their codes to avoid duplicates.
Please note that the solution might be irrelevant if it's outdated or not applicable to your case. If the problem persists, we highly recommend checking related 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.
Problem: The client was trying to translate the menu item 'shoots' to Spanish but it was not displaying the translated term 'sesiones' on the Spanish version of the website.
Solution: We identified that the 'Shoots' menu item was created as a Custom Link, which WPML could not automatically translate because it was not pointing to a specific URL. To resolve this: 1. Navigate to Appearance > Menus. 2. Select the menu you wish to translate (e.g., 'right side menu'). 3. Click the '+' icon to add a new language version for the menu. 4. Name the translated menu (e.g., 'Spanish right menu'). 5. Create a custom link with the name 'Sesiones' pointing to '#'. 6. Add the necessary pages to the menu from the right sidebar. We performed the same steps for the mobile menu to ensure consistency across devices.
If the solution provided here does not apply to your case, or if it seems outdated, we recommend checking the related 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 do not hesitate to open a new support ticket with us.
Problem: The client was experiencing an issue where the blog page style broke after adding another language. Additionally, the client wanted to make the footer in Arabic RTL without adding separate widgets, but when switching to Arabic, the footer remained LTR.
Solution: Firstly, the issue with the blog page style was resolved by the client by adding some posts in the other languages. Regarding the RTL direction for the footer in Arabic, we suggested that this is a theme-related issue rather than a WPML issue. A custom CSS solution could be applied, but it might be complex. Here is an example of a CSS rule that could be used to align text to the right when in the Arabic language:
:lang(ar) > #block-38 > div {<br /> text-align: right;<br />}
We also suggested that the client could try creating separate widgets for each language by going to Appearance > Menus and following our guide on translating widgets. If the issue persists, we recommended contacting Astra Support for further assistance, as they suggest creating a Child Theme with Custom CSS for RTL support, which can be found here: RTL CSS via Child Theme.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If this is the 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 with us.
Problem: The client reported an issue with the search function in Korean, one of the WPML registered languages. The search would return no results for visitors unless they were logged into the WordPress backend. The client provided a Korean term (for "church") 교회, which should have returned many results, and shared a screen recording to illustrate the problem.
Solution: First, we checked if there were translations available and published for the term in question. We found that while there were no translations for posts in Korean, there were some for Books. We then conducted tests using the word '걱정과 불안' with Books and confirmed that the search worked when logged in but not when logged out, despite the translations being published.
We asked the client how the search module was created—whether it was part of the theme, a third-party plugin, or custom. After reviewing the provided screenshots, we could not find any known issues with the WordPress search function and WPML that would explain this behavior.
We then requested the client to upload the Themify theme to a sandbox environment we created to further investigate the issue. We provided the link to the sandbox for the client to proceed with the test.
If you're experiencing a similar issue, we recommend checking if your translations are published and testing the search functionality in a clean sandbox environment. If the problem persists, it might be theme-specific, and you should check for updates from the theme developer.
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, 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 with us.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
