![]() Paging & & as you've been Fluency's alpha testers sorry for the silence on your last post - I haven't had a chance to test this new version yet - hopefully soon.Ī question for you thought - have you looked at: - they are much cheaper than DeepL and support a LOT more languages. The module has been moved from Gitlab to Github to adhere to ProcessWire's module directory requirements for future listing. ![]() This includes passing DeepL's HTTP response for use in programmatic conditions. Return values from the Fluency module now match the return values from the DeepL module for consistency. If you are currently calling either the module or DeepL class directly, please read the documentation as the parameters have changed. README has been updated with documentation for usage.Ī new parameter has been added to both the Fluency and DeepL translate methods that allow you to pass in any DeepL API key/values with your request. Public methods have been added to the Fluency module so that translation, usage stats, and available languages can be pulled from calling the Fluency module or by using the DeepL class directly. It is recommended that this be enabled unless you have a specific reason not to use it. (internally this uses the preserve_formatting DeepL API parameter). The configuration screen now has a new setting for the Preserve Formatting feature which addresses the issue reported in this thread where short strings or phrases were being returned with additional/missing punctuation. ![]() After upgrading all roles who should have access must have the fluency-translate permission added Use of Fluency is now permission based as requested. Translation was pulling from the wrong location in CKEditors so it was translating the last saved content, not the latest changes made in the field before page save. This was due to the admin AJAX call to the module using a GET request where a POST request should have been used to prevent running into URL length issues. The module has been updated to fix an issue with lengthy content that would result in failure, mostly important for CKEditor fields that include markup in the content. The module has been updated with critical fixes and feature requests fulfilled. Recommended that all users upgrade to the latest version Important update to the module with a new release. Permission will be the next feature.Įxcellent to hear that it's in production! We've been using it and it's been smooth sailing. ![]() This release also formally adds the 5th Fluency->translate() argument to feed in additional API parameters.Įverything is always a time crunch between holidays here, looking forward to when I can get back to working on more changes. The new permission is named "fluency-translate" in case you want to rename yours to match the later releases. I put some work in over the weekend on the permission feature. Pushed the fix that removed the bd() call. Thanks again for your work on this - I am now using it in production. In my use case I actually needed to give the guest user this permission so that I could do translations via a cron called script. I have already changed it locally to add a "fluency" permission. Just a reminder to remove the bd($content) call in Īlso, just want to agree with request for a dedicated permission.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |