Problem:
When the client attempts to change a product variation, such as inserting a sale price and saving, the process does not complete, and the spinning icon persists. An error indicating 'PHP Fatal error: Uncaught Error: Call to a member function get_stock_quantity() on bool' appears in the logs.
Solution:
If you're experiencing a similar issue when saving product variations, we recommend trying the following steps in your WordPress admin area:
1. Navigate to WooCommerce -> WooCommerce Multilingual & Multicurrency -> Status -> Troubleshooting.
2. Execute the following troubleshooting options:
- "Sync product stock quantity and status"
- "Fix translated variations relationships"
- "Sync removed product meta from original products to translations"
Please ensure you take a full backup of your website and database before proceeding with these steps.
Keep in mind that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 you still need assistance, please do not hesitate to open a new support ticket in the WPML support forum.
Problem: The client is attempting to use DeepL for automatic translation on their production site but encounters an issue where the translation management page is not loading, displaying an error message suggesting a problem with the internet connection. Solution: We recommend deactivating the WP External Links plugin, as our tests indicate that this plugin is causing the issue with the translation management page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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. For further assistance, please visit our support forum.
Problem: The client added a custom language and encountered an error stating that content in this language cannot be automatically translated unless mapped to a supported language. Solution: We recommend duplicating the content from English and Arabic to the respective custom language. It is important to understand that automatic translation is not possible when the original language and the target language are the same. To resolve this issue, you should map your custom secondary language to your site's default language. For detailed instructions, please refer to our documentation on Using Automatic Translation with Custom Languages.
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 you still need assistance, please do not hesitate to open a new support ticket in our forum.
Problem: The client is encountering a PHP Fatal error due to memory exhaustion when trying to access the Translation bucket page. The error suggests that the site is exceeding the memory limit, which could be due to a conflict with plugins or the theme.
Solution: We recommend changing the WP MEMORY LIMIT to 512M to see if this solves the issue. Add this code to your wp-config.php to increase WP memory:
define('WP_MEMORY_LIMIT', '512M');
Paste it just before:
/ That's all, stop editing! Happy blogging. /
If these steps do not resolve the issue, we may need to replicate the problem on a test site with WPML or require access to the client's staging site for further investigation.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket.
Problem: The client was unable to use the WPML translation editor to translate a page from Italian to English using Elementor. The content did not appear, and the page continued to load without showing the original content in the fields for translation.
Solution: We recommended the client to: 1. Ensure that Elementor widgets are registered for translation as explained in our documentation: Registering Custom Elementor Widgets for Translation. 2. If the issue persists, we provided a series of SQL queries to clean up invalid records from the database and reset auto-increment values. The client should: - Make sure to have a complete database backup. - Run the following SQL queries to delete invalid records:
DELETE FROM `wp_borgo23_icl_mo_files_domains` WHERE id = 0;<br />DELETE FROM `wp_borgo23_icl_strings` WHERE id = 0;<br />DELETE FROM `wp_borgo23_icl_string_packages` WHERE ID = 0;<br />DELETE FROM `wp_borgo23_icl_string_positions` WHERE id = 0;<br />DELETE FROM `wp_borgo23_icl_string_translations` WHERE id = 0;<br />DELETE FROM `wp_borgo23_icl_translate` WHERE tid = 0;<br />DELETE FROM `wp_borgo23_icl_translate_job` WHERE job_id = 0;
- If no errors occur, run the following queries to alter tables:
SET sql_mode = '';<br />ALTER TABLE `wp_borgo23_icl_flags` CHANGE `id` `id` INT NOT NULL AUTO_INCREMENT;<br />ALTER TABLE `wp_borgo23_icl_languages` CHANGE `id` `id` INT NOT NULL AUTO_INCREMENT;<br />ALTER TABLE `wp_borgo23_icl_languages_translations` CHANGE `id` `id` INT NOT NULL AUTO_INCREMENT;<br />ALTER TABLE `wp_borgo23_icl_mo_files_domains` CHANGE `id` `id` INT NOT NULL AUTO_INCREMENT;<br />ALTER TABLE `wp_borgo23_icl_strings` CHANGE `id` `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT;<br />ALTER TABLE `wp_borgo23_icl_string_packages` CHANGE `ID` `ID` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT;<br />ALTER TABLE `wp_borgo23_icl_string_positions` CHANGE `id` `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT;<br />ALTER TABLE `wp_borgo23_icl_string_translations` CHANGE `id` `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT;<br />ALTER TABLE `wp_borgo23_icl_translate` CHANGE `tid` `tid` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT;<br />ALTER TABLE `wp_borgo23_icl_translate_job` CHANGE `job_id` `job_id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT;
- After running the queries successfully, edit the homepage with Elementor, make a minor change, update, and then attempt to translate again.
Please note that this solution 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 WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket for further assistance.
Problem: If you're experiencing issues with automatic translation not working after moving your site, and you are using the Thrive Architect plugin, it's important to note that Thrive Architect is not currently compatible with WPML. Solution: Firstly, we apologize for any inconvenience caused. Since Thrive Architect is not compatible with WPML, you will need to translate content manually. We recommend following the method outlined in our documentation on using different translation editors for different pages. Additionally, if you see an option to "mark it as copy" in your WPML interface, please click on it. This should allow you to use the Advanced Translation Editor without issues.
Please be aware that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, don't hesitate to open a new support ticket. You can reach out to us on the WPML support forum.
Problem: The client needed to integrate automatic translation for two languages without affecting the existing manual translations for three other languages. Solution: We recommended using the WPML bulk automatic translation feature with the following steps: 1. Navigate to WPML > Translation Management. 2. Select the posts and pages that require translation. 3. Choose the two languages for automatic translation. 4. For the three languages with manual translations, set the option to "Do Nothing". 5. Select the Translate automatically option and then click on the Start translating button. For more detailed instructions, we provided a guide: https://wpml.org/documentation/automatic-translation/automatically-translating-multiple-translation-jobs-in-bulk/
If this solution does not apply to your case, or if it seems outdated, we encourage you 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.
Problem: The client needed to implement a language switcher with specific styling requirements, including inserting a "/" between languages and styling the selected language in a different color. Solution: We recommended using CSS to achieve the desired styling. To add a "/" between language switcher items, custom CSS can be applied. For styling the current language, the client can use the following CSS code:
.wpml-ls-item.wpml-ls-current-language a span {
color: #d00 !important;
}
If this solution does not apply or is outdated, or if you have a different 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 further assistance is needed, please open a new support ticket in our forum: WPML support forum.
Problem: The client was unable to proceed with the configuration wizard of the "WooCommerce Multilingual & Multicurrency" plugin as there was no button or link to continue the process. Solution: 1. We recommended that the client temporarily deactivate all plugins except for WPML, WooCommerce, and WooCommerce Multilingual to check if there is a conflict with another plugin. 2. We instructed the client to back up their database before making any changes. 3. We asked the client to provide us with debug information by following the instructions on our documentation page: http://wpml.org/faq/provide-debug-information-faster-support/.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, we encourage you 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. If you need further assistance, please visit our support forum: https://wpml.org/forums/forum/english-support/.
Problem: The client was experiencing issues with saving and creating multi-language products with several hundred variations, which was taking a long time to complete. Solution: 1. We confirmed that the issue had been tested on a site clone and the changes were working. 2. We instructed the client to edit a specific file by navigating to "Plugins -> Plugin Editor" and overwriting the mentioned code lines, emphasizing the importance of making a backup before making any changes. 3. We informed the client that we could not provide an ETA for the release that includes these changes, as the priority might be lower due to the lack of similar reports from other clients. 4. We updated the files on the client's site and asked the client to try saving the product again, noting that it should now take around 30 seconds without getting "stuck".
If you're experiencing a similar issue, we recommend you try the steps mentioned above. However, please be aware 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 problem persists, please open a new support ticket with us.
Problem: The client is seeing a message stating 'WPML detected a new address for this site' despite not having changed anything in the last three years. Additionally, the WPML editor is no longer available in their pages, products, etc. Solution: If you're experiencing a similar issue where you see a message about WPML detecting a new address for your site, and you find that the WPML editor is missing from your pages and products, we recommend the following steps: 1. Go to WPML > Settings > Translation Editor. 2. Here, you can switch back to using the Classic Translation Editor if you prefer it over the Advanced Translation Editor. For a guide on how to switch editors, please visit the following documentation: Translation Editor Options.
Please note that the solution provided might be irrelevant if it's outdated or not applicable 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 issue persists, please do not hesitate to open a new support ticket. You can reach out to us on the WPML support forum.
Problem: The client wanted to know if it's possible for the main language (Armenian) to show its language code 'hy' in the URL slug, similar to how the Russian version shows 'ru'.
Solution: We recommended adding PHP code to the client's theme to redirect the root domain to the directory of the default language. Here are the steps: 1. Create a PHP template file for the site's theme, preferably in a child theme. 2. Add the following PHP code to the new template file:
3. Edit the root page and select the newly created template from the Summary section in the right sidebar. 4. Update the page to ensure the root page now redirects to the default language directory.
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 you still need assistance, please open a new support ticket with us.
Problem: The client reported an issue where the header and footer were not displaying on a specific page of their site when changing the language to English or Italian. The page was created with WP editor, and they were using the Elementor Header & Footer Builder plugin with the 'Post Types Translation' option in WPML set to 'Translatable'. No translations for the header and footer were available in Elementor Header & Footer Builder, and creating translations resulted in the header and footer showing twice on all pages except the problematic one.
Solution: We recommended the following steps: 1. Ensure that all Elementor templates are translated. For guidance, see how to translate Elementor templates. 2. Follow the solution provided in a related support forum post: Help with Elementor Header & Footer. 3. Increase the WordPress memory limit to meet WPML's minimum requirements by adding the following code to the wp-config.php file:
If these steps do not resolve the issue, we asked the client to provide detailed steps on how they created and translated the header, and how they are adding the menu on the rest of the pages.
Please note that the solution provided might be 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 WPML support forum.
Problem: The client was experiencing a 404 error when trying to access the Italian translation of the BuddyPress members page. The expected Italian page was not found, but a version with an untranslated title was accessible at a different URL. The issue was not present in the development version of the site.
Solution: We identified that the slugs were not translated, which likely caused the 404 error on the Italian members page. Additionally, we mentioned that a low memory limit could contribute to the site not functioning as expected. If you're experiencing this, we recommend translating the slugs for the BuddyPress pages and ensuring that your site has an adequate memory limit.
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 open a new support ticket.
Problem: The client was unable to change the site URL in their WPML account due to a 'Site key not matching' error after migrating their website from one URL to another.
Solution:
Upon investigation by our team, we found that the client started as an end user account by taking ownership of the website. And then acquired a Blog account.
We removed the end user link from our side and now the client is able to use their Blog account by following these steps:
- Go to the Account > Sites page after login to the respective wpml.org account.
- Remove the previous site registration.
- Add a new one generating a new site key that should be used on the site.
If you still need assistance, we highly recommend opening a new support ticket in the 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
