Problem: You are experiencing issues with your website where translations have stopped syncing, the navigation menu switcher generates random links, and the website is experiencing frequent crashes. Errors reported include PHP memory exhaustion and incorrect function calls for loading translations. Solution: 1. Contact your hosting provider to increase the server PHP memory limit as indicated by the 'Fatal error: Allowed memory size exhausted' message. 2. For the PHP 'Notice: Function _load_textdomain_just_in_time', refer to the WPML errata page for guidance on resolving early translation loading issues: https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/ 3. For issues related to properties missing 'agents', follow the instructions provided in this video tutorial to assign agents to properties: https://go.screenpal.com/watch/cThQoCnQ5xZ
If these steps do not resolve your issues or if the solution seems outdated or irrelevant to your case, we 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: WPML Support Forum.
Problem: The client reported that the flags in the navigation menu were not synchronizing correctly. When clicking on a flag for another language on various pages, it redirected to a random page in that language instead of the correct translation. Solution: We first suggested checking our documentation on translating menus, which can be found here: https://wpml.org/documentation/getting-started-guide/translating-menus/ Upon further investigation, we discovered that the language switchers function correctly when the footer language switcher is enabled. We asked the client to confirm where the navigation menu language switchers were added, as we were unable to inspect or edit them.
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: The client is experiencing issues where newly imported translations from XLIFF files are not appearing or updating correctly on their website. Additionally, when attempting to edit these translations in the WPML Translation Editor, the changes do not reflect, and they have to redo the translations manually. Solution: We explained that once translations are imported via XLIFF files directly into the database, they cannot be edited using the WPML Translation Editor. This is because the WPML editor operates with a separate memory system that does not synchronize with direct database edits. To resolve this, the client should choose a consistent method of translation: either continue using XLIFF for all updates and re-import after making changes or switch to using the WPML Translation Editor for all translations to ensure consistency and avoid loss of data.
If this solution does not apply to your situation, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If issues persist, we highly recommend opening a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing "We have detected a problem with some tables in the database" error message in the WordPress back-end Solution: We recommend the following steps to address the error message: 1. Try to remove the warning message by clicking the small 'x' icon on the message. 2. Refresh the dashboard to see if the warning message reappears. If the message does not reappear, the issue is likely resolved. If the error persists, we advise the client to inform us so we can investigate further. For additional guidance, please consult our documentation on dealing with error messages: https://wpml.org/faq/how-to-deal-with-error-messages-about-a-broken-table-that-needs-fixing/#problem-with-some-tables-in-the-database
Problem: The client is experiencing an issue where the 'Min Price' field is not displaying the correct translation on the front-end, despite being translated in the back-end. Solution: We recommend the following steps: 1. Navigate to WPML-> String Translation. 2. Enable the 'Look for strings while pages are rendered' option. 3. Visit the page that contains the 'Min Price' string on the front-end. 4. Disable the 'Look for strings while pages are rendered' option. 5. Search for the 'Min Price' string and translate it.
Problem:
Property slider not showing on translated page
Solution:
To set a property to show up on the slider there's an option to set. This option is translatable, make sure:
- Property is translated.
- When translating, the option "field-REAL_HOMES_add_in_slider" should be translated as the same value "yes", instead of translating "yes" into other language (i.e. Oui for French).
