Problem: The client translated three pages into Spanish, but when attempting to view these pages, they displayed as empty with only the background color visible, lacking header, footer, menus, or content.
Solution: We investigated the issue and found that it might have been related to a caching problem, which now appears to be resolved. If you're still experiencing this issue, we recommend clearing your cache and refreshing the page. Additionally, ensure that there are no duplicated templates in your theme that could be causing the problem. If the issue persists, it might be necessary to re-translate the pages to ensure all elements are correctly processed.
Please note that 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 problem continues, please do not hesitate to open a new support ticket at our support forum.
Problem: If you're experiencing an issue where the CSS selector
current-menu-item
is not being appended to the menu item in the navigation block of the page that is currently being viewed in a secondary language, this might be due to incorrect post IDs in the translated menu. Solution: We recommend checking the
wp_posts
table in your database for the menu ID and verifying the record. You should ensure that the post IDs match the translated IDs. Here is an example of what you might see and how to correct it:
<!-- wp:navigation-link {"label":"Post A – es ","type":"post","id":66,"url":"https://your-site.com/es/2024/09/15/post-a-es/","kind":"post-type"} /-->
This ID should be updated to the correct translated post ID, like so:
<!-- wp:navigation-link {"label":"Post A – es ","type":"post","id":72,"url":"https://your-site.com/es/2024/09/15/post-a-es/","kind":"post-type"} /-->
After making these changes, the menu should work correctly in the secondary language.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing an error message 'jobs cannot be loaded' when trying to access page 2 of the Translation Queue or when increasing the number of items per page, it might be due to a specific item on that page causing a failure. Solution: We recommend accessing your database and running the following SQL query:
UPDATE `{wpdbPrefix}_icl_translation_status` SET `status` = 1 WHERE `status` = 2;
Make sure to replace {wpdbPrefix} with your table prefix. It's crucial to back up your database and website before proceeding. If you're unsure how to run the SQL query, please contact your hosting support for assistance.
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 the problem persists, please open a new support ticket.
Problem: The client is using the WCFM - WooCommerce Multivendor Marketplace plugin along with its additional plugins. After exporting translations from Polylang to WPML, some Hebrew strings were mistakenly recognized as English. The client attempted to correct this using the 'Change language of selected strings' feature in WPML, but this led to further issues. Specifically, the menu item 'Store Vendors' in English was incorrectly changed to 'Store Name Vendors', and in Hebrew, it appeared as 'Vendors שם החנות'. Solution: We recommend locating the strings in question within WPML > String Translation. From there, change the default language of the string to a language that is not currently set up on the site. This will allow you to add a 'translation' for the English language, effectively correcting the string in both languages.
If this solution does not resolve the issue, or if it seems outdated or irrelevant to your current setup, 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 further assistance be needed, please do not hesitate to open a new support ticket with us at WPML support forum.
Problem: You are trying to translate the 'Read More' text of the Read More block in WordPress Gutenberg using the Twenty Twenty Four theme. Despite following the provided documentation and adding translations to all the read more String Translations, the 'Read More' text is not translating on your home page in Spanish. Solution: We manually translated the strings for you via the Gutenberg block editor. To see how we did this, you can refer to this screen recording: https://go.screenpal.com/watch/cZiVQmV8t26.
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 you still need assistance, please open a new support ticket at our support forum.
Problem: The client is experiencing issues after migrating translations from Loco Translate to WPML. Some Hebrew strings were incorrectly marked as English in WPML, and the client wishes to revert to the original Loco Translate settings and then restart the translation process manually, ensuring accuracy. Solution: First, ensure that your site meets the minimum requirements for running WPML by increasing the WP Memory limit to 256M. You can do this by adding the following code to your
wp-config.php
file:
define('WP_MEMORY_LIMIT', '256M');
Place it just before:
/* That's all, stop editing! Happy blogging. */
After updating the memory limit, verify the settings under WPML > Support > WordPress and attempt to save the translations again. Ensure that the strings in WPML > String Translation are assigned to the correct source language by following the instructions here: How to Change the Source Language of Strings. If you decide to revert to LocoTranslate, disabling WPML should return your site to its previous state. However, using the WPML reset feature is only recommended if you plan to stop using WPML entirely.
If this solution does not resolve your issue or seems outdated, please check for related known issues at WPML Known Issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket at WPML Support Forum.
Problem: The client is inquiring whether the OTGS Installer needs to remain active on their website for WPML to function correctly, and if it's possible to uninstall it after WPML has been installed. Solution: We assure the client that the OTGS Installer is a helper plugin used for the installation of WPML and that it is not required after WPML has been successfully installed. Therefore, the client can safely deactivate and uninstall the OTGS Installer from their website without affecting WPML's functionality.
If this solution does not seem relevant to your situation, please feel free to open a new support ticket with us.
