module Fluency - The complete translation enhancement suite for ProcessWire

[Spinbox]

@FireWire Thank you for this amazing module!

I'm using RockPageBuilder (6.7.0) and the latest dev version of Fluency. In some cases I use nested Rockpagebuilder fields (So a Rockpagebuilder field inside a Rockpagebuilder field). In this specific case the translated values aren't saved (unless you edit the fields after translating, as you mentioned earlier).

[FireWire]

@Spinbox I'm not sure why that wouldn't be working if the fields are initialized with a translate button. I've never nested RPB fields. I'd like to support whatever features RPB has. I've reached out to @bernhard to see if there's anything that he may know of to help or confirm that nesting is supported. Will come back with more info when I can.

[imandreas]

The module is fantastic, amazing! Thank you @FireWire

Just let you know, I had a long trouble shooting, because I moved the created page "Translation" in the admin navigation into another sub-part of the tree in the navigation

That caused a lot of error messages like "An unknown error occurred while querying the translation service. Please try again later."

I tried to figure it out, but failed. Finally I found that issue.

 

[FireWire]

Quick announcement. DeepL is enforcing a new authentication method when making API calls that deprecates how previous methods were used. You may have received an email from DeepL notifying you of this change, if your clients have a DeepL account of their own to power the translation on their site they may have received this notification. This is the authentication method that Fluency uses (and was the only option available for a long time).

The deprecated authentication method will no longer work on January 15th 2026 onward, which means that the current and and all past versions of Fluency will stop working and an API error will be shown when attempting to translate content.

Fluency will be ready. I am working on updating the module to adhere to the new requirements and it will be ready ahead of the January 15th cutoff. This means that the Fluency modules you have installed for yourself and clients will need to be updated.

I just received the email notifying me a couple of days ago and this is much shorter notice than usual for a deprecation of a critical API component. Unfortunately we have to work with what we have as far as time. It isn't ideal, but again, Fluency will be ready with weeks to spare and an update will be available as soon as possible. Stay tuned for more information and an update on the module release.

Thanks and if you have any questions feel free to respond and tag me!

 

[FireWire]

@imandreas The pages under the 'Admin' branch of the page tree are often created by ProcessWire itself for Process modules. Moving them may make modules in general that use them break. It's not recommended that they be moved because they won't be where ProcessWire or the module itself expect them to be. This is part of how modules are built for ProcessWire and isn't customizable.

[FireWire]

Hello all! There's a new version of Fluency and a critical update announcement for all DeepL users.

Fluency 2.2.0 has just been released and is a critical update for all users of Fluency that employ DeepL as their translation service. As mentioned above, DeepL is deprecating their previous method of API authentication on January 15, 2025. This means that all Fluency versions less than 2.2.0 that are using DeepL will no longer translate content.

Upgrading from Fluency 1.8.0 or earlier requires a complete uninstall/reinstall. The module will have to be configured again, so note your API key if you don't have access to it otherwise. This will not result in any content loss.

Fluency 2.2.0 also brings additional features and bugfixes. These include compatibility with AdminThemUikit v3 and its theming customization abilities. Fluency also now uses CSS custom properties so it is possible to customize it separately. This release also includes a fix for an issue that may affect saving content in RockPageBuilder fields mentioned earlier in this thread. For full notes on changes and improvements see the Github release page.

If you have any trouble with the module please report them here, filing an issue on Github is helpful as well.

Thank you all for your feedback and ongoing support. Additional thanks to the developers who have donated via PayPal, always appreciated!

[Ivan Gretsky]

Good day, PWmates!

I just had a super productive and mega fast support session with @FireWire. Great thanks to you, man! 

I almost forgot how pleasant is it to be here, in the supportive and friendly PW community. I am 12 year around and this great spirit is not going nowhere) Happy New Year to all of us here, where we unite and make at least a little corner of the world a better place! 

P.S. And if you think this post is late to the party check this out))

[lpa]

Thank you for this great module — it’s very helpful.

After upgrading to version 2.2.0, we encountered a strange issue. I personally haven’t been able to reproduce it, but my colleague consistently runs into it.

When clicking the “Translate to all languages” link in the Finnish (default) body field using CKEditor, the English translation replaces the Finnish content in the default tab instead of being placed in the English tab. As a result, the original Finnish content is lost.

We are using ProcessWire 3.0.229. The CKEditor module version is 1.7.1, which comes bundled with the ProcessWire core.

What makes this even stranger is that the issue occurs on both Windows and macOS, and in both Chrome and Edge. However, on my Mac, everything works as expected in both Chrome and Safari.

[FireWire]

@lpa I didn't deliver a formal release announcement but Fluency 2.3.0 was released. There were some fixes to CKEditor that may possibly be related. I've had 2 reports of issues with CKEditor fields in the last couple of weeks that hadn't been seen before. Not sure what caused it.

2.3.0 is in the modules directory, you can upgrade from within ProcessWire or download the latest version from Github. Let me know if that fixes the issue. I'm going to be away from my computer over the weekend so I won't be able to come back and check until Monday afternoon at the earliest. 

[lpa]

Thanks. I just checked and found out that the version was already 2.3.0. So the problem is in that version, still.

[imandreas]

Hi there, I got now the response in log file of Fluence 2.1.1:

Engine: DeepLEngine /Error: AUTHENTICATION_FAILED /Message: Legacy authentication method 'query parameter' is no longer supported. Please update to header-based authentication. Find more details in our docs: https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods. You can find more info in our docs: https://developers.deepl.com/docs/getting-started/auth /Response: {"message":"Legacy authentication method 'query parameter' is no longer supported. Please update to header-based authentication. Find more details in our docs: https:\/\/developers.deepl.com\/docs\/resources\/breaking-changes-change-notices\/november-2025-deprecation-of-legacy-auth-methods. You can find more info in our docs: https:\/\/developers.deepl.com\/docs\/getting-started\/auth"}

Then I updated the codebase of Fluency module 2.3.0, API credentials of DeepL are still there, using the Free account type of Deepl.

But now I got the error message by Fluency:

An unknown error occurred while querying the translation service. Please try again later

And no further Log file entries.

Modules are already refreshed. 

Does someone has any idea what might be reason?

[imandreas]

Btw, it might be something with DeepL. On my localhost with Fluency 2.1.1 and the same API Credentials, the translation works fine, just not on live server. It might be fixed after some timeouts. 

[imandreas]

It works now again on production, but I don't know why.

I did the following:

changed codebase:

2.3.0 => 2.1.1: Fluency - Apply

With claude some changes because the API call failed:

[Fluency module API failure] JSON.parse: unexpected character at line 1 column 1 of the JSON data - Fluency.js:194:13 und dann: Uncaught (in promise) TypeError: can't access property 0, t.translations is undefined -
  FtStandaloneTranslatorFieldset.js:147:48

 - site/modules/Fluency/resources/scripts/global/Fluency.js
 - site/modules/Fluency/src/scripts/global/Fluency.js

 - site/modules/Fluency/resources/scripts/components/FtStandaloneTranslatorFieldset.js
 - site/modules/Fluency/src/scripts/components/FtStandaloneTranslatorFieldset.js
 

The POST request /page/fluency/api/translation/ failed, the API was not accessible, it returned the page itself, now the return is JSON as expexted for Fluency.
 

I'm really not sure, why it works now. 

[imandreas]

BTW - just again: this module is outstanding - love it so much (beside of course PW and other modules :) But the UI is just incredible easy :)

[FireWire]

On 1/16/2026 at 11:36 AM, lpa said:

Thanks. I just checked and found out that the version was already 2.3.0. So the problem is in that version, still.

@lpa Apologies for the late reply, I got sick and was off my feet (and keyboard) for a little while there. Are you still having this issue? If so, are you seeing any errors in the browser developer tools console? Did you make any change to your languages? Can you clear the translation cache and see if that changes anything?

On 1/21/2026 at 7:44 AM, imandreas said:

The POST request /page/fluency/api/translation/ failed, the API was not accessible, it returned the page itself, now the return is JSON as expexted for Fluency.

I can't reproduce this, I'm using Fluency 2.3.0 in production and having no issues.

On 1/21/2026 at 4:18 AM, imandreas said:

Then I updated the codebase of Fluency module 2.3.0, API credentials of DeepL are still there, using the Free account type of Deepl.

That query parameter error is impossible with 2.2.0+

<?php

// Line 217 in DeepLEngine.php
$requestUrl = "{$this->apiUrl}{$endpoint}"; // <- This used to have a query parameter for the API key anything earlier than 2.2.0 will have it

// Line 227
"Authorization: DeepL-Auth-Key {$this->apiKey}", // This is the header authentication now required and added in 2.2.0

It's not possible to get an API key parameter error because Fluency will never send a request with an API key parameter.

On 1/21/2026 at 4:42 AM, imandreas said:

Btw, it might be something with DeepL. On my localhost with Fluency 2.1.1 and the same API Credentials, the translation works fine, just not on live server. It might be fixed after some timeouts.

It's possible there's a DeepL issue? No idea. Fluency 2.1.1 should fail. 2.1.1 on local may be working if you have translation cache enabled and it's not actually making API calls to DeepL. Just a guess

This is hard to diagnose because the errors don't make sense...