Problem: You are experiencing issues with translations resetting to a semi-translated state on your WordPress site using the Houzez theme, particularly after making changes in theme settings, adding Google reCAPTCHA, or updating the content in Elementor.
Solution: To address translation issues with theme options and Google reCAPTCHA fields: 1. Identify the fields you want to translate in the theme options, either by their label or by inspecting the element to find its "id" or "name". 2. Depending on the type of field: - For fields displayed with posts (like a metabox), go to WPML -> Settings -> Custom Field Translation. Set the field to "Copy" or "Translate", save, and then resave the content in the default language. - For fields that are just strings, go to String Translation -> Admin Strings, find and include the field, then translate it in String Translation. 3. For Google reCAPTCHA fields ('recaptha_site_key' and 'recaptha_secret_key'), include these in String Translation under 'houzes_options', correct the language settings if necessary, and translate.
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 issue continues, please open a new support ticket at WPML support forum.
The client is experiencing PHP warnings specifically when navigating to 'Properties' to list and edit properties or when adding a new property. The issue does not appear on other pages.
Solution:
We recommend enabling the WordPress debug mode to gather more detailed information about the warnings. To do this, modify the
1
wp-config.php
file as follows:
1
2
3
4
5
6
7
8
9
10
11
12
// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );
After enabling debugging, reproduce the issue and check the
1
/wp-content/debug.log
file for any errors or warnings related to WPML. If possible, share the debug log via Pastebin for a cleaner discussion.
If the debug log does not show any WPML-related errors, the issue might be due to a plugin or theme compatibility problem. Follow these steps:
1. Ensure you back up your site. 2. Deactivate all non-WPML and non-Houzez theme related plugins. 3. Check if the issue persists. 4. If resolved, reactivate the plugins in small groups to identify the problematic plugin.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, please check the related known issues, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: You are developing a site using the Houzez theme and WPML plugin and encountering a database error when adding new properties. The error message indicates an unknown column 'ate_sync_count' in 'field list', with error code 1054. Solution: If you're experiencing this issue, we recommend you first perform a full site backup. Then, log in to your database using a tool like PHPMyAdmin and execute the following SQL query to add the missing column:
1
ALTER TABLE `wp_icl_translate_job` ADD `ate_sync_count` int unsigned NULL DEFAULT '0'AFTER `automatic`;
After running this query, check if the issue persists.
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 continues, please open a new support ticket at WPML support forum.
