Problem: If you're experiencing issues with WPML where SEO titles and meta descriptions for categories are not appearing on the frontend, it might be due to a known issue with WPML SEO versions after 2.2.0. Previously, translations for these fields were added manually in the category editing screen. Solution: We recommend two possible solutions: 1. Roll back to WPML SEO 2.1.1 to continue using manual translations in the category edit screen. 2. Use the Translation Dashboard to translate these fields as String Packages, which is the recommended approach moving forward. You can find this option under WPML → Translation Dashboard.
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.
Problem: You are experiencing an issue where WPML is overriding the Yoast SEO fields for translated taxonomies, replacing Arabic SEO content with the default English content. This behavior is affecting the Focus keyphrase, Custom SEO title, and Meta description fields, causing a drop in rankings for Arabic pages. You need a solution that allows manual per-language editing of these fields without using WPML String Translation. Solution: This is a know issues which will be solved in a future update for WPML SEO. For now, we recommend downgrading WPML SEO to version 2.1.1 to restore the ability to manually set SEO content per language directly within each taxonomy page. This version does not force the default language values and allows for independent SEO strategies per language. You can find more details and the downgrade guide here: https://wpml.org/errata/wordpress-seo-issues-translating-yoast-seo-term-meta/.
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 WPML support forum for further assistance.
Problem: After switching to a new host, the client is unable to send translation jobs to the queue; they do not appear as expected. Solution: We identified that this issue often occurs due to a known problem related to host migration. Specifically, it involves a database error where a UUID column is missing after migration. We recommend checking the detailed documentation on this issue at WPML Known Issue on Database Error Missing UUID Column After Migration.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. We also 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. For further assistance, you can contact us directly through the WPML support forum.
Problem: If you're experiencing an error when trying to automatically translate your homepage, where WPML cannot send some of the content to translation because it includes fields that are encoded, we can help. Solution: This is a known issue. We recommend you follow the steps described on our erratum page: https://wpml.org/errata/wpml-cannot-send-base64-encoded-content-to-translation/.
If this solution does not apply to your case, or if it seems outdated, 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. We highly recommend opening a new support ticket for further assistance. You can do so at WPML support forum.
