Skip to main content

Documentation: Autolanguage plugin

Changelog

Autolanguage PRO plugin - v2.7.2 5 6

13 November 2026

  • Addition: the `alt` and `title` attributes in HTML are translated. A translation service translates the text between the tags and leaves the tags themselves alone, which keeps links, classes and ids intact but also left the alt text of an image and the title of an image or a link in the source language. The option "Images (Alt & Caption)" never covered these: it is about the intro and full article image, not about an image placed in the text. The texts of these two attributes are now taken out of the HTML, translated together in one extra request and put back, for every translation service and for every field that holds HTML: article text, category and tag description, module content, editor custom fields and mail templates. No other attribute is touched, a value that is an address or holds no letters is left as it is, and an attribute the service did translate itself is not translated twice. Nothing to switch on: it follows the field the HTML is in
  • Fix: the social media links on the install and uninstall screens have an accessible name, so a screen reader announces "Open LinkedIn in new window" and so on instead of an empty link. The icons themselves are hidden from screen readers, every link that opens a new window carries rel="noopener noreferrer", and the new window icon of the administrator template is shown again on the other links of those screens
  • Security: a translation no longer turns text shown as code into live code. Every translated result was run through a full HTML entity decode, so `<script>` that an article showed as text became a real script tag in every translation, written past Joomla's text filters. Only the entities a translation service adds are decoded now; an entity for ``, `&` or `"` that the source itself carries stays as it is
  • Security: a batch translation checks the rights on every selected item. Rights on the component were enough to have the plugin overwrite translations, also for a user limited per category or allowed to create but not to edit. The source item, the category a new translation goes into and every existing translation now need the edit rights Joomla's own edit screen asks for; an item that fails is skipped and counted in a warning
  • Security: the Gemini API key is sent in a header instead of in the web address, where proxies and firewalls log it
  • Fix: a dictionary term is no longer replaced inside a link, an image path or an attribute. A brand name in `href="https://brand.example"` was swapped for the target term and broke the link. The dictionary now only touches the text between the tags and leaves web addresses alone
  • Fix: Traditional Chinese, Brazilian Portuguese and Serbian in Latin script are translated into the right variant. The language code was cut to two letters, so zh-TW came out as Simplified Chinese and pt-BR as European Portuguese at Google, Microsoft and DeepL. Each service now gets its own code for these variants, and DeepL gets a valid English target for every English content language
  • Fix: OpenAI, Anthropic, Gemini, Mistral, DeepSeek and xAI retry a throttled request. They gave up on the first "Too Many Requests", leaving every field after the limit in the source language, and showed the same error once per field. They now wait and try again the way DeepL, Google and Microsoft already did, an exhausted credit balance is not retried, and an error is shown once
  • Change: a large batch translation runs in steps. Everything was handled in one page request, which a selection of twenty articles into three languages regularly outlived, ending in a white page or a gateway time-out. The batch now stops after about 40 seconds and carries on by itself in a new request until the selection is done, and reports the totals at the end
  • Change: debug logging is off by default, also in the FREE edition and on a site that never saved the settings, and the log no longer holds a preview of the content being translated, only its length and a short hash
  • Change: the model lists of the AI services are cached for an hour whatever the site's cache setting. With System Cache off, the Joomla default, every visit to the configuration asked every configured service again, which could take up to a minute
  • Change: the target language buttons on an edit screen work with a keyboard and a screen reader. They have a visible focus, sit in a labelled group, and "Select all" and "Select none" are buttons. The script and its styles moved to media/plg_system_autolanguage, so the browser caches them and a template can override them, and it no longer writes to the browser console
  • Change: the plugin does nothing on a request it ignores. Its language file and log file were loaded on every page, frontend included
  • Change: the "opens in a new window" icon is shown again on links in alerts in the plugin settings; only the PRO badge hides it, and says it in hidden text instead. The DeepL usage bar has an accessible name
  • Change: replaced Joomla APIs that are removed in Joomla 7 and the `curl_close()` calls that are deprecated in PHP 8.5
  • Language: new string in all 6 languages; the Spanish one is a provisional translation awaiting review

Autolanguage plugin - v2.7.2 5 6

13 November 2026

  • Addition: the `alt` and `title` attributes in HTML are translated. A translation service translates the text between the tags and leaves the tags themselves alone, which keeps links, classes and ids intact but also left the alt text of an image and the title of an image or a link in the source language. The option "Images (Alt & Caption)" never covered these: it is about the intro and full article image, not about an image placed in the text. The texts of these two attributes are now taken out of the HTML, translated together in one extra request and put back, for every translation service and for every field that holds HTML: article text, category and tag description, module content, editor custom fields and mail templates. No other attribute is touched, a value that is an address or holds no letters is left as it is, and an attribute the service did translate itself is not translated twice. Nothing to switch on: it follows the field the HTML is in
  • Fix: the social media links on the install and uninstall screens have an accessible name, so a screen reader announces "Open LinkedIn in new window" and so on instead of an empty link. The icons themselves are hidden from screen readers, every link that opens a new window carries rel="noopener noreferrer", and the new window icon of the administrator template is shown again on the other links of those screens
  • Security: a translation no longer turns text shown as code into live code. Every translated result was run through a full HTML entity decode, so `<script>` that an article showed as text became a real script tag in every translation, written past Joomla's text filters. Only the entities a translation service adds are decoded now; an entity for ``, `&` or `"` that the source itself carries stays as it is
  • Security: a batch translation checks the rights on every selected item. Rights on the component were enough to have the plugin overwrite translations, also for a user limited per category or allowed to create but not to edit. The source item, the category a new translation goes into and every existing translation now need the edit rights Joomla's own edit screen asks for; an item that fails is skipped and counted in a warning
  • Security: the Gemini API key is sent in a header instead of in the web address, where proxies and firewalls log it
  • Fix: a dictionary term is no longer replaced inside a link, an image path or an attribute. A brand name in `href="https://brand.example"` was swapped for the target term and broke the link. The dictionary now only touches the text between the tags and leaves web addresses alone
  • Fix: Traditional Chinese, Brazilian Portuguese and Serbian in Latin script are translated into the right variant. The language code was cut to two letters, so zh-TW came out as Simplified Chinese and pt-BR as European Portuguese at Google, Microsoft and DeepL. Each service now gets its own code for these variants, and DeepL gets a valid English target for every English content language
  • Fix: OpenAI, Anthropic, Gemini, Mistral, DeepSeek and xAI retry a throttled request. They gave up on the first "Too Many Requests", leaving every field after the limit in the source language, and showed the same error once per field. They now wait and try again the way DeepL, Google and Microsoft already did, an exhausted credit balance is not retried, and an error is shown once
  • Change: a large batch translation runs in steps. Everything was handled in one page request, which a selection of twenty articles into three languages regularly outlived, ending in a white page or a gateway time-out. The batch now stops after about 40 seconds and carries on by itself in a new request until the selection is done, and reports the totals at the end
  • Change: debug logging is off by default, also in the FREE edition and on a site that never saved the settings, and the log no longer holds a preview of the content being translated, only its length and a short hash
  • Change: the model lists of the AI services are cached for an hour whatever the site's cache setting. With System Cache off, the Joomla default, every visit to the configuration asked every configured service again, which could take up to a minute
  • Change: the target language buttons on an edit screen work with a keyboard and a screen reader. They have a visible focus, sit in a labelled group, and "Select all" and "Select none" are buttons. The script and its styles moved to media/plg_system_autolanguage, so the browser caches them and a template can override them, and it no longer writes to the browser console
  • Change: the plugin does nothing on a request it ignores. Its language file and log file were loaded on every page, frontend included
  • Change: the "opens in a new window" icon is shown again on links in alerts in the plugin settings; only the PRO badge hides it, and says it in hidden text instead. The DeepL usage bar has an accessible name
  • Change: replaced Joomla APIs that are removed in Joomla 7 and the `curl_close()` calls that are deprecated in PHP 8.5
  • Language: new string in all 6 languages; the Spanish one is a provisional translation awaiting review

Autolanguage PRO plugin - v2.7.1 5 6

9 October 2026

  • Change: a YOOtheme Builder page is translated in a few requests instead of one per element. Every heading, paragraph and button on a page used to be sent to the translation service on its own, so a page of some size meant hundreds of requests within seconds, which is what a service counts against its request rate limit. The texts of a page are now collected and sent together, at most 50 per request, and a text that occurs more than once on a page, such as the label of a repeated button, is sent once and filled in everywhere. DeepL, Google Translate and Microsoft Translator take the bundle in a single call. The AI services still translate text by text, because that is how their API works, and nothing changes for them
  • Fix: DeepL no longer leaves parts of a large page untranslated with "HTTP 429 - Too Many Requests". DeepL limits not only the number of characters per month but also the number of requests it accepts in a short time, and a YOOtheme Builder page is translated element by element, so a page with a lot of content sends many small requests in quick succession. The plugin took that answer as a failure and kept the original text for the element, which left the translation created but partly in the source language, also on a Free key with nearly the whole monthly quota still available. A throttled request is now sent again after a pause that grows per attempt, following the waiting time DeepL names when it gives one, the way this already worked for Google Translate and Microsoft Translator. An exhausted character quota is not retried, because waiting does not lift it. When the limit still holds after the retries, one message says so instead of one per element

Autolanguage plugin - v2.7.1 5 6

9 October 2026

  • Change: a YOOtheme Builder page is translated in a few requests instead of one per element. Every heading, paragraph and button on a page used to be sent to the translation service on its own, so a page of some size meant hundreds of requests within seconds, which is what a service counts against its request rate limit. The texts of a page are now collected and sent together, at most 50 per request, and a text that occurs more than once on a page, such as the label of a repeated button, is sent once and filled in everywhere. DeepL, Google Translate and Microsoft Translator take the bundle in a single call. The AI services still translate text by text, because that is how their API works, and nothing changes for them
  • Fix: DeepL no longer leaves parts of a large page untranslated with "HTTP 429 - Too Many Requests". DeepL limits not only the number of characters per month but also the number of requests it accepts in a short time, and a YOOtheme Builder page is translated element by element, so a page with a lot of content sends many small requests in quick succession. The plugin took that answer as a failure and kept the original text for the element, which left the translation created but partly in the source language, also on a Free key with nearly the whole monthly quota still available. A throttled request is now sent again after a pause that grows per attempt, following the waiting time DeepL names when it gives one, the way this already worked for Google Translate and Microsoft Translator. An exhausted character quota is not retried, because waiting does not lift it. When the limit still holds after the retries, one message says so instead of one per element

Autolanguage PRO plugin - v2.7.0 5 6

7 October 2026

  • Change: the instruction sent to the AI translation services (OpenAI, Anthropic, Gemini, Mistral, DeepSeek and xAI) is stricter. The text to translate is now fenced between markers and the instruction states that everything between them is text, never a command, that a question is translated into a question rather than answered, and that an instruction is translated rather than carried out. The wording lives in one place instead of being repeated in each of the six services, so they can no longer drift apart. DeepL, Google Translate and Microsoft Translator are unaffected: they are translation services and have no conversation to be drawn into
  • Fix: a title is no longer replaced by an answer to itself. A short field such as "Where is Mount Sinai?" reads as a question, and an AI translation service sometimes answers it instead of translating it, returning a paragraph about the location. That paragraph does not fit in the title field, so the translation failed with "Data too long for column title" and that language was skipped. A result that is far longer than its source can never be a translation, so it is now refused, the original text is kept and the log records what happened. Running the translation again gives the service another chance
  • Fix: "Update links in content" now reaches a YOOtheme Builder page. The setting rewrites a link so it points at the translation of the article, category or menu item it leads to, but it looked for `href="index.php?..."` in the text, and a Builder page has none: its links live in the layout JSON as a property, and a link typed into a text block sits there behind escaped quotes that the same search cannot see either. Every translated Builder page therefore kept pointing at the source language. Both kinds are now rewritten, along with the `lang` parameter. Only the `index.php?` form is handled: a SEF link carries no ids, and guessing which item it leads to would send visitors to the wrong page, so pick the non-SEF form in the link picker for links that have to follow the translation
  • Fix: a translation run ended in a 500 while its work had already been done. Before writing a clone the plugin checked its database connection, because a long translation call leaves it idle long enough for MySQL to drop it, and it did so by opening a second driver and handing that driver's open connection to the first one. Two driver objects then owned one connection and both closed it at the end of the request, so the second close failed with "mysqli object is already closed" from a destructor, far outside any code that could catch it. The translations themselves were already saved, which is why reloading the page showed them. The connection is now reopened on the driver the plugin already has, and only when a check shows it is actually gone
  • Fix: a block of content that happens to contain a brace or an icon is translated again on a YOOtheme Builder page. Two rules meant to keep technical values away from the translation service, one for CSS and JSON, one for SVG markup, rejected the whole value as soon as such a fragment appeared anywhere inside it. A custom HTML table with a `<style>` block in front of it, or with a check mark drawn as an inline SVG in one of its cells, was therefore left in the source language while the rest of the page came back translated. Both rules now only apply to a value that is nothing but code or nothing but an icon
  • Fix: the column headers of a YOOtheme table element are translated. The five header fields were missing from the list of translatable properties, so a table came back with translated rows under headers still in the source language
  • Fix: a YOOtheme Builder article kept its page content in the source language. YOOtheme stores the builder layout as JSON in an HTML comment in the article text and renders the page from that JSON, so the layout is the only copy that reaches a visitor. The plugin looked that comment up with an expression that stops at the first `-->`, and a layout holding an HTML comment of its own, which any pasted snippet or tracking code puts there, was therefore handed over truncated and unreadable. The layout was then kept as it was and the translation ran on the article text YOOtheme never shows, which left the translated article with an English title above a page still entirely in the source language. The layout is now read with the same expression YOOtheme reads it with
  • Fix: a YOOtheme layout the plugin cannot read is now named in the log as such. Both routes that kept the source language were silent, so a log could not tell an article that has no builder layout apart from one whose layout could not be parsed, and a support log looked exactly the same in both cases
  • Fix: the language buttons shown when editing an item no longer include the language of the item itself. The list was built from the "Active Source Language" setting, so with that setting left empty every content language was offered, including the one the item was already in. Ticking it never did anything, because saving always leaves the item's own language out, but it suggested a translation that was never going to happen. When no other language is left, the notice is not shown at all
  • Fix: a translation into a language with its own script gets an alias in that script again. With "Unicode Aliases" switched on in the Global Configuration, a Hebrew, Russian or Ukrainian translation has to get an alias in its own characters, but on Joomla 6 a new translation came out as `byt` for "בית" or `sovist` for "Совість". The plugin built the alias itself and in doing so skipped that setting, and since Joomla 6 writes every script out in Latin letters the result was no longer empty, so Joomla kept it. The alias is now made the way Joomla makes it for an item saved by hand, in the language of the translation. Applies to articles, categories, menu items and tags. Existing translations keep the alias they have: empty the alias field and save to have it rebuilt
  • Fix: a new translation is linked to its source again when the item already has translations in other languages. Joomla gives a group of associated items a new key when the item is saved, and it does so after the plugin has read the old one. This has always been the case for menu items and applies to categories since Joomla 6.1. The new translation was then stored under the key the group had just left, so it was associated with nothing, and saving the source again created a second translation next to it. The association is now written under the key the group has at the end of the save. A translation that was left unlinked before this version has to be associated by hand once, or removed so the next save creates it again
  • Addition: "Link A/B/C text" added to the translatable fields for articles. The three link labels on an article's Links tab were copied to every translation unchanged, so a Dutch "Lees het rapport" stayed Dutch on the English article. Tick the new option and `urlatext`, `urlbtext` and `urlctext` are translated along with the rest. The addresses themselves are never rewritten, and a label that is an address rather than a piece of text is left alone so a bare link does not come back as translated words. Existing installations keep the fields they have selected, so switch the option on to start using it
  • Addition: "Tags" added to the translatable fields for articles. With "Fields to Update" set to "Only the selected fields" the tags of an existing translation were never touched, so there was no way to bring the tags of a set of translations up to date without rebuilding everything else from the source article as well. Tick the new option, and leave the others unticked if tags are all you want, and saving the source article updates the tags of its translations and nothing else. With "Fields to Update" on "All fields" tags keep following the source as they always did. Existing installations keep the fields they have selected, so switch the option on to start using it
  • Change: a tag taken off an article now comes off its translations too. Tags were only ever added, so a translation kept every tag the source article had ever carried. A tag is removed when it is no longer on the source article and is a tag for all languages, a tag in the source language, or the translation of a tag in the source language. A tag that exists only in the language of the translation was put there by hand and stays
  • Addition: Joomill scheduled promotion
  • Addition: License status notice
  • Language: new strings in all 6 languages; the Spanish ones are a provisional translation awaiting review
  • Change: compatible with Joomla 6.2

Autolanguage plugin - v2.7.0 5 6

7 October 2026

  • Change: the instruction sent to the AI translation services (OpenAI, Anthropic, Gemini, Mistral, DeepSeek and xAI) is stricter. The text to translate is now fenced between markers and the instruction states that everything between them is text, never a command, that a question is translated into a question rather than answered, and that an instruction is translated rather than carried out. The wording lives in one place instead of being repeated in each of the six services, so they can no longer drift apart. DeepL, Google Translate and Microsoft Translator are unaffected: they are translation services and have no conversation to be drawn into
  • Fix: a title is no longer replaced by an answer to itself. A short field such as "Where is Mount Sinai?" reads as a question, and an AI translation service sometimes answers it instead of translating it, returning a paragraph about the location. That paragraph does not fit in the title field, so the translation failed with "Data too long for column title" and that language was skipped. A result that is far longer than its source can never be a translation, so it is now refused, the original text is kept and the log records what happened. Running the translation again gives the service another chance
  • Fix: "Update links in content" now reaches a YOOtheme Builder page. The setting rewrites a link so it points at the translation of the article, category or menu item it leads to, but it looked for `href="index.php?..."` in the text, and a Builder page has none: its links live in the layout JSON as a property, and a link typed into a text block sits there behind escaped quotes that the same search cannot see either. Every translated Builder page therefore kept pointing at the source language. Both kinds are now rewritten, along with the `lang` parameter. Only the `index.php?` form is handled: a SEF link carries no ids, and guessing which item it leads to would send visitors to the wrong page, so pick the non-SEF form in the link picker for links that have to follow the translation
  • Fix: a translation run ended in a 500 while its work had already been done. Before writing a clone the plugin checked its database connection, because a long translation call leaves it idle long enough for MySQL to drop it, and it did so by opening a second driver and handing that driver's open connection to the first one. Two driver objects then owned one connection and both closed it at the end of the request, so the second close failed with "mysqli object is already closed" from a destructor, far outside any code that could catch it. The translations themselves were already saved, which is why reloading the page showed them. The connection is now reopened on the driver the plugin already has, and only when a check shows it is actually gone
  • Fix: a block of content that happens to contain a brace or an icon is translated again on a YOOtheme Builder page. Two rules meant to keep technical values away from the translation service, one for CSS and JSON, one for SVG markup, rejected the whole value as soon as such a fragment appeared anywhere inside it. A custom HTML table with a `<style>` block in front of it, or with a check mark drawn as an inline SVG in one of its cells, was therefore left in the source language while the rest of the page came back translated. Both rules now only apply to a value that is nothing but code or nothing but an icon
  • Fix: the column headers of a YOOtheme table element are translated. The five header fields were missing from the list of translatable properties, so a table came back with translated rows under headers still in the source language
  • Fix: a YOOtheme Builder article kept its page content in the source language. YOOtheme stores the builder layout as JSON in an HTML comment in the article text and renders the page from that JSON, so the layout is the only copy that reaches a visitor. The plugin looked that comment up with an expression that stops at the first `-->`, and a layout holding an HTML comment of its own, which any pasted snippet or tracking code puts there, was therefore handed over truncated and unreadable. The layout was then kept as it was and the translation ran on the article text YOOtheme never shows, which left the translated article with an English title above a page still entirely in the source language. The layout is now read with the same expression YOOtheme reads it with
  • Fix: a YOOtheme layout the plugin cannot read is now named in the log as such. Both routes that kept the source language were silent, so a log could not tell an article that has no builder layout apart from one whose layout could not be parsed, and a support log looked exactly the same in both cases
  • Fix: the language buttons shown when editing an item no longer include the language of the item itself. The list was built from the "Active Source Language" setting, so with that setting left empty every content language was offered, including the one the item was already in. Ticking it never did anything, because saving always leaves the item's own language out, but it suggested a translation that was never going to happen. When no other language is left, the notice is not shown at all
  • Fix: a translation into a language with its own script gets an alias in that script again. With "Unicode Aliases" switched on in the Global Configuration, a Hebrew, Russian or Ukrainian translation has to get an alias in its own characters, but on Joomla 6 a new translation came out as `byt` for "בית" or `sovist` for "Совість". The plugin built the alias itself and in doing so skipped that setting, and since Joomla 6 writes every script out in Latin letters the result was no longer empty, so Joomla kept it. The alias is now made the way Joomla makes it for an item saved by hand, in the language of the translation. Applies to articles, categories, menu items and tags. Existing translations keep the alias they have: empty the alias field and save to have it rebuilt
  • Fix: a new translation is linked to its source again when the item already has translations in other languages. Joomla gives a group of associated items a new key when the item is saved, and it does so after the plugin has read the old one. This has always been the case for menu items and applies to categories since Joomla 6.1. The new translation was then stored under the key the group had just left, so it was associated with nothing, and saving the source again created a second translation next to it. The association is now written under the key the group has at the end of the save. A translation that was left unlinked before this version has to be associated by hand once, or removed so the next save creates it again
  • Addition: "Link A/B/C text" added to the translatable fields for articles. The three link labels on an article's Links tab were copied to every translation unchanged, so a Dutch "Lees het rapport" stayed Dutch on the English article. Tick the new option and `urlatext`, `urlbtext` and `urlctext` are translated along with the rest. The addresses themselves are never rewritten, and a label that is an address rather than a piece of text is left alone so a bare link does not come back as translated words. Existing installations keep the fields they have selected, so switch the option on to start using it
  • Addition: "Tags" added to the translatable fields for articles. With "Fields to Update" set to "Only the selected fields" the tags of an existing translation were never touched, so there was no way to bring the tags of a set of translations up to date without rebuilding everything else from the source article as well. Tick the new option, and leave the others unticked if tags are all you want, and saving the source article updates the tags of its translations and nothing else. With "Fields to Update" on "All fields" tags keep following the source as they always did. Existing installations keep the fields they have selected, so switch the option on to start using it
  • Change: a tag taken off an article now comes off its translations too. Tags were only ever added, so a translation kept every tag the source article had ever carried. A tag is removed when it is no longer on the source article and is a tag for all languages, a tag in the source language, or the translation of a tag in the source language. A tag that exists only in the language of the translation was put there by hand and stays
  • Addition: Joomill scheduled promotion
  • Addition: License status notice
  • Language: new strings in all 6 languages; the Spanish ones are a provisional translation awaiting review
  • Change: compatible with Joomla 6.2

Autolanguage PRO plugin - v2.6.0 5 6

2 September 2026

  • Addition: new "Fields to Update" option for articles, categories, menu items, modules, tags and mail templates. Set it to "Only the selected fields" and an update of an existing translation writes nothing but the fields ticked under "Translatable Fields". Until now every unselected field was copied over from the source item in its original language, so a finished set of translations could not be given a meta description without their title and text being replaced by the source text at the same time. In this mode tags, custom fields, the workflow stage and the module menu assignment of the existing translation are left alone as well. The default keeps the previous behaviour
  • Fix: a translation is no longer lost when it comes out longer than the field it has to fit in. Joomla stores an article title in 255 characters, and Russian, Spanish and Portuguese generally run longer than the English original, so a title close to that limit failed with "Data too long for column title" and that language was skipped while the others went through. Every translated value is now shortened to what the field holds, counted in characters so accented and Cyrillic text is measured correctly, and the log names the field and the language that was shortened. Applies to articles, categories, menu items, modules, tags and mail templates
  • Fix: long API keys were cut off while you pasted them. Since 2.5.0 the key fields are hidden password fields, and Joomla gives such a field a limit of 99 characters unless the extension says otherwise, so the browser silently dropped everything past the 99th character. An Anthropic key is 108 characters and an OpenAI project key is longer still, so those never arrived complete and the service answered with an authorisation error. All nine key fields now allow 255 characters. Enter your key again if you added or changed one under 2.5.0
  • Fix: custom field values on articles and categories were translated even with "Custom Fields" left unticked under "Translatable Fields". The setting is now honoured: the values are still copied to the translation, but in their original language, which is what the option has always described

Autolanguage plugin - v2.6.0 5 6

2 September 2026

  • Addition: new "Fields to Update" option for articles, categories, menu items, modules, tags and mail templates. Set it to "Only the selected fields" and an update of an existing translation writes nothing but the fields ticked under "Translatable Fields". Until now every unselected field was copied over from the source item in its original language, so a finished set of translations could not be given a meta description without their title and text being replaced by the source text at the same time. In this mode tags, custom fields, the workflow stage and the module menu assignment of the existing translation are left alone as well. The default keeps the previous behaviour
  • Fix: a translation is no longer lost when it comes out longer than the field it has to fit in. Joomla stores an article title in 255 characters, and Russian, Spanish and Portuguese generally run longer than the English original, so a title close to that limit failed with "Data too long for column title" and that language was skipped while the others went through. Every translated value is now shortened to what the field holds, counted in characters so accented and Cyrillic text is measured correctly, and the log names the field and the language that was shortened. Applies to articles, categories, menu items, modules, tags and mail templates
  • Fix: long API keys were cut off while you pasted them. Since 2.5.0 the key fields are hidden password fields, and Joomla gives such a field a limit of 99 characters unless the extension says otherwise, so the browser silently dropped everything past the 99th character. An Anthropic key is 108 characters and an OpenAI project key is longer still, so those never arrived complete and the service answered with an authorisation error. All nine key fields now allow 255 characters. Enter your key again if you added or changed one under 2.5.0
  • Fix: custom field values on articles and categories were translated even with "Custom Fields" left unticked under "Translatable Fields". The setting is now honoured: the values are still copied to the translation, but in their original language, which is what the option has always described

Autolanguage PRO plugin - v2.5.0 5 6

1 September 2026

  • Addition: new "API timeout" option in the Service tab sets the maximum duration of a single translation request for all drivers (10-600 seconds, default 180)
  • Security: batch translation now checks whether you actually have rights on the component you are translating, so it can no longer be used to create content somewhere you have no access to
  • Security: API keys are now hidden fields in the configuration screen instead of plain readable text
  • Security: after a batch translation without a selection you are returned to a checked page instead of an unverified web address
  • Security: error messages from the translation services are no longer written to the log with their full response, which could contain your content
  • Security: the helper plugin for update logging is only installed when the update server supplies a valid checksum for it, and only from the Joomill update server
  • Fix: nested categories deeper than one level were created inside the source language tree instead of under their translated parent. Associations created during a translation run were only written to the database at the very end of the request, so a child could not yet see the translation of the parent that had just been created in the same run. The plugin now keeps those associations available for the rest of the request. The same fix applies to nested menu items, nested tags, articles placed in an associated category, module menu assignments and translated links in articles, modules and mail templates
  • Fix: a batch translation now processes categories, menu items and tags top down instead of in the order the list view happened to post them, so a parent is always translated before its children
  • Fix: API keys pasted from a provider's website are now cleaned of invisible characters. Copying a key from a styled page can drag along a non-breaking space, a zero width space, a byte order mark or a line break, none of which are visible in the input field and none of which were removed before. Such a key was rejected as unauthorised by every service, and for DeepL it also broke the detection of the `:fx` suffix, which sent a Free key to the Pro endpoint. Applies to all translation services
  • Fix: the subject line of a YOOtheme Builder form is translated again. The list of translatable YOOtheme properties held `email_subjec` instead of `email_subject`, so that one property never matched anything and always kept its source language
  • Fix: a translation run no longer leaves fields in their source language when the translation service briefly refuses more requests. Every field is sent as its own request, so a batch of a few articles into several languages reaches the rate limit of Google or Microsoft quickly, and until now such a field silently kept its original text. A refused request is now repeated up to three times, waiting the delay the service itself asks for, and the message names the limit instead of quoting the raw error from the service. A field that still fails keeps its original text and is updated by running the translation again. Refusals that waiting cannot solve, such as an exhausted monthly quota or an invalid key, are not repeated
  • Fix: translations no longer fail with "Connection Error: Operation timed out after 30002 milliseconds" on OpenAI. The cURL request timeout was hardcoded (30 seconds for OpenAI) and is unaffected by the PHP max_execution_time setting
  • Fix: the PRO-only settings in the free version showed an upgrade badge with no text next to it. Joomla puts every field description behind the inline help toggle, which leaves the badge without the one sentence explaining what it unlocks. Those fields now render their own description, always visible
  • Fix: the model dropdowns for OpenAI, Mistral, Anthropic, Gemini, xAI and DeepSeek, and the DeepL credits notice, showed "Error: Plugin settings not found (Check DB name)" while the plugin was still disabled. They asked Joomla for the plugin, which only hands back enabled ones, instead of reading the saved settings. The message also pointed at the database prefix, which had nothing to do with it
  • Change: when a category has no translated parent, the translation is placed at root level of the target language instead of inside the source language tree, and a warning is written to the log. Menu items and tags already behaved this way and now log the same warning
  • Change: all translation drivers now also set an explicit 15 second connect timeout, so an unreachable API endpoint fails fast instead of consuming the full request timeout

Autolanguage plugin - v2.5.0 5 6

1 September 2026

  • Addition: new "API timeout" option in the Service tab sets the maximum duration of a single translation request for all drivers (10-600 seconds, default 180)
  • Security: batch translation now checks whether you actually have rights on the component you are translating, so it can no longer be used to create content somewhere you have no access to
  • Security: API keys are now hidden fields in the configuration screen instead of plain readable text
  • Security: after a batch translation without a selection you are returned to a checked page instead of an unverified web address
  • Security: error messages from the translation services are no longer written to the log with their full response, which could contain your content
  • Security: the helper plugin for update logging is only installed when the update server supplies a valid checksum for it, and only from the Joomill update server
  • Fix: nested categories deeper than one level were created inside the source language tree instead of under their translated parent. Associations created during a translation run were only written to the database at the very end of the request, so a child could not yet see the translation of the parent that had just been created in the same run. The plugin now keeps those associations available for the rest of the request. The same fix applies to nested menu items, nested tags, articles placed in an associated category, module menu assignments and translated links in articles, modules and mail templates
  • Fix: a batch translation now processes categories, menu items and tags top down instead of in the order the list view happened to post them, so a parent is always translated before its children
  • Fix: API keys pasted from a provider's website are now cleaned of invisible characters. Copying a key from a styled page can drag along a non-breaking space, a zero width space, a byte order mark or a line break, none of which are visible in the input field and none of which were removed before. Such a key was rejected as unauthorised by every service, and for DeepL it also broke the detection of the `:fx` suffix, which sent a Free key to the Pro endpoint. Applies to all translation services
  • Fix: the subject line of a YOOtheme Builder form is translated again. The list of translatable YOOtheme properties held `email_subjec` instead of `email_subject`, so that one property never matched anything and always kept its source language
  • Fix: a translation run no longer leaves fields in their source language when the translation service briefly refuses more requests. Every field is sent as its own request, so a batch of a few articles into several languages reaches the rate limit of Google or Microsoft quickly, and until now such a field silently kept its original text. A refused request is now repeated up to three times, waiting the delay the service itself asks for, and the message names the limit instead of quoting the raw error from the service. A field that still fails keeps its original text and is updated by running the translation again. Refusals that waiting cannot solve, such as an exhausted monthly quota or an invalid key, are not repeated
  • Fix: translations no longer fail with "Connection Error: Operation timed out after 30002 milliseconds" on OpenAI. The cURL request timeout was hardcoded (30 seconds for OpenAI) and is unaffected by the PHP max_execution_time setting
  • Fix: the PRO-only settings in the free version showed an upgrade badge with no text next to it. Joomla puts every field description behind the inline help toggle, which leaves the badge without the one sentence explaining what it unlocks. Those fields now render their own description, always visible
  • Fix: the model dropdowns for OpenAI, Mistral, Anthropic, Gemini, xAI and DeepSeek, and the DeepL credits notice, showed "Error: Plugin settings not found (Check DB name)" while the plugin was still disabled. They asked Joomla for the plugin, which only hands back enabled ones, instead of reading the saved settings. The message also pointed at the database prefix, which had nothing to do with it
  • Change: when a category has no translated parent, the translation is placed at root level of the target language instead of inside the source language tree, and a warning is written to the log. Menu items and tags already behaved this way and now log the same warning
  • Change: all translation drivers now also set an explicit 15 second connect timeout, so an unreachable API endpoint fails fast instead of consuming the full request timeout

Autolanguage PRO plugin - v2.4.2 5 6

1 August 2026

  • Fix: when Translation Method is set to Batch, "Update Existing Translations" is now always treated as Yes for every content type and the option is hidden from the config screen (it only applies to, and is only shown for, the Upon Saving method)
  • Change: dlid prefix to key
  • Change: PHP file headers updated to the standard Joomla docblock copyright format; code style only, no functional changes
  • Change: full code style pass against the Joomla CMS phpcs ruleset (PSR-12): phpcbf auto-fixes for indentation, line endings, brace placement and whitespace, plus phpcs annotations for deliberate exceptions (`_JEXEC` guards, legacy global class names, legacy API naming). Code style only, no functional changes
  • Language: es-ES language (thanks to Andrés Restrepo | alamarte.com)

Autolanguage plugin - v2.4.2 5 6

1 August 2026

  • Fix: when Translation Method is set to Batch, "Update Existing Translations" is now always treated as Yes for every content type and the option is hidden from the config screen (it only applies to, and is only shown for, the Upon Saving method)
  • Change: PHP file headers updated to the standard Joomla docblock copyright format; code style only, no functional changes
  • Change: full code style pass against the Joomla CMS phpcs ruleset (PSR-12): phpcbf auto-fixes for indentation, line endings, brace placement and whitespace, plus phpcs annotations for deliberate exceptions (`_JEXEC` guards, legacy global class names, legacy API naming). Code style only, no functional changes
  • Language: es-ES language (thanks to Andrés Restrepo | alamarte.com)

Autolanguage PRO plugin - v2.4.1 5 6

8 July 2026

  • Addition: Downloads from the Joomill update server now include diagnostic request headers with site and environment information

Autolanguage plugin - v2.4.1 5 6

8 July 2026

  • Addition: Downloads from the Joomill update server now include diagnostic request headers with site and environment information

Autolanguage PRO plugin - v2.4.0 5 6

2 July 2026

  • Addition: The Help button now links to the Joomill documentation page
  • Addition: Support for plugin lazy loading
  • Addition: Review request banner
  • Change: The installer script now implements InstallerScriptInterface
  • Fix: Bug in #__history table (Joomla 5 only)

Autolanguage plugin - v2.4.0 5 6

2 July 2026

  • Addition: The Help button now links to the Joomill documentation page
  • Addition: Support for plugin lazy loading
  • Change: The installer script now implements InstallerScriptInterface
  • Fix: Bug in #__history table (Joomla 5 only)

Autolanguage plugin - v2.3.0 5 6

8 June 2026

  • Change: Updated to current Joomla standards for forward compatibility.
  • Security: Added CSRF protection to the batch translate action.
  • Security: Hardened redirect handling to prevent open-redirect issues.
  • Fix: Various stability and compatibility fixes across all translation engines.

Autolanguage PRO plugin - v2.3.0 5 6

8 June 2026

  • Addition: Custom translation instructions for AI engines Tell the AI how to translate: set the tone of voice, keep brand names or product terms untranslated, or enforce a regional spelling. Works with OpenAI, Anthropic (Claude), Gemini, Mistral, DeepSeek and xAI (Grok).
  • Addition: DeepL Translation Memory support. Reuse your saved DeepL translations for more consistent results.
  • Addition: DeepL custom instructions and glossary improvements including improved HTML tag handling for cleaner translated content.
  • Change: Smarter DeepL language handling. Formality and custom instructions are now only sent for the languages DeepL actually supports, so translating into other languages keeps working instead of failing.
  • Change: OpenAI model compatibility. Support for newer models that only accept the default temperature setting.
  • Change: Updated to current Joomla standards for forward compatibility.
  • Security: Added CSRF protection to the batch translate action.
  • Security: Hardened redirect handling to prevent open-redirect issues.
  • Fix: Various stability and compatibility fixes across all translation engines.

Autolanguage PRO plugin - v2.2.0 5 6

17 May 2026

  • Addition: Deepseek as a translation engine
  • Fix: Prevent "MySQL server has gone away" error by extend MySQL session timeout and implement reconnection logic

Autolanguage PRO plugin - v2.1.0 5 6

11 April 2026

  • Addition: Dictionary support
  • Addition: Mistral AI as a translation engine with model selection
  • Addition: Google Gemini as a translation engine
  • Addition: xAI / Grok as a translation engine
  • Fix: Refine Autolanguage conditions to block YOOtheme template pages when using 'save' translation method.

Autolanguage plugin - v2.1.0 5 6

11 April 2026

  • Addition: Dictionary support PRO version only
  • Addition: OpenAI / ChatGPT as a translation engine with model selection
  • Addition: Mistral AI as a translation engine with model selection
  • Addition: Google Gemini as a translation engine PRO version only
  • Addition: xAI / Grok as a translation engine PRO version only
  • Fix: Refine Autolanguage conditions to block YOOtheme template pages when using 'save' translation method.

Autolanguage plugin - v2.0.0 5 6

14 March 2026

  • Addition: Batch Translate mode
  • Addition: Loggerservice

Autolanguage PRO plugin - v2.0.0 5 6

14 March 2026

  • Addition: Batch Translation mode
  • Addition: Anthropic Claude as a translation engine with model selection
  • Addition: YOOtheme Pro: translation of JSON-embedded content with layout preserved
  • Addition: Configurable default status (published / unpublished / draft) for all content types
  • Addition: Download ID field in the install package for automatic updates
  • Fix: Module translations now correctly linked via com_modules.module context (ready for Joomla 6.1)
  • Change: Settings screen: clearer field layout and conditional visibility
  • Change: Language selection list is more concise and user-friendly

Autolanguage PRO plugin - v1.1.0 5 6

14 February 2026

  • Addition: Add Target Languages in Configuration
  • Addition: Add manual language filtering support on an item-by-item basis
  • Addition: DeepL: Show remaining credits after processing option
  • Addition: Enhanced Debugging & Logs

Autolanguage plugin - v1.0.1 5 6

12 February 2026

  • Fix: HTML entities

Autolanguage PRO plugin - v1.0.2 5 6

12 February 2026

  • Fix: HTML entities

Autolanguage PRO plugin - v1.0.1 5 6

8 February 2026

  • Change: Deepl formality to prefer more or less to avoid error messages

Autolanguage PRO plugin - v1.0.0 5 6

8 February 2026

  • Addition: First release

Autolanguage plugin - v1.0.0 5 6

8 February 2026

  • Addition: First release