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!