Skip to content Skip to sidebar

Home › Support › English Support › [Resolved] JetReviews Plugin Translations

[Resolved] JetReviews Plugin Translations

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client was unable to translate certain fields in the JetReviews plugin despite adding them to the 

wpml-config.xml

file. They encountered issues with fields not being recognized for translation.

Solution:
We recommended a multi-step approach to resolve the translation issues:
1. Add the following to "WPML > Settings > Custom XML Config":

<wpml-config>
  <elementor-widgets>
    <widget name="jet-reviews-advanced">
      <fields>
        <field>new_review_button_label</field>
        <field>author_name_placeholder</field>
        <field>author_mail_placeholder</field>
        <field>review_content_placeholder</field>
        <field>review_title_placeholder</field>
        <field>submit_review_button_label</field>
        <field>cancel_button_label</field>
        <field>new_comment_button_label</field>
        <field>comment_placeholder</field>
        <field>show_comments_button_label</field>
        <field>hide_comments_button_label</field>
        <field>comments_title_label</field>
        <field>submit_comment_button_label</field>
        <field>reply_comment_button_label</field>
        <field>reply_placeholder</field>
        <field>submit_reply_comment_button_label</field>
      </fields>
    </widget>
  </elementor-widgets>
</wpml-config>

Then retranslate your template to be able to translate most of the texts.

2. Default labels:

Some texts, "Choose File" and "Maximum file" are default labels, and we need to match them with the JS labels.

Open ... 

\wp-content\plugins\jet-reviews\includes\components\reviews\render\review-listing-render.php

Rename 'uploadButtonLabel' with 'buttonLabel'
Rename 'uploadMaxSizeLabel' with 'maxFileSizeLabel'

Once you've done that, you'll be able to translate the "Choose File" and "Maximum file" strings using the String Translation.

If these steps do not resolve the issue, or if the solution becomes 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.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 11 replies, has 0 voices.

Last updated by fikretT 2 weeks ago.

Assisted by: Kor.

Author Posts
December 28, 2025 at 6:47 pm #17690863

fikretT

Hi,

I found some information about my problem at https://wpml.org/forums/topic/displaying-the-translations-of-some-jetreviews-fields/ and applied it. It partially worked, and I was able to translate many fields. I added new fields to the XML file for the missing fields, but I didn't get the desired result. There are a few fields that I can't translate. How can I add these fields to the XML file?

Thank you,
December 29, 2025 at 9:11 am #17694373

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for contacting us. Based on the screenshot you shared, it appears that text translation is not enabled for these strings, which is why they are not showing up in String Translation.

Could you install the plugin here on our sandbox site hidden link and replicate the issue over there so that I can check?

December 30, 2025 at 9:00 am #17696197

fikretT

Hi Kor,

I installed the plugin as requested. However, since it wouldn't be very useful on its own, I installed Elementor and Elementyro Pro separately, just like on my website, and placed them all in a single post template.

I also included the XML file I mentioned in my first message.

Thank you,

Ekran Resmi 2026-12-30 11.59.28.png
December 30, 2025 at 4:19 pm #17697136

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. I’m able to reproduce the issue on my end here:
hidden link

I’ll go ahead and escalate this to our 2nd Tier Support team for further investigation.
January 8, 2026 at 7:43 am #17711751

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your patience. I've some feedback from our 2nd Tier Support we have a solution for this.

1. Add the following to "WPML > Settings > Custom XML Config":

<wpml-config>
  <elementor-widgets>
    <widget name="jet-reviews-advanced">
      <fields>
        <field>new_review_button_label</field>
        <field>author_name_placeholder</field>
        <field>author_mail_placeholder</field>
        <field>review_content_placeholder</field>
        <field>review_title_placeholder</field>
        <field>submit_review_button_label</field>
        <field>cancel_button_label</field>
        <field>new_comment_button_label</field>
        <field>comment_placeholder</field>
        <field>show_comments_button_label</field>
        <field>hide_comments_button_label</field>
        <field>comments_title_label</field>
        <field>submit_comment_button_label</field>
        <field>reply_comment_button_label</field>
        <field>reply_placeholder</field>
        <field>submit_reply_comment_button_label</field>
      </fields>
    </widget>
  </elementor-widgets>
</wpml-config>

Then retranslate your template to be able to translate most of the texts.

2. Default labels:

Some texts, "Choose File" and "Maximum file" are default labels, and we need to match them with the JS labels.

Open ... 

\wp-content\plugins\jet-reviews\includes\components\reviews\render\review-listing-render.php

Rename 'uploadButtonLabel' with 'buttonLabel'
Rename 'uploadMaxSizeLabel' with 'maxFileSizeLabel'

Once you've done that, you'll be able to translate the "Choose File" and "Maximum file" strings using the String Translation.

I've attached some screenshots for your reference.

Screenshot_214.png
Screenshot_215.png
Screenshot_216.png
January 12, 2026 at 4:19 pm #17722514

fikretT

Hi Kor,

First of all, I wish you a wonderful new year with your loved ones. May you have abundant wealth, health, peace, and happiness.

I was able to translate some fields by following the instructions. Thank you for the instructions and screenshots. However, I couldn't translate the "Rating" field. I translate this field in the String translation section, but the end-user can't see it.

Thank you,
January 13, 2026 at 12:41 pm #17725248

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. I've tried, and I'm getting the same issue. I'm checking this with our 2nd Tier Support and I will get back to you once I've feedback.

January 13, 2026 at 4:09 pm #17726554

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your patience. I have some feedback, and it seems the string that you're trying to translate is not coded for translation. The author simply didn't use the gettext function.

Please Edit .../wp-content/plugins/jet-reviews/includes/tools.php

Line 1088, replace:

'label' => 'Rating',

With:

'label' => __('Rating', 'jet-reviews'),

Then, navigate to WPML > Theme and plugins localization > Locate the JetReviews plugin and rescan it.

Then, the string should appear correctly in the String Translation for translations. Could you try and let me know how it goes?

January 16, 2026 at 6:19 am #17735711

fikretT

Hi Kor,

I'm sorry, but I can't find the path you mentioned. I only have 1066 lines.

However, there has been an improvement. I found another bug in the plugin and reported it to the plugin authors. They confirmed the bug and suggested I revert to an older version as a temporary workaround. Could the reason I can't find the path you mentioned be because I'm currently using a different version (2.3.7) than the one you're working on?

Thank you,
January 16, 2026 at 7:22 am #17735772

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. We are testing with the latest version. Could you share your version here using Dropbox or Google Drive so that I can try to locate the code that needs to be replaced for you?

January 17, 2026 at 9:43 am #17738865

fikretT

Hi Kor,

Yes, I can do that, but it will only be a temporary solution. All the work and time we've dedicated is for the latest version of the plugin. Once the plugin authors release a new version fixing the bug, your solution will most likely work without needing to do anything extra. Wasting time with an old version is pointless. I'll wait a while. Can I reopen this thread if I encounter any problems?

Thank you,
January 19, 2026 at 8:06 am #17741192

Kor
WPML Supporter since 08/2022

Languages: English (English )

Timezone: Asia/Singapore (GMT+08:00)

Thanks for your reply. Yes, feel free to reopen this ticket if you need anything further.

January 19, 2026 at 3:37 pm #17743242

fikretT

Hi Kor,

I received a response from one of the plugin's authors. Reverting to the old version unfortunately leads to more problems that cannot be fixed. Therefore, I reverted to the latest version and followed their instructions. For all the areas I've seen so far, the translations are working.

Thank you for your time and your support,