Available Solutions

Problem:
The client added a custom language switcher in their header Elementor template. After switching languages, the language switcher is only visible in the default language and becomes hidden in other languages.
Solution:
We recommend going to the header template where the language switcher was added in Elementor. Make a small change and save it. Ensure that the translated version of the template is 100% complete. This should resolve the issue of the language switcher being hidden after changing languages.
If this does not resolve the issue, as a less recommended option, you can change the language from the top admin bar, go to Elementor in the translated page, and add the shortcode there too.

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 persists, please open a new support ticket.

Problem:
You are trying to translate your website into Italian and English. After translating the 'Zimmer' page and saving it, all translations disappear, and every text field is filled with 'benvenuto le camere'.
Solution:
We noticed that you are using the Classic Translation Editor, which is WPML’s legacy editor. For better translation quality and access to new features, we recommend switching to WPML’s Advanced Translation Editor. This change might also solve the issue you are experiencing.
If you have just activated WPML but have no translations yet, consider resetting WPML and reconfiguring it. Here’s how to do that:
1. Go to WPML → Support and click on the Troubleshooting link.
2. In the Reset section of the Troubleshooting page, select the checkbox for "I am about to reset all translation and language data." Then, click the "Reset and deactivate WPML" button.
Resetting WPML documentation
Please backup your database before making any changes.

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:
You are encountering a database error indicating that the 'wp_icl_string_batches' table does not exist. This error is logged during queries involving several related tables.
Solution:
First, ensure you have a staging site to test the following solution and avoid running it directly on a production website. You need to create the missing table by running the following SQL code. Please adjust the prefix according to your database configuration:

CREATE TABLE `wp_icl_string_batches` (
    `id` BIGINT(20) UNSIGNED AUTO_INCREMENT,
    `string_id` BIGINT(20) UNSIGNED NOT NULL,
    `batch_id` BIGINT(20) UNSIGNED NOT NULL,
    PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci;

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 the problem persists, please open a new support ticket.