webs

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:
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 wants to configure custom fonts in the general settings for each language, rather than for each element through the page builder.

Solution:
If you are experiencing this, we recommend using CSS code to apply different fonts for each translation. Here is an example of how to do it:

html[lang="ar"] {font-family: "Cyrillic Barlow Condensed Reg" !important; font-size: 20px !important; font-weight: 600 !important;}

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.