Problem: The client was unable to view and publish translated Gravity Forms in Farsi after following the translation steps. The forms were not appearing in the pending section. Solution: We identified that the issue was related to the client's WordPress user not having the correct language pairs set up. We recommended: 1. Navigating to WPML > Translation Management > 'Translators' tab. 2. Editing the user account to set the correct language pairs for translation from the default language to Farsi. 3. Saving the changes and checking if the translation jobs appear in the list. Additionally, we handled a specific translation job by re-sending it for translation and assigning it to the client's WordPress user, which resolved the issue, allowing the form to appear correctly in Persian.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 persists, please open a new support ticket at WPML support forum.
Problem: You have customized the display of products using layers on your site and are trying to apply conditions to these layers in different languages using WPML. The condition specified for the layer in English is not applied in Farsi and Arabic translations. It works correctly in Arabic after manual recreation, but not in Persian. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to WPML-> Settings-> Custom Fields Translation section 2. Search for the following fields and set them to Copy: * wd_layout_type * wd_layout_conditions 3. Click Save 4. Edit the template in the default language 5. Make a minor edit and update it 6. Update its translation After these steps, the conditions and type should be copied to the translated templates.
Please note that 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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client needed the correct CSS code to apply a specific font for the Persian language on their website, after previously receiving incorrect information. Solution: We advised the client to use the CSS language selector
html[lang="fa-IR"]
for the Persian language. To apply the font across various elements like body, h1, h2, etc., the client should use the following code:
html[lang="fa-IR"] body { font-family: 'kalameh-fa' !important; }
If this solution does not resolve the issue or seems outdated, or if it does not apply to your case, we recommend opening a new support ticket. We also highly suggest 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 was unable to load the Elementor page builder, especially when trying to edit pages in a secondary language. Additionally, the WordPress admin bar was inactive, and there were issues with logging into the site in the secondary language. Solution: 1. We recommended increasing the WordPress memory limit to meet the WPML Minimum Requirements. 2. We suggested updating Elementor Pro to the latest version to resolve compatibility issues. 3. We enabled the "Auto sign-in and sign-out users from all domains" option in WPML -> Languages settings to fix the login issues.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your case, 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 if problems persist. For further assistance, you can also visit our support forum at WPML Support Forum.
Problem: 1. The client is using the Woodmart theme and has encountered an issue where there is no option to translate the layout used for displaying a single product. 2. Social network icons in the second language are displayed as 'X', which is due to the special fonts used in the Arabic version of the site. Solution: For the issue with social network icons, we recommend applying custom CSS to assign a different, working font to these icons. Here is an example of how you can do this:
If this does not resolve the issue, we suggest consulting with the theme support to determine which fonts are compatible.
If you find that this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket with us for further assistance. You can do so at our support forum.
This code is just an example and depending on the design of your site, you will need to apply CSS code and adjust the values.
For example, if you want to target all paragraphs on the site, you would include the
tag as follows:
html[lang="ar"] p{font-family: "Hoverla Font ENG" !important; font-size: 24px !important;}
If you want to target more HTML tags, you can use something like this:
html[lang="ar"] p, html[lang="ar"] a, html[lang="ar"] h1{font-family: "Hoverla Font ENG" !important; font-size: 24px !important;}
Please note that custom CSS is outside the scope of our Support guidelines, but we still wanted to share with you some examples that you can follow.
If the solution provided turns out to be irrelevant, either because it is outdated or does not apply to your case, we suggest opening a new support ticket. We strongly recommend that you review the known issues, check the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins.
