Problem: You are using the LH Archived Post Post Status plugin to archive pages and want to translate a custom archiving message set in the plugin's settings page, but it does not appear in the string translations. Solution: First, ensure you have deleted any existing translations of the default message in WPML > String Translation. Then, scan the LH Archived Post Status plugin for strings by navigating to WPML > Plugin and Theme localization. If the custom message still doesn't appear, use the 'Translate texts from admin screens' option in WPML > String Translation. If the message is still not available for translation, adjust the translation preferences by going to WPML > Settings and enabling 'Show System Field' under 'Custom Field Translation'. Search for 'post_status_message' and set its translation preference to 'Translate'. After saving the message again in the settings, switch to another language using the language switcher on the topbar, add the message manually for that language, and save the changes. For detailed guidance, please refer to this guide.
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. If needed, please open a new support ticket for further assistance at WPML support forum.
Problem: The client is using the Hestia Pro theme on their WordPress site and has added a lot of CSS. They are facing issues with the currency switcher widget, which drops down past the website's footer, creating unwanted black space below it. The client wants to make the currency switcher widget scrollable, change its placement to the top of the website if necessary, and eliminate the black space below the footer. Solution: We recommend using PHP to customize the currency switcher and position it anywhere on the page. This can be done by adding the code directly to the theme or through plugins that allow PHP code integration within the page builder. For detailed guidance on placing and customizing the currency switcher, please refer to this existing support ticket: https://wpml.org/forums/topic/placing-and-customizing-the-currency-switcher/#post-11440045 Additionally, you can find more information on using the currency switcher shortcode in our documentation: https://wpml.org/documentation/related-projects/woocommerce-multilingual/multi-currency-support-woocommerce/#currency-switcher-shortcode If these solutions do not resolve your issue or if they seem 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 https://wpml.org/forums/forum/english-support/.
Problem: If you're experiencing an 'Uncaught TypeError: Cannot access offset of type string on string' error in the WP SEO Multilingual classes RankMathSEO Sitemap Hooks.php on line 69, it might be due to issues with the Rank Math SEO caching. Solution: We recommend the following steps to resolve this issue: 1. Edit the file at .../wp-content/plugins/wp-seo-multilingual/classes/RankMathSEO/Sitemap/Hooks.php using a code editor. 2. Navigate to line 66. 3. Just before line 66, add the following code:
// If 'loc' is not set, just return the URL unchanged.<br />if (!isset($url['loc'])) {<br />return $url;<br />}
4. Save the changes. **** Important! Please make a full site backup (files and DB) before you proceed with these steps****
This workaround should help mitigate the issue temporarily. Additionally, we have escalated this problem to our compatibility team and it will be addressed in future versions of WPML SEO.
We have also published an errata regarding this issue, which you can view here.
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 is working on a site under development and needs to register the WPML key to the website. Additionally, the WPML plugin cannot connect to wpml.org, which is necessary for checking new releases and security updates. Solution: To register the WPML key: 1. Ensure you are logged into wpml.org. 2. Navigate to WordPress Dashboard > Plugins > Add New > Commercial (Tab). 3. Click on "Register WPML" at the right section of the screen. 4. Click on "Get a key for this site". A new page will open, and the auto-generated key will appear. 5. Copy the key and paste it into the "Site Key" input box. 6. Click the "OK" button. For more information, visit https://wpml.org/faq/install-wpml/#register
For the connection issue: 1. Contact your hosting service provider and request them to whitelist the following URLs: - wpml.org - cdn.wpml.org - api.wpml.org - api.toolset.com - cloudfront.net For more details, visit https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/
Regarding plugin installation, the client does not need to install all plugins shown. Essential ones include WPML String Translation and WPML Multilingual CMS.
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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue where switching to the Spanish language on their website redirects them to the homepage instead of the translated Activity page. They have set up WPML and translated a custom post type (CPT) 'Cooking Classes' but encounter redirection and 'Invalid post type' errors. Solution: We recommend the following steps to troubleshoot and resolve the issue: Ensure that the custom post type 'Tours' is properly configured for translation in WPML. Go to ACF > POST TYPES > TOURS > EDIT, select WPML translation Editor, and click the + sign to translate it. If these steps do not resolve the issue or if you encounter further problems, it might be due to outdated information or a different configuration. 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: You are experiencing issues with category display in the backend of a multilingual site using WPML. Categories are not displayed in the expected language; instead, they appear in the language of the last updated post. Solution: We recommend the following steps to resolve the issue: 1. Navigate to WPML > Support > Troubleshooting. 2. Click on the following buttons: - Synchronize posts taxonomies (Select pages/posts from the dropdown before clicking the button) - Clear the cache in WPML - Remove ghost entries from the translation tables - Assign translation status to duplicated content - Set language information - Fix post-type assignment for translations 3. Go to Settings > Permalinks. 4. Set the Permalink structure to "Postname" and save the changes. 5. Clear the caches from your site and browser, then check again.
If the issue persists or the solution 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an 'Invalid post type' error when WPML was active, which disappeared upon deactivating WPML. The issue was suspected to be related to a conflict with another plugin. Solution: We recommended the client to test their site in a minimum environment by deactivating all plugins except for WPML and its add-ons. This would help identify if the issue was indeed due to a plugin conflict. The client was advised to reactivate the plugins one by one to pinpoint which one caused the issue. It was important to make a full site backup before proceeding with these steps. If the site was live, we suggested performing these procedures in a staging environment or a snapshot on a local or another server.
If you're experiencing similar issues, we recommend trying these steps to see if it resolves the problem. However, 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 installed the WPML plugin on their website, which caused the website to malfunction. The client was also concerned about changing the default language back to Dutch without consequences. Solution: We resolved the issue by translating everything from Dutch to other languages and vice versa, and setting the default language back to English. This adjustment made the homepage and shop pages display correctly in all languages, including Dutch. If you're experiencing similar issues, we recommend checking your language settings and ensuring that translations are correctly set up. Changing the default language can generally be done without severe consequences, but it is advisable to select a default language and maintain consistency without changing it frequently.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please do not hesitate to 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 through our support forum at WPML Support Forum.
Problem: You are trying to customize the menu on your site after using the automatic translation feature in WPML, but it's not working as expected. Solution: We have checked your site and synced the menu again. Most items in your site's menu are now translated. However, custom menu items such as the Home page item's label and link, and the Properties' label need manual translation. You should translate these items in WPML -> Strings Translation. For instance, the Dutch link should be translated to: https://checkka.com/nl/.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Additionally, 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. For further assistance, you can also visit our support forum at WPML support forum.
Problem: The client created English translations for their website pages but when selecting the English language via the language switcher, the pages continue to display in Spanish. Solution: 1. Direct Access Check: Confirm if accessing the English homepage directly via https://www.mansiondepapilio.com/en/ displays the page correctly. This helps determine if the issue is specifically with the language switcher. 2. Language Switcher Configuration: Ensure the language switcher is correctly configured by checking under WPML > Languages. Verify settings for Menu language switcher, Widget language switcher, and ensure they are properly added to your site (e.g., in the header, footer, or sidebar). 3. Permalinks: Refresh your permalink structure by navigating to Settings > Permalinks and clicking the 'Save Changes' button without making any changes. 4. Increase WP_MEMORY_LIMIT: Increase the WP_MEMORY_LIMIT to at least 256M. Follow the instructions on how to do this at increasing your site's memory limit.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, 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: The client reported that after assigning 20,000 credits to their website and subsequently deleting and re-adding the site key, the credits did not appear in their WPML account. Solution: We conducted a thorough analysis and discovered that between the creation and removal of the site key, over 25,000 credits were used. This usage was confirmed through detailed logs. Therefore, no credits remained when the site key was deleted and re-added. We advised the client to review their Automatic Translation Usage Report for detailed information on credit usage, which can be accessed via WPML > Translation Management > Tools > Payment and settings > Automatic Translation Usage Reports. For further details, the client can refer to the documentation on Automatic Translation Invoices. Additionally, we provided a specific credits usage report available at Google Drive.
If this solution does not resolve your issue, or if it 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 further assistance is needed, please open a new support ticket.
Problem: The client needed to know if WPML can handle different base languages for different pages, hide the selected language in the language selection box, and work with the Events Calendar Pro plugin for Mandarin language. Solution: 1. WPML allows setting different base languages for different pages or posts. You can manage this by setting the language of each page/post individually in the WPML settings. 2. WPML provides an option to hide the currently selected language from the language switcher. This can be configured in the WPML settings under the language switcher options. 3. WPML is compatible with the Events Calendar Pro plugin and supports translating content into Mandarin or any other language. For more details on setting up multilingual events websites with WPML and the Events Calendar, visit the following links:
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. If further assistance is needed, please open a new support ticket.
Problem: The client is inquiring if the latest version of WPML is compatible with PHP 8.X, as their site on Wordpress.com is updating to PHP 8.1. Solution: We have confirmed that the latest version of WPML should operate without issues on PHP 8.X. However, there are known situations where deprecated errors might appear with PHP 8.2. These errors can be hidden and do not impact the functionality of WPML. For more details on this specific issue, you can refer to our errata page: PHP 8.2 Deprecated: Creation of dynamic property WHIP_RequirementsCheckerConfiguration is deprecated.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client reported that while navigating their multilingual website, which includes English, French, and Arabic, the site automatically switched to English when clicking on links, despite French being set as the default language. Solution: We identified that the main menu did not have translations set up for each language, causing the site to revert to English. We recommended creating separate menus for each language and provided guidance on how to do this with a link to our documentation: Translating Menus. Additionally, we accessed the site's backend and assigned the correct French menu in the Elementor settings, which resolved the issue.
If this solution does not resolve your issue, or if it 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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are developing a site using WPML for translations and encountering issues where translated pages do not display the correct layout, style, or theme, particularly in the English version. This problem persists even after clearing the cache with WP-ROCKET. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Navigate to WPML -> Settings -> Custom Fields Translation. 2. Click on 'Show system fields'. 3. Look for any items named with 'css', 'style', or 'styling'. 4. Set these items to 'Copy' or 'Copy Once' if they are not already set. 5. Make a minor modification to the main language version of the home page (even an extra space is sufficient) and save. 6. Edit the translation using the WPML Advanced Translation Editor and save it. Check if the styling appears correctly in the second language after these adjustments. If this does not resolve the issue, it might be necessary to provide temporary access (wp-admin and FTP) to your site for further investigation. Ensure you back up your site files and database before providing access. For more details on privacy and security, please visit: our privacy and security policy.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
