Problem: The client's website, set to Arabic as the default language in WPML settings, displays the header and footer built with Elementor only partially translated; widgets and menu content appear in Arabic, but other fields remain in English despite being translated in Elementor and string translation. Additionally, for Yoast SEO, while most features display in Arabic for admins who have selected Arabic in their profiles, the Analysis section does not switch to Arabic and remains in English. Solution: For the Elementor header and footer issue, we recommend adding the Arabic template ID in the theme options and translating it to English. This adjustment should resolve the translation discrepancies. Regarding the Yoast SEO issue, try disabling all non-WPML plugins and switching to one of the default themes to check if the problem still persists. Ensure to back up your site before making these changes.
If these solutions do not resolve your issues or seem 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 problem persists, please open a new support ticket.
Problem: You are trying to translate the Newspaper theme's (by tagDiv) post settings using the WPML translation editor, but the translations of theme's custom fields attached to the post revert to the original language.
Solution: We have identified that the issue stems from an accompanying plugin by the theme, the tagDiv Cloud Library. To resolve this, deactivate the tagDiv Cloud Library plugin, update the translation, and then check again. This should retain the proper translated values in both the backend and frontend. If this does not resolve the issue, we recommend contacting the theme support for further assistance.
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 persists, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client is experiencing a 503 error or a timeout when trying to access the 'Translate texts in admin screens' link in their WordPress site using the WPML plugin. This issue is accompanied by multiple WordPress database errors indicating that the 'wp_icl_background_task' table does not exist. Solution: First, ensure you have a backup of your site. Then, attempt to recreate the missing table by running the following SQL commands in your database:
DROP TABLE IF EXISTS wp_icl_background_task;<br />CREATE TABLE wp_icl_background_task (task_id bigint(20) unsigned NOT NULL AUTO_INCREMENT, task_type varchar(500) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci NOT NULL, task_status smallint(5) unsigned NOT NULL DEFAULT '0', starting_date datetime DEFAULT NULL, total_count int(10) unsigned NOT NULL DEFAULT '0', completed_count int(10) unsigned NOT NULL DEFAULT '0', completed_ids text CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci, payload text CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci, retry_count smallint(5) unsigned NOT NULL DEFAULT '0', PRIMARY KEY (task_id)) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_520_ci;
If issues persist after these steps, it may be due to other underlying problems not directly related to WPML. In such cases, we recommend checking for 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 still exists, please open a new support ticket for further assistance.
