attribute to pages translated into Dari on their website. While pages in Arabic correctly have this attribute, the Dari pages do not. Solution: First, ensure that Dari is recognized as an RTL language in your WordPress setup. Since Dari is not a built-in language in WPML or WordPress, you need to manually configure it. You can map Dari to Arabic in WPML to inherit the RTL attributes. This can be done under WPML -> Languages -> Site Languages -> Edit languages. For more details, visit Editing WPML's Languages Table.
Additionally, check your theme's compatibility with RTL languages and ensure it supports RTL styling. For guidance on building RTL WordPress themes, refer to Building RTL WordPress Themes and the WordPress Codex at Right-to-Left Language Support.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum.
Problem: The client is trying to add the Dari language as a custom language to their website using WPML and is concerned about a red 'X' appearing next to the Dari language in the admin area, fearing it indicates a configuration issue. Solution: We clarified that the red 'X' next to the Dari language does not indicate a problem with the language configuration. It is actually the button to delete the language and appears only because Dari is a custom language on the website. The website is correctly set up, and the client should not experience any issues with the Dari language.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening 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, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is unable to edit the URL of a hyperlink when the entire line of text in a cell is the link text, as experienced while translating a blog post using WPML. Solution: We recommend modifying the HTML structure of the hyperlink. This change should allow WPML to recognize and provide the option to edit the URL in the translation editor.
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 issues persist, please open a new support ticket.
Problem: The client is planning to migrate their staging site to production and has questions regarding the completeness of their migration checklist, the necessity of including WPML in the migration, updating WPML plugins, and managing site registrations. Solution: 1. The migration checklist is complete, but the client should use an additional tool like WPML's built-in import/export feature. More details can be found here: WPML Export and Import documentation. 2. There is no need to include WPML in the migration if the client is only importing products/pages, provided WPML is already configured on the production site. 3. The staging site URL will not be automatically removed from the client's account; the client needs to manually remove it. 4. The production site URL will not be automatically added; the client needs to manually register it. 5. The client should update WPML Multilingual CMS and WPML String Translation on the staging site before migration to ensure compatibility and functionality. This can be done via Plugins > Add New > Commercial > Check for updates. 6. If content is being migrated via WPML Import/Export and not by pushing the complete website to production, the client will need to connect and share translation memory between the sites. This step can be executed at any point before deleting the staging site, ideally before opening a page with the WPML Translation Editor. More information on this process can be found here: Automatic Translation Subscription for Multiple Sites. 7. During the migration process, the client should select "Yes / This is only a copy - original site is still running" to preserve the staging site and share translation memory with the production site.
If this solution does not resolve your issue or 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was experiencing issues with blog posts written in Arabic not rendering properly. They needed assistance with configuring WPML to support right-to-left (RTL) formatting for Arabic blog posts. Solution: We identified that the issue was due to incorrect placement of a variable in the translation string. The variable %s, which displays the list of available languages a blog post is available in, was incorrectly formatted as “s%” for RTL languages. We corrected the translation string for “This post is also available in” from
منشور المدونة متاح أيضًا باللغات التالية: s%
to
منشور المدونة متاح أيضًا باللغات التالية: %s
.
If you're experiencing similar issues, we recommend checking your translation strings for proper variable formatting in RTL languages. For further guidance, please refer to our documentation on WPML documentation.
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: The language selector does not appear on the Korean version of a blog post, although it appears on the English, Spanish, and Simplified Chinese versions. Solution: We re-translated the string related to the language selector in the WPML String Translation tool. We recommend you check if the string and languages now work correctly on your Korean post. If this solution does not resolve the issue or seems outdated, please visit our known issues page, 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 for further assistance. Contact WPML Support
Problem: You are trying to translate text items in the Jetpack newsletter signup widget on your Spanish pages using WPML, but the translations are not applying, and the text still displays in English. Solution: We recommend adding the following XML code to WPML-> Settings-> Custom XML tab to ensure the Jetpack widget strings are translatable:
After adding this code, the strings should translate correctly. Please check your Spanish version to confirm.
If this solution does not resolve your issue or 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 problem persists, please open a new support ticket.
Problem: If you're experiencing issues where links in the Spanish version of your primary navigation bar aren't linking to the correct Category pages, and the URLs have incorrect character encoding (e.g., “á” substituted for an “a” with an accent mark), leading to non-existent pages. Solution: We recommend following these steps to resolve the issue: 1. IMPORTANT: Create a backup of your website. Alternatively, test this on a copy/staging version of the website to avoid any disruption of a live website. 2. Navigate to the WordPress Dashboard > WPML > WP Menu Sync. 3. Click the sync button. 4. Select all the checkboxes. 5. Click the start button. This should help in correcting the links in your navigation bar. For more detailed guidance, visit our documentation on translating menus.
If this solution does not resolve the issue, 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 do not hesitate to open a new support ticket for further assistance.
