Problem: The client needs to modify the language URL format to include country codes like /ca/fr/ and /us/en/ in their WordPress site using WPML. They attempted to modify the
REQUEST_URI
in an init hook but were unable to change the permalink structure as desired. Solution: We informed the client that achieving this URL format with WPML directly is not possible without additional custom coding. Since this requires complex code and might cause side effects, we recommended hiring a WPML contractor for professional assistance. You can find a suitable contractor by visiting https://wpml.org/contractors/.
Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your issue, 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 is trying to translate their website using WPML, but only one section of the homepage is being translated, and the footer is not visible in the translated version. The theme used, 'Service Finder,' is not WPML compatible, and there are issues with outdated plugins and new/custom Elementor widgets. Solution:
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, we recommend opening 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, please visit our support forum: https://wpml.org/forums/forum/english-support/
Problem: The client is trying to import listings to a staging site using WP All Import and WPML. The process works well for the English version, but issues arise with images not being attached to listings in other languages when translated automatically by WPML. The client wants to use the same image across all languages without translations. The current settings are: Gallery is set to copy, and Media is set to not translatable, which causes the media translation settings not to appear on the Settings page. Solution: We recommend setting Media to translatable to ensure images are properly attached to listings in all languages. After importing the listings in the default language, the client should edit the post and ensure that the 'duplicate image' option is checked under the Media attachment section in the sidebar. Additionally, it's important to verify that both duplicate options are checked in WPML > Settings > Media. This configuration doesn't create new files but makes database entries to link images across languages.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to use their assigned translation credits for automatic translation in WPML, and they also faced issues translating content on Elementor pages. Solution: 1. We identified that the translation credits were stuck due to a change in the automatic translation account ID after reinstalling WPML. To resolve this, the client needed to: - Move the credits back to their WPML.org account by clicking the "add/remove credits" button on https://wpml.org/account. - Remove the current site key and generate a new one at https://wpml.org/account/sites/, then unregister and re-register WPML with the new key on their website. - Re-add the credits to the site following the steps provided at https://wpml.org/documentation/automatic-translation/how-to-assign-automatic-translation-credits-to-your-sites/. 2. For translating Elementor pages, the client was advised to download and install a specific add-on for WPML to handle custom Elementor blocks. They should follow the steps outlined at https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/. If these solutions do not resolve the issues or if they seem 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: You lost 16000 credits after adding and removing a production site and cannot find the credits anymore. Solution: If you're experiencing this issue, it might be due to the automatic translation account ID being reset when WPML is uninstalled or WordPress is reinstalled. We have added the 16k credits back to your WPML.org account. You should now be able to see and assign them to your site by following the steps provided in this documentation: How to Assign Automatic Translation Credits to Your Sites.
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. Additionally, if you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing a permission issue with the WPML plugin because there is no 'languages' folder in your wp-content directory. This results in an error stating that 'WPML String Translation is attempting to write .mo files with translations' but cannot due to the missing folder. Solution: We recommend manually creating the 'languages' folder in your wp-content directory. This should resolve the permission issue and allow WPML String Translation to write the necessary .mo files. If you're experiencing this issue, please try this solution and check if it resolves the error.
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 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 trying to activate the WPML String Translation plugin to translate fields in your forms, but encounter a PHP warning on each page that has a form. The warning message is: 'Warning: Invalid argument supplied for foreach() in /home/officemo/sites/officemovepro.com/wp-content/plugins/gravityforms-multilingual/classes/Notification/Routing.php on line 154.' Although the form is translated, the error message appears. Solution: We recommend the following steps to resolve or hide the PHP warning: 1. Create a full website backup. 2. Update your PHP version to 8.0 to potentially resolve the warning. 3. To hide the warnings, disable the debug mode in WordPress. Edit your wp-config.php file and add the following line:
define('WP_DEBUG_DISPLAY', false);
4. Alternatively, consider downgrading the Gravity Forms Multilingual version as this has resolved the warning for another user. For more details, check the discussion here: WPML support forum.
If these steps do not apply to your situation or if the problem 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You transferred 40000 credits to your site but cannot see them in your account. Solution: If you're experiencing this issue, it might be due to the creation of a new automatic translation account ID when WPML is reinstalled or WordPress is reset. This can cause credits to remain in the old account. We have identified two separate automatic translation accounts in your case and have now moved the credits to the correct account. You should be able to see them on your site now.
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 the problem persists, please open a new support ticket.
Problem: You are trying to translate the copyright information field in the footer using WPML, but the translated string is not displayed on the website frontend. Instead, the original English text appears. Solution: To display the translation of the Elementor Pro Templates, you need to translate the templates via translation management rather than using string translation. Ensure that the translation is 100% complete to be visible on the frontend of the website. For more information, please visit Translating Elementor Templates.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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, please visit our support forum at WPML Support Forum.
Problem: After updating content and UI on the client's site, the changes were not being translated by WPML. Additionally, the client encountered multiple PHP warnings indicating 'Undefined array key' errors. Solution: 1. We advised the client to ensure that after making changes in the content in the original language, they should update the translation. If this step was already done but the issue persisted, we recommended applying the workaround described on our errata page: https://wpml.org/errata/wordpress-6-7-mo-files-not-loaded-and-leading-to-missing-translations-on-front-end/. 2. Regarding the PHP warnings, we clarified that these messages likely resulted from using an incompatible PHP version (v8.3) with WordPress core and many plugins/themes. We suggested downgrading the PHP version to v8.2 or v8.1 to avoid such warnings.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are trying to update the WPML plugin but it cannot connect to wpml.org due to network or security settings preventing outgoing communication. Additionally, there is an issue with the 'Site key not matching'. Solution: First, check if the issue with the WPML plugin not connecting is a false positive by clearing your server cache. You can do this by navigating to Plugins > Add new > Commercial, then clicking the 'check for updates' button. If WPML still shows as registered, the issue might just be a false positive.
If the 'Site key not matching' error persists, generate a new WPML key from http://wpml.org/account/sites/. Ensure that the key is generated specifically for the URL https://wildvermeersch.com. After generating the new key, go to the backend of your site, navigate to Plugins > Add new > Commercial, click the 'UNregister WPML' button, then 'REgister WPML', and use the new key.
If these steps do not resolve your issues, or if the solution seems 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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with sidebar filter translations not appearing on the category page, despite translations being added in the template. Additionally, after translating WooCommerce categories and ACF content, the translated categories in English were missing products present in the original category, displaying 'no product is present for this category' on the frontend. Solution: We reviewed the settings and found that in WPML -> Settings -> Post Types Translation, 'Products (product)' was set to 'Translatable - use translation if available or fallback to default language', and the same setting was applied for 'Product categories (product_cat)'. However, the categories were translated from Arabic to English in WooCommerce -> WooCommerce Multilingual & Multicurrency -> Categories, which caused the filtering issue. To resolve this, we duplicated some products in WPML -> Translation Management, which made the sidebar display the filtering options correctly. We advised the client to duplicate all other products similarly and apply the same changes to other sites. Additionally, we noted that if the product titles and content in Arabic are changed to Arabic in the future, it is crucial to first disconnect the duplicated English products to avoid displaying English products in Arabic.
If this solution does not resolve your 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is trying to cancel their WPML subscription as it is no longer in use. Solution: If you're looking to cancel your WPML subscription, we recommend you request a refund by visiting https://wpml.org/purchase/refunds/. Alternatively, you can contact our administrative team directly by filling out the form at https://wpml.org/home/contact-us/contact-form/. They will respond to you as soon as possible.
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 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.
Problem: The client reported an issue with the String Translation table on their site, which was not currently affecting the site's operation but could become critical in the future. An error was observed in the dashboard. Solution: 1. We requested the client to create a full backup of the site before proceeding. 2. After gaining access to the site, it was discovered that the error message was due to a missing file from a plugin used to check the database. 3. We advised the client to connect to the site via FTP, navigate to the
wp-content
folder, then to the
plugins
folder, and delete the 'pexlechris-adminer' folder to resolve 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with setting up WPML on a site with a large number of products and encountering errors, particularly with automatic translations not working correctly and fatal errors related to Yoast SEO, this might be relevant to you. Solution: We found that the fatal error was related to an incorrect translation of a placeholder in a string from Yoast SEO. The error message indicated an 'Unknown format specifier "t"', which was due to a missing 's' in a placeholder within the Dutch translation of the string:
Fatal error: Uncaught ValueError: Unknown format specifier "t" in /path/to/wordpress-seo/admin/class-yoast-columns.php:41
To resolve this, check the translation of the string and ensure that all format specifiers (like %s, %d, etc.) are correctly translated. The problematic string was: "Admin only notice: this page does not show a meta description because it does not have one, either write it for this page specifically or go into the [%1$s - %2$s] menu and set up a template." 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
