Strings not available for translation

Hello @alexodiy ,

Unfortunately, there are a few functional button labels that aren’t translatable. Because those labels are directly fetched from the database and are totally functional. You can’t change the language of the labels like Active, Waiting, Closed, New, and All, Advanced Filter, Thread Starter, Agent Performance (Today), Ticket (number) has been merged with this ticket at (Date). But the dev team is working on it. Hopefully, these will be translated-ready.

However, rest of them you mentioned is currently translated ready.

Also, some of the strings can be set manually from the Ticket Form Config. Here is the screenshot: https://prnt.sc/erwUVG_qTo1E

Thank you

Thanks for the reply, I’ll look for a solution myself, I’ll post to this ticket once I’ve solved it

Hello again.

Please don’t close the ticket until we resolve the issue…

So, in the file /wp-content/plugins/fluent-support/app/Hooks/Handlers/Menu.php on line 279 there is a script connection wp-content/plugins/fluent-support/assets/admin/js/start.js and in it this situation – https://skr.sh/sL2PquDKHcP?a these words are right here – https://skr.sh/sL2ii2FVaPB?a .

Are you sure you passed all lines to the start.js file via wp_localize_script() on line 378?

wp_localize_script('fluent_support_admin_app_start', 'fluentSupportAdmin', $appVars);

Among other things, word “Support” is not being translated

• This reply was modified 1 year, 7 months ago by Dan Zakirov.
• This reply was modified 1 year, 7 months ago by Dan Zakirov.

Also in this file wp-content/plugins/fluent-support/assets/portal/js/app.js the word “View all” can’t be translated, please check it

Here are some more problems in the personal user account:

1. https://skr.sh/sL3fZsWfD49?a
2. https://skr.sh/sL3GFASOjdz?a

In admin:

1. https://skr.sh/sL3RNN6Gfb8?a

Hello Dan Zakirov?

There are a few strings that are used as button/badge labels or values, which are also stored in the database. In that case, we are not allowing or showing any translation value. But we have filter hooks or configuration forms by using them you can use translated value.
For example, we have a filter hook for ticket status fluent_support/ticket_statuses(Open, closed, new) where you can translate them. Same for priorities.

However, I was checking the source to find all possible missing strings that should be translatable. And I have tried to add as much as possible. Here is the missing string I have added, which will be available in the next version.

Ticket Form Config, Advanced Filter, OR, And, medium, normal, critical, new, open, waiting, Closed, Thread Starter, Thread Follower, Support Staff, Agent Performance (Today), View All

Please note that if you have the pro version of the plugin, translation for the ticket form might not work. In that case, you have to use the translation value in the Ticket form configuration form under Global Settings.