Problem: If you're trying to translate the welcome message of the Chaty WordPress plugin into Spanish and it still appears in English despite being translated, the issue might be due to how the plugin handles text settings. The text and settings for WhatsApp are saved in the database under the option cht_social_whatsapp. In the plugin code, the option name is sometimes not correctly handled, which affects how WPML translates these settings. Solution: We recommend modifying the plugin's code to ensure consistent handling of option names. Here’s how you can do it: 1. Open the file
This change should resolve the translation issue. However, please note that you might need to reapply this fix after each Chaty plugin update unless the plugin author addresses this issue.
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 the issue persists, please open a new support ticket.
Problem: The client was unable to save the language switcher settings in the WPML -> Languages menu. Despite receiving a 'settings saved' message, the settings were not preserved upon page reload, and the language switcher did not appear in the main menu. The issue persisted even after clearing the WPML cache and was not present on a cloned site. The client discovered that disabling tagDiv plugins allowed changes to be made, but this was not a viable long-term solution. Solution: We identified that a file named
maintenance.php
, which was unexpectedly present in the wp-content folder, was causing the issue. This file was likely generated by a plugin not currently installed. Removing this file resolved the problem, allowing the client to modify the language switcher settings without needing to deactivate the tagDiv plugins. This solution suggests that the issue was related to a server-specific drop-in plugin that interfered with WPML and tagDiv plugins.
If this solution does not resolve your issue, or if it seems outdated, we 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. Should the problem persist, please open a new support ticket.
Problem: You are trying to display full property details in Arabic and Spanish on your website. The information is correctly translated but does not appear in these languages. The English version displays correctly. Solution: The issue was that admin strings that should not have been translated were being translated, specifically the field names. To resolve this, follow these steps: 1. Go to WPML > Settings > Custom XML Config and add the following configuration to ensure all labels are automatically registered for translation and prevent incorrect string registration:
2. Navigate to WPML > String Translation > Admin Strings, select all [wpresidence_admin][wpestate_custom_fields_list][add_field_name] options, and click "Remove from String Translation". 3. In WPML > String Translation, select all [wpresidence_admin][wpestate_custom_fields_list][add_field_name] options again and click on "Delete selected strings".
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 at WPML support forum for further assistance.
