Polylang AI Translation Plugin

Suggest new features and report bugs here.

1
Add the ability to select from which date to translate records or in which date interval
Feature0
1
I have 4000 product. I do not want to bulk translate all of them with one job. I want to translate 400 of them which are in one category. After that next 400 and so on. Currently I cannot find convinient way to do this
Feature4
1
Where is DeepL now? Its desabled?
Feature2
1
Translate the SEO fields of title and meta description (check the box to translate?) and then for the most commonly used plugins: Yoast, Rank Math, All in One SEO, SeoPress, Slim SEO, Squirrly SEO, The SEO Framework.
Feature1
1
So we can provide support for Meta Box and Jetengine.
Feature0
1
Context We often get asked if our plugin supports themes or pagebuilders. We frequently have to say no because each system has its own storage method. Sometimes in a custom meta field, sometimes in its own database table, or sometimes via a custom post type. Proposal Create an LL
Feature0
1
We need to read the details of ones OpenAI account to show inside the plugin. Then we know whether there is credit, how much there is left and what kind of tier you are. This we users understand better what the costs are and when they need to add new credit.
Feature0
1
We need a feature to enable so that you do not have to trigger the translations yourself anymore, but the plugin is constantly checking for missing translation, schedules them and translates them.
Feature0
1
When not working with ACF, users need to be able to add custom fields that they want to be detectable by the AI translator. Currently this is possible via the "pllatavailablepostmetatranslation_fields" filter hook, but that's too technical. There needs to be a interface/field in
Feature0
1
We need to add the force mode to the bulk translator too, so that users can force translate posts and terms even if they are already translated.
Feature0